After installing xorg-server 1.17.2 KDM failed to load KDE. Checking the logs I saw that X fails to load glamor and the ati drivers: EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x42) [0x58aa22] (EE) 1: /usr/bin/X (0x400000+0x18ece9) [0x58ece9] (EE) 2: /lib64/libc.so.6 (0x7f307a1c3000+0x354d0) [0x7f307a1f84d0] (EE) 3: /lib64/libc.so.6 (0x7f307a1c3000+0x933e0) [0x7f307a2563e0] (EE) 4: /usr/lib64/dri/radeonsi_dri.so (0x7f3074946000+0x146c4e) [0x7f3074a8cc4e] (EE) 5: /usr/lib64/dri/radeonsi_dri.so (0x7f3074946000+0x1d151f) [0x7f3074b1751f] (EE) 6: /usr/lib64/dri/radeonsi_dri.so (0x7f3074946000+0x147eb0) [0x7f3074a8deb0] (EE) 7: /usr/lib64/dri/radeonsi_dri.so (0x7f3074946000+0x14805a) [0x7f3074a8e05a] (EE) 8: /usr/lib64/xorg/modules/libglamoregl.so (0x7f30758a0000+0x21df8) [0x7f30758c1df8] (EE) 9: /usr/lib64/xorg/modules/libglamoregl.so (0x7f30758a0000+0x1cf15) [0x7f30758bcf15] (EE) 10: /usr/lib64/xorg/modules/libglamoregl.so (0x7f30758a0000+0x1d4ca) [0x7f30758bd4ca] (EE) 11: /usr/lib64/xorg/modules/libglamoregl.so (0x7f30758a0000+0x195a1) [0x7f30758b95a1] (EE) 12: /usr/lib64/xorg/modules/libglamoregl.so (0x7f30758a0000+0x1a0f2) [0x7f30758ba0f2] (EE) 13: /usr/bin/X (0x400000+0x11488a) [0x51488a] (EE) 14: /usr/bin/X (0x400000+0x10a50a) [0x50a50a] (EE) 15: /usr/bin/X (0x400000+0x3735e) [0x43735e] (EE) 16: /usr/bin/X (0x400000+0x3b315) [0x43b315] (EE) 17: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f307a1e4ad5] (EE) 18: /usr/bin/X (0x400000+0x2622e) [0x42622e] (EE) (EE) Segmentation fault at address 0x10 (EE) Fatal server error: Reproducible: Always Steps to Reproduce: 1. Install xorg-server 1.17.2 2. Start KDM and login to KDE Actual Results: KDM enters restart loop Expected Results: Login to KDE
Did you rebuild x11-drivers/xf86-video-ati after upgrading the X server? Recent portage versions should do that automaticaly unless the upgrade process was interrupted by a failure.
Yes, I did it twice to be sure.
The crash happens somewhere in /usr/lib64/dri/radeonsi_dri.so which is part of mesa. Which mesa version are you using?
Hello, Happens with both 10.6.1 and 10.6.2.(In reply to Chí-Thanh Christopher Nguyễn from comment #3) > The crash happens somewhere in /usr/lib64/dri/radeonsi_dri.so which is part > of mesa. > Which mesa version are you using? Hello, Happens with both 10.6.1 and 10.6.2.
I'm also suffering from this bug. I'll give a try to mesa 10.6.3.
It is the same with Mesa 10.6.3
(In reply to Dimitar Kosev from comment #6) > It is the same with Mesa 10.6.3 Thanks. I just hope for, that we are not the only dudes hitting this bug...
Status update: xorg-server-1.17.2-r1 & mesa-11.0 show exactly the same symptoms. I don't understand how other users would not run into this issue. Are there so few out their running their card using the open source radeon driver?
Is there an upstream bug? Upstream Mesa developers are much more likely to be able to diagnose and fix this.
I tried reproducing the bug but i failed, i am using xorg-server-1.17.2-r1 and mesa-10.6.3, using a AMD Radeon 7850 with xf86-video-ati.
- sys-kernel/hardened-sources-4.1.6-r1 - media-libs/mesa-11.0.0_rc2 - x11-drivers/xf86-video-ati-7.5.0 1. Intel 5520 & Xeon E5620, FirePro V4800 (Redwood XT - RV830) 2. Intel QM67 Express & i7-2630QM, FirePro M5950 (Whistler XT - Radeon HD 6770M) - x11-base/xorg-server-1.17.1-r1: runs fine on both setups - x11-base/xorg-server-1.17.2-r1: crashing on both setups [382559.636] (EE) No devices detected. [382559.636] (EE) Fatal server error: [382559.636] (EE) no screens found(EE) [382559.636] (EE)
Has anyone reported this upstream? That's the only way this will be fixed, and this bug is currently blocking stabilization of new mesa and xserver versions.
(In reply to Matt Turner from comment #12) > Has anyone reported this upstream? That's the only way this will be fixed, > and this bug is currently blocking stabilization of new mesa and xserver > versions. No, I didn't.
(In reply to Dimitar Kosev from comment #13) > (In reply to Matt Turner from comment #12) > > Has anyone reported this upstream? That's the only way this will be fixed, > > and this bug is currently blocking stabilization of new mesa and xserver > > versions. > > No, I didn't. Would you please?
Bug filed with Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=92168 I hope I will have enough time to deal with it.
Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will let us determine whether the patch at [1] is at fault. [1] https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/xorg-server-1.17.2-uninit-clientsWritable.patch
(In reply to Matt Turner from comment #16) > Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will > let us determine whether the patch at [1] is at fault. > > [1] > https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/ > xorg-server-1.17.2-uninit-clientsWritable.patch I didn't have time to test yesterday. I hope I can spend some time on this issue during the weekend. Let me report back later. According to the log attached upstream I may have a different issue compared to Dimitar, because in my case Xorg cannot even detect my card and dies early during launch. I will attach my version of failing Xorg as well. Thx: Dw.
Ok, I was able to test last night, it is the same. Fluxbox however starts normally with both 1.17.2 and r1. Could it be something KDE related that needs rebuild?
Created attachment 414400 [details] working Xorg log file 1.17.1-r1
Created attachment 414402 [details] failing Xorg log file
(In reply to Matt Turner from comment #16) > Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will > let us determine whether the patch at [1] is at fault. > > [1] > https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/ > xorg-server-1.17.2-uninit-clientsWritable.patch 1.17.2 fails, I attached Xorg logs and also another log produced by a working version of Xorg.
(In reply to Matt Turner from comment #16) > Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will > let us determine whether the patch at [1] is at fault. > > [1] > https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/ > xorg-server-1.17.2-uninit-clientsWritable.patch Please note, that the working log contains these lines after probing the card: (WW) Falling back to old probe method for modesetting (II) [KMS] Kernel modesetting enabled. While failing version says: (II) modeset(G0): using drv /dev/dri/card0 (EE) No devices detected. Do I have a configuration problem related to modesetting? Thx: Dw.
(In reply to Attila Tóth from comment #22) > (In reply to Matt Turner from comment #16) > > Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will > > let us determine whether the patch at [1] is at fault. > > > > [1] > > https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/ > > xorg-server-1.17.2-uninit-clientsWritable.patch After some guidance given by some helpful freedesktop guys it seems to be a different problem from Dimitar's. It is caused by some improper config options in my xorg.conf file. Please see this upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=92478
Hello guys, It seems this issue is now resolved. Yesterday I saw some new xorg-server packages with a fix for a crash because of xproto. I updated two systems to xorg-server 1.17.4. mesa 11.0.4, one with xproto 7.0.28 (the problematic one) and one with 7.0.27, both are so far working fine.
Thanks! Marking resolved.
