(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 18.104.22.1681, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.0
0: X(xf86SigHandler+0x79) [0x80bc2f9]
2: /usr/lib/xorg/modules/extensions//libglx.so [0x67705c]
3: /usr/lib/xorg/modules/extensions//libglx.so [0x6715da]
4: /usr/lib/xorg/modules/extensions//libglx.so(GlxExtensionInit+0x162) [0x676932]
5: X(InitExtensions+0x8a) [0x80e545a]
6: X(main+0x2ad) [0x806b1bd]
7: /lib/libc.so.6(__libc_start_main+0xe6) [0x41c5d6]
8: X(FontFileCompleteXLFD+0x221) [0x806a771]
Fatal server error:
Caught signal 11. Server aborting
Created attachment 300005 [details]
Full Xorg log
Same with VMWare.
Created attachment 300061 [details]
Xorg.0.log for ATI Radeon X800
Also crashes for ATI Radeon X800 on my x86_64 box.
Preliminary test of -16 indicates that it has been fixed for kvm.
*** Bug 440263 has been marked as a duplicate of this bug. ***
Created attachment 300103 [details]
Xorg.0.log x86_64 r5xx radeon
I just tried out 22.214.171.1241-16.20080401 from Koji on an x86_64 system and it is
still crashing. Attached is Xorg.0.log output.
xorg-x11-server-Xorg-126.96.36.1991-16.20080401.fc9.i386 works for me with nVidia
Corporation NV34M [GeForce FX Go5200 64M].
I did another test with an x86 box with an NV5M64 [RIVA TNT2 Model 64/Model 64
Pro] (rev 15) video card and confirmed that -15 failed and -16 worked.
I tried reverting the ati driver on the other box (x86_64 r5xx radeon) and that
one is still failing.
I did some more testing with the x86_64 machine. I reverted to
188.8.131.521-14.20080314.fc9.x86_64.rpm and things worked. I went back to
184.108.40.2061-16.20080401.fc9.x86_64.rpm and things were broken again.
I was using the latest (-9) ati driver for both of those tests.
(In reply to comment #9)
> I did some more testing with the x86_64 machine. I reverted to
> 220.127.116.111-14.20080314.fc9.x86_64.rpm and things worked. I went back to
> 18.104.22.1681-16.20080401.fc9.x86_64.rpm and things were broken again.
> I was using the latest (-9) ati driver for both of those tests.
What version of mesa are you using?
I have the following installed on the x86_64 box:
On the x86 box (that works) I have the following installed:
The backtrace in comment #6 is a different backtrace, which matches the one in
bug 440491 (supposedly fixed in -17). So I think this can be closed.
-17 seems to have fixed this and my x86_64 machine is working OK using that
version of the server.
-17 fixed the problem for me too.