kernel-2.6.13-1.1526_FC5 locks up X

[Jim Cornette]

After launching X with kernel-2.6.13-1.1526_FC5, X locked up and the
machine was totally unresponsive. X caught a signal 11 as indicated in
the Xorg.0.log.old excerpt.

(**) Option "AlwaysCore"
(**) Synaptics: always reports core events
(II) XINPUT: Adding extended input device "Synaptics" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
Synaptics DeviceInit called
SynapticsCtrl called.
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOn called
(--) Synaptics touchpad found
Synaptics DeviceOff called
Synaptics DeviceOn called
(--) Synaptics touchpad found
ProcXCloseDevice to close or not ?
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 
0x1002/0x4336]
(II) Mouse0: ps2EnableDataReporting: succeeded

    *** If unresolved symbols were reported above, they might not
    *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
	 at http://wiki.X.Org
  for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.

END


I was switching between vt terminal and between F7 where the GUI is
supposed to be when the computer crashed.

The system log from login to next login is also attached. (lucky 13)

Should a bug report be filed? X or kernel?

Jim




-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lucky-13
URL: <http://listman.redhat.com/archives/fedora-test-list/attachments/20050829/7bbfc1fc/attachment.ksh>