Fedora Linux Support Community & Resources Center
Old 21st October 2004, 03:39 AM
allex87 Offline
Registered User
Join Date: Oct 2004
Posts: 1
X caught signal 11 in today's xorg release


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

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

Old 21st October 2004, 04:27 AM
Darkmage Offline
Registered User
Join Date: Mar 2004
Posts: 462
I had the same problem and I download the updated version from ftp://people.redhat.com/mharris/test...-x11/6.8.1-12/
and it worked.
Old 21st October 2004, 05:08 AM
mattisking Offline
Registered User
Join Date: Oct 2004
Location: Charlotte, NC
Age: 44
Posts: 18
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.

Last edited by mattisking; 21st October 2004 at 05:10 AM. Reason: correction
Old 21st October 2004, 05:06 PM
kennon Offline
Registered User
Join Date: May 2004
Location: Central California
Posts: 36
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'?
Old 21st October 2004, 08:52 PM
jale2ice Offline
Registered User
Join Date: May 2004
Location: New Jersey, USA
Age: 38
Posts: 134
I was waiting for that! Thanks,
AMD Athlon XP 2500+ Barton
Corsair PC3200 DDR 400 1024MB
NVIDIA GeForce FX 5900 Ultra 256MB
Maxtor 120GB HD 7200RPM
Maxtor 60GB HD 7200RPM
Fedora Core 4 & Windows XP Pro
Registered Linux User # 372000

caught, release, signal, today, xorg

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Descent3 SIGNAL 11 caught,aborting - Fullscreen out of range Biomecanoid Using Fedora 0 19th July 2009 07:34 PM
Caught signal 15, un-registering and exiting ChantCd Hardware & Laptops 5 1st June 2007 06:58 PM
x windows problem, caught signal 11 mwenger Using Fedora 0 31st August 2005 02:55 AM
Show your support for Xorg...Ask ATI to release an Xorg driver..link inside :D jeremym Linux Chat 5 5th December 2004 02:57 PM

Current GMT-time: 09:46 (Wednesday, 23-08-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat