X caught signal 11 in today's xorg release

[allex87]

Hello,

I just update my fc3t3 today with yum and some xorg packages were updated. It also installed a new kernel. So I rebooted to the new kernel, but upon reboot, X would not start saying this in the log:


[root@idaho ~]# startx
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/idaho:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.4.21-20.ELsmp i686 [ELF]
Current Operating System: Linux idaho 2.6.8-1.610 #1 Tue Oct 12 17:32:34 EDT 2004 i686
Build Date: 19 October 2004
Build Host: porky.build.redhat.com

Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.8-1.610 (bhcompile@porky.build.redhat.com) (gcc version 3.4.2 20041006 (Red Hat 3.4.2-5)) #1 Tue Oct 12 17:32:34 EDT 2004
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 20 22:29:28 2004
(==) Using config file: "/etc/X11/xorg.conf"

(WW) RADEON(0): Failed to set up write-combining range (0xd0000000,0x4000000)

*** 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.

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.


I have also tried the old kernel. Same problem.

Here are some package versions...

[root@idaho ~]# rpm -q xorg-x11 kernel
xorg-x11-6.8.1-10
kernel-2.6.8-1.610
kernel-2.6.9-1.639



I hope we can get this thing going again...


Alex.

[Darkmage]

I had the same problem and I download the updated version from ftp://people.redhat.com/mharris/testing/unstable/xorg-x11/6.8.1-12/
and it worked.

[mattisking]

Yep, xorg was broken today in release 10 and then fixed later in release 12.

For those that are stuck, unable to reboot to fix the problem (and don't know how otherwise) go into Grub, select your kernel of choice (problem exists no matter the kernel selected), and edit it 'e'. There's probably 3 lines there... on the middle one, remove the ending part "rhgb Quiet" and replace it with "3" (without the quotes). This will boot up without XWindows. Once logged in you can update using yum to the now released fix (in 12).

If you can't for some reason, downgrade your xorg packages. You'll find the old packages (unless you cleared your cache) in /var/cache/yum/development/...

You'll have to work out the parameters to downgrade. I'm faaaaar from being an expert but I basically used rpm -Uvh package.rpm --force --nodeps

or something like that. I'm still running with the downgraded 8 version and will upgrade to the new 12 version tomorrow with the full set of updates.

[kennon]

Thank you very much for the updated info. Did a full upgrade on my home machine last night and got the problem as described above. I shut down and went to bed thinking I was screwed. I love the Fedora community. Everyone raves about the Debian community but I think Fedora has the best community support of any distro I have used in the last 5 years.

So if I am reading the post correctly did you say the fixed packages are now released to the yum repo's? If so can we fix this just by booting into run level 3 and running 'yum -y update'?

[jale2ice]

I was waiting for that! Thanks,