Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Xorg 1.13 - Segfault on server shutdown -- FIXED in 1.13.1
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Tue Nov 20, 2012 4:09 am    Post subject: Xorg 1.13 - Segfault on server shutdown -- FIXED in 1.13.1 Reply with quote

After upgrading to xorg 1.13, I have been getting the following error when shutting down x and returning to the console. However, while X is running, everything seems fine. I can post additional information if needed, but I'm not sure exactly what would help in resolving this.

[ 151.706] (EE)
[ 151.706] (EE) Backtrace:
[ 151.707] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x59a356]
[ 151.707] (EE) 1: /usr/bin/X (0x400000+0x19e259) [0x59e259]
[ 151.707] (EE) 2: /lib64/libpthread.so.0 (0x7fcecaec1000+0x10460) [0x7fcecaed1460]
[ 151.707] (EE) 3: /usr/bin/X (0x400000+0x4f777) [0x44f777]
[ 151.707] (EE) 4: /usr/bin/X (0x400000+0x151ee8) [0x551ee8]
[ 151.707] (EE) 5: /usr/bin/X (0x400000+0x14be3f) [0x54be3f]
[ 151.707] (EE) 6: /usr/bin/X (mieqProcessDeviceEvent+0x1ae) [0x57b31e]
[ 151.707] (EE) 7: /usr/bin/X (0x400000+0x30f45) [0x430f45]
[ 151.707] (EE) 8: /usr/bin/X (DisableDevice+0xb8) [0x4325d8]
[ 151.707] (EE) 9: /usr/bin/X (0x400000+0x32aa2) [0x432aa2]
[ 151.707] (EE) 10: /usr/bin/X (0x400000+0x28245) [0x428245]
[ 151.707] (EE) 11: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7fcec9b5a4bd]
[ 151.707] (EE) 12: /usr/bin/X (0x400000+0x27d99) [0x427d99]
[ 151.707] (EE)
[ 151.707] (EE) Segmentation fault at address 0xd0
[ 151.707] Fatal server error:
[ 151.707] Caught signal 11 (Segmentation fault). Server aborting
[ 151.707]
[ 151.707] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help.
[ 151.707] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 151.707] (EE)
[ 152.841] Server terminated with error (1). Closing log file.

I'm not very experienced at troubleshooting Linux error messages like this, but I glanced through /var/log/Xorg.0.log and do not see any errors with anything. If I roll back to the 1.12 version of xorg that I was running, the server exits normally and I do not see any errors.

Thanks!


Last edited by fhaddad78 on Thu Jan 03, 2013 7:34 pm; edited 2 times in total
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Tue Nov 20, 2012 5:14 am    Post subject: Reply with quote

Just as an update, this appears to be a problem with xorg 1.13 as there are many similar posts online.
Back to top
View user's profile Send private message
salahx
Guru
Guru


Joined: 12 Mar 2005
Posts: 395

PostPosted: Tue Nov 20, 2012 8:57 am    Post subject: Reply with quote

While there are many posts about people with problem with the new xorg-server 1.13, interestingly there no 1 central root cause. For one person, they forgot to rebuild the drviers afterwards; one had a problem becasue they had an xorg.conf and shouldn't; one having problem because their Xorg driver is now KMS-only; one was missing their card in VIDEO_DRIVERS; and - in my case, the default gdm file was passing X a command line that caused it to crash.
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Wed Nov 21, 2012 4:22 am    Post subject: Reply with quote

Still troubleshooting:

Out of curiosity, can the way Awesome WM sends a shutdown message to the X server be the cause of the problem?

Like I mentioned in the OP, everything works fine. I'm getting the segmentation fault when I issue a shutdown to the X server. I'm using the shutdown option from the menu in Awesome WM.
Back to top
View user's profile Send private message
salahx
Guru
Guru


Joined: 12 Mar 2005
Posts: 395

PostPosted: Wed Nov 21, 2012 10:08 am    Post subject: Reply with quote

One thing that might help is to get a better backtrace, if you have splitdebug enabled (if not, enabling it requires changes CFLAGS and FEATURES and rebuilding the entire system). Tricky part is FINDING the core dump, in my case, it was in /var/gdm, so if you can replicate this without the DM (by using startx) it makes that part easier.
Back to top
View user's profile Send private message
sgao
Tux's lil' helper
Tux's lil' helper


Joined: 22 Apr 2006
Posts: 133

PostPosted: Mon Nov 26, 2012 1:12 am    Post subject: Reply with quote

Try removing /etc/X11/xorg.conf and restarting.
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Mon Nov 26, 2012 3:49 am    Post subject: Reply with quote

@sgao I don't have an xorg.conf file in /etc/X11. However, I did try removing the display configuration file /usr/share/X11/xorg.conf.d/20-nvidia.conf to see if that was causing the issue, but after removing it, X wouldn't even start. The error message said something about not finding a display.
Back to top
View user's profile Send private message
sgao
Tux's lil' helper
Tux's lil' helper


Joined: 22 Apr 2006
Posts: 133

PostPosted: Mon Nov 26, 2012 4:30 am    Post subject: Reply with quote

A few things to try:

1. Re-emerge all xorg drivers found by "qlist -I -C x11-drivers/"
2. Check if "keymap" is enabled for sys-fs/udev. If not, enable keymap, and then re-emerge udev.

If above steps still make no difference, try following:

emerge --sync
emerge portage
emerge -auvDN world
emerge --depclean
revdep-rebuild
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Mon Nov 26, 2012 5:39 am    Post subject: Reply with quote

@sgao Thanks for the quick reply. Unfortunately none of the suggested steps worked. Out of curiosity, when you are suggesting steps to try and resolve the issue, what sorts of things do you think about? The reason I ask is, I don't have any clue as to what could be causing the problem, so it's hard for me to troubleshoot.

Thanks!
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Tue Nov 27, 2012 5:58 am    Post subject: Reply with quote

UPDATE

Today I pulled out my Nvidia card and removed all the Nvidia drivers to try the Intel GPU built into my core i5 2500k. I reconfigured/compiled the kernel and removed the 20-nvidia.conf file in /usr/share/X11/xorg.conf.d, but I am still getting the segmentation fault message on exit.

I added to my .xinitrc file the following line to enable/configure dual monitors:

xrandr --output HDMI1 --mode 1600x1200 --output HDMI3 --mode 1600x1200 --right-of HDMI1

So, at this point, I'm still troubleshooting / searching for possible causes.
Back to top
View user's profile Send private message
aucampia
n00b
n00b


Joined: 21 Mar 2009
Posts: 9

PostPosted: Wed Nov 28, 2012 1:50 am    Post subject: Reply with quote

Having similar issues - also tried all suggested options.

As a side note its on my laptop with hybrid graphics - of which the discrete graphics (AMD) is not configured really.

I'm rolling back to 1.12.x
Back to top
View user's profile Send private message
aucampia
n00b
n00b


Joined: 21 Mar 2009
Posts: 9

PostPosted: Wed Nov 28, 2012 3:56 am    Post subject: Reply with quote

Still having some issues on xorg-server-1.12 - not the same issues though - I'm maksing x11-drivers/xf86-video-intel-2.20.13 - will indicate if no further crash experienced for some time.
Back to top
View user's profile Send private message
aucampia
n00b
n00b


Joined: 21 Mar 2009
Posts: 9

PostPosted: Wed Nov 28, 2012 5:55 am    Post subject: Reply with quote

I'm running stable now for some time with x11-drivers/xf86-video-intel-2.19.0

fhaddad78, can you try running with x11-drivers/xf86-video-intel-2.19.0 (with x11-base/xorg-server-1.13.0) and see if your situation improves ?
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Wed Nov 28, 2012 8:06 am    Post subject: Reply with quote

I tried the 2.19 intel drivers and had the same result, so I went back to xorg-server 1.12.4 and all is well in the world again. This is one of those issues I don't know how to troubleshoot and I can't seem to find any similar topics on-line.
Back to top
View user's profile Send private message
Fitzcarraldo
Guru
Guru


Joined: 30 Aug 2008
Posts: 531
Location: United Kingdom

PostPosted: Wed Nov 28, 2012 5:01 pm    Post subject: Reply with quote

I had to revert to xorg-server-1.12.4 too. In my case it was because the latest version of the mach64 driver (x11-drivers/xf86-video-mach64-6.9.3) won't build with xorg-server-1.13.0-r1. :roll:
_________________
Fitzcarraldo's blog
Back to top
View user's profile Send private message
gcyoung
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jul 2007
Posts: 86
Location: England

PostPosted: Thu Nov 29, 2012 4:30 pm    Post subject: xorg-server-1.13 Reply with quote

I had the same problem, until I noticed on a re-install that sys-fs/udev must be
compiled with USE flag 'keymap' set. I re-emerged that file and the x11-drivers and
the problem was solved.
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Thu Nov 29, 2012 6:25 pm    Post subject: Reply with quote

@gcyoung

Here is how I'm compiling udev. I do have keymap enabled as you stated. Anything else possibly?

sys-fs/udev-171-r9 USE="gudev keymap rule_generator -action_modeswitch -build -debug -edd (-extras) -floppy -hwdb -introspection (-selinux) {-test}"
Back to top
View user's profile Send private message
gcyoung
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jul 2007
Posts: 86
Location: England

PostPosted: Fri Nov 30, 2012 8:23 am    Post subject: Reply with quote

I may have "spoken" too soon, since I did get a couple of "hangups" later.
Anyway, I suggest you put your "USE" flags into /etc/portage/package.use, and then just execute 'emerge -uDN sys-fs/udev', as a more 'correct' method of operation.
ie:--
sys-fs/udev <list of desired flags>

The flags I have set are 'gudev hwdb introspection keymap rule_generator'. You can check your settings with 'equery u sys-fs/udev'. That will show you a list of set and unset flags.

I should also point out that I use 'slim' as a login manager, have a radeon ( ati) graphics card and use enlightenment as desktop manager. That may have some bearing, for a second computer I have with a nividia card and gnome 2 gave no problems at all on upgrade.
Back to top
View user's profile Send private message
gcyoung
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jul 2007
Posts: 86
Location: England

PostPosted: Fri Nov 30, 2012 9:22 am    Post subject: xorg-server-1.13.0-r1 Reply with quote

Gentoo Bugzilla has this listed as bug 445158
Back to top
View user's profile Send private message
gcyoung
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jul 2007
Posts: 86
Location: England

PostPosted: Sat Dec 01, 2012 1:39 pm    Post subject: xorg-server Reply with quote

I believe now that my problem may be due to another cause, since I reverted to an earlier version and still had the same problem.

I had updated openrc at the same time as xorg-server, and the problem may be due to something in that.
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Sat Dec 01, 2012 4:05 pm    Post subject: Reply with quote

@gcyoung

USE flags.
I actually do use a package.use file where I set all my USE flags. What I posted was just for you to see all the possible flags and how I had them set.

Bug 445158
I think that's a slightly different bug. Its regarding an ATI graphics card and a segmentation fault on STARTUP. I am able to start and successfully run the xorg-server. My issue is when I shut it down and return to the console. I boot my machine in console mode and use startx to launch an xsession.

Openrc
I do not think the cause is openrc. I hadn't updated my version prior to upgrading xorg-server to 1.13. I did upgrade openrc afterwards, but I can confirm I was getting the seg fault on server shutdown prior to upgrading openrc.

When searching the web for xorg 1.13 segmentation fault on shutdown, my post here is the only one that appears. I know others are getting segmentation faults but in their cases its when trying to start the x server. I don't know if that would be the same issue as mine or not though. The only thing I can confirm 100% is that my issue is directly related to xorg 1.13 because the issue goes away when I revert back to a prior version.

I guess I'll just keep on doing research and see what happens when another update to the xserver is released.
Back to top
View user's profile Send private message
gcyoung
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jul 2007
Posts: 86
Location: England

PostPosted: Sun Dec 02, 2012 1:50 pm    Post subject: xorg-server Reply with quote

to :fhaddad79

I trust you have done a revdep-rebuild recently. I have often found that to resolve
problems occurring after an update. Apologies if I am telling you what you already know.

Your first post refers to a couple of libraries. My system links these to later versions
libthread-2.15.0 and libc-2.15.so

Sorry! Just checked the earlier entries and found you had done a revdep-rebuild. Wouldn't do any harm to try the '--library' version though.
Back to top
View user's profile Send private message
gcyoung
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jul 2007
Posts: 86
Location: England

PostPosted: Mon Dec 03, 2012 11:17 am    Post subject: xorg-server Reply with quote

An update to nfs-utils-1.2.6 seems to have cured my shutdown problems, so it would appear the hangup on shutting down I experienced must have been due to an unmounting problem; not the xorg-server.
Back to top
View user's profile Send private message
v_andal
Guru
Guru


Joined: 26 Aug 2008
Posts: 305
Location: Germany

PostPosted: Tue Dec 04, 2012 8:20 am    Post subject: Reply with quote

Not very helpful, but this kind of crashes forced me to switch from fluxbox to sawfish. Somehow, with sawfish I see no crashes, while with fluxbox it was crashing everytime on shutdown.
Back to top
View user's profile Send private message
fhaddad78
n00b
n00b


Joined: 21 May 2012
Posts: 68

PostPosted: Fri Dec 07, 2012 12:32 am    Post subject: Reply with quote

UPDATE:

I recently switched to the the unstable tree and upgraded my entire system. This of course put xorg-server 1.13.0-r1 back along with the Intel 2.20.15 driver. In addition, pretty much every single package was updated and I'm still getting the segmentation fault when shutting down X.

Lastly, I noticed today (after upgrading to the 3.6.8) kernel the following lines in dmesg:

Code:
[    1.138949] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20120711/utaddress-251)
[    1.138957] ACPI Warning: 0x0000000000000500-0x000000000000057f SystemIO conflicts with Region \GPR2 1 (20120711/utaddress-251)
[    1.138959] ACPI Warning: 0x0000000000000500-0x000000000000057f SystemIO conflicts with Region \GPIO 2 (20120711/utaddress-251)
[    1.139365] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120711/utaddress-251)


No idea if this could have anything to do with the segmentation fault?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum