[Sheflug] major crash

[Matt Fairtlough <xxxxx [at] xxxxxxxxxxxxxx>]

Can anyone cast any light on the following trace from /var/log/messages 
(crash with suspicious
problems on rebooting: took several attempts)?  

this is a brand new Gigabyte GA-7DXR+ board with AMD XP 1800+ and 
512MBytes DDR (from Dane-elec(?)
replacing my previous, defunct main board.  How naive of me to think I'd 
have a respite from
malfunctions.  I've also installed a surge protector and replaced my 
power supply with an Apollo
300W supply (tho' they seem a bit confused about the Apollo space 
program as there is an icon with
the space shuttle on it :-) in case my previous hassles were due to 
power spikes.

Sep 16 09:08:00 xenon PAM-unix2[8376]: session finished for user root, 
service su
Sep 16 09:08:00 xenon kernel: NVRM: AGPGART: freed 16 pages
Sep 16 09:08:00 xenon kernel: NVRM: AGPGART: backend released
Sep 16 09:08:00 xenon kernel: NVRM: AGPGART: unknown chipset
Sep 16 09:08:00 xenon kernel: NVRM: AGPGART: aperture: 64M  [at]  0xe0000000
Sep 16 09:08:00 xenon kernel: NVRM: AGPGART: aperture mapped from 
0xe0000000 to 0xe2d1c000
Sep 16 09:08:00 xenon kernel: NVRM: AGPGART: mode 4x
Sep 16 09:08:00 xenon kernel: NVRM: AGPGART: allocated 16 pages
Sep 16 09:08:00 xenon PAM-unix2[7826]: session finished for user matt, 
service xdm
Sep 16 09:11:00 xenon kernel: Unable to handle kernel paging request at 
virtual address 20245489
Sep 16 09:11:00 xenon kernel:  printing eip:
Sep 16 09:11:00 xenon kernel: c011eb91
Sep 16 09:11:00 xenon kernel: *pde = 00000000
Sep 16 09:11:00 xenon kernel: Oops: 0002
Sep 16 09:11:00 xenon kernel: CPU:    0
Sep 16 09:11:00 xenon kernel: EIP:    0010:[sys_rt_sigprocmask+221/500]
Sep 16 09:11:00 xenon kernel: EFLAGS: 00010006
Sep 16 09:11:00 xenon kernel: eax: 00000000   ebx: dd4d8000   ecx: 
00000000   edx: 00000000
Sep 16 09:11:00 xenon kernel: esi: bffffc64   edi: dd4d9fc0   ebp: 
00000000   esp: dd4d9f9c
Sep 16 09:11:00 xenon kernel: ds: 0018   es: 0018   ss: 0018
Sep 16 09:11:00 xenon kernel: Process cron (pid: 837, stackpage=dd4d9000)
Sep 16 09:11:00 xenon kernel: Stack: dd4d8000 00000008 00000000 bffffb0c 
00000000 00000000 00000000 00010000
Sep 16 09:11:00 xenon kernel:        00000000 c0106e63 00000000 bffffc5c 
bffffbdc 00000008 00000000 bffffb0c
Sep 16 09:11:00 xenon kernel:        000000af 0000002b 0000002b 000000af 
4005582d 00000023 00000216 bffffaf0
Sep 16 09:11:00 xenon kernel: Call Trace: [system_call+51/64]
Sep 16 09:11:00 xenon kernel:
Sep 16 09:11:00 xenon kernel: Code: 09 c2 89 54 24 20 eb 27 8d b4 26 00 
00 00 00 8b 44 24 18 8b
Sep 16 09:11:16 xenon kernel:  <3>hub.c: Cannot enable port 1 of hub 1, 
disabling port.
Sep 16 09:11:16 xenon kernel: hub.c: Maybe the USB cable is bad?
Sep 16 09:11:18 xenon kernel: hub.c: Cannot enable port 2 of hub 1, 
disabling port.
Sep 16 09:11:18 xenon kernel: hub.c: Maybe the USB cable is bad?
Sep 16 09:11:20 xenon kernel: hub.c: Cannot enable port 1 of hub 1, 
disabling port.
Sep 16 09:11:20 xenon kernel: hub.c: Maybe the USB cable is bad?
Sep 16 09:11:22 xenon kernel: hub.c: Cannot enable port 2 of hub 1, 
disabling port.
Sep 16 09:11:22 xenon kernel: hub.c: Maybe the USB cable is bad?
Sep 16 09:11:24 xenon kernel: hub.c: Cannot enable port 1 of hub 1, 
disabling port.
Sep 16 09:11:24 xenon kernel: hub.c: Maybe the USB cable is bad?
Sep 16 09:11:25 xenon kernel: hub.c: Cannot enable port 2 of hub 1, 
disabling port.
Sep 16 09:11:25 xenon kernel: hub.c: Maybe the USB cable is bad?


___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.