Red Hat Bugzilla – Bug 136632
X crashes on startup with caught signal 11 in Xorg.0.log
Last modified: 2007-11-30 17:10:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914
Description of problem:
Following yesterday's update via yum 2 of my machines were rendered
unable to launch X.org. I saw the threads on disabling "rhgb quiet" as
well as trying to disable DRI in the xorg.conf. Neither of these
worked in allowing X to start. The section of the Xorg.0.log
containing the error is:
This has happened on a HP laptop (Radeon graphics) and an AMD Athlon
(Nvidia) so I don't think it's graphics card-specific. Both of these
boxes were started as FC3T2 and continuously updated.
Any ideas where I can begin attempting to fix this?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Reboot machine.
2. Choose .639 kernel (minus the rhgb quiet in the kernel params)
3. Boot will thrash when X tries to load
4. After 3 attempts to load, X presents error and lets you see the logs.
Actual Results: X refuses to start, even after attempting to
Expected Results: X should start up.
(**) Option "dpms"
(**) NV(0): DPMS enabled
(==) RandR enabled
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signal 11. Server aborting
*** This bug has been marked as a duplicate of 136478 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.