On Wed, Jan 28, 2009 at 11:12:23AM -0800, Florian Lier wrote: > Hey all, > > I'm trying to get the current (X.Org X Server 1.6.99.1) "X" running on > several "test-systems" for like 2 or 3 months now. (for mpx purposes) > I tested several systems with ATI, INTEL and NVIDIA gcards... > The most "difficult" system seems to be the one with NVIDIA cards. > As far as I can interpret the backtrace there is always a problem with the nv > driver. > > Backtrace: > 0: /home/fl0/mpxcompiz/bin/Xorg(xorg_backtrace+0x3b) [0x80e829b] > 1: /home/fl0/mpxcompiz/bin/Xorg(xf86SigHandler+0x51) [0x809ccb1] > 2: [0xb7f78400] > 3: /home/fl0/mpxcompiz/bin/Xorg(xf86SetDesiredModes+0x27b) [0x80ab18b] > 4: /home/fl0/mpxcompiz/lib/xorg/modules/drivers//nv_drv.so [0xb7a6412c] > 5: /home/fl0/mpxcompiz/lib/xorg/modules/drivers//nv_drv.so [0xb7a64562] > 6: /home/fl0/mpxcompiz/bin/Xorg(AddScreen+0x19d) [0x80684ad] > 7: /home/fl0/mpxcompiz/bin/Xorg(InitOutput+0x23a) [0x808b12a] > 8: /home/fl0/mpxcompiz/bin/Xorg [0x8068ba1] > 9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b19685] > 10: /home/fl0/mpxcompiz/bin/Xorg [0x8068231]
The nv driver calls back into the X server to set the first mode by calling xf86SetDesiredModes, which is crashing somewhere. This sounds like a regression in the X server. I'd recommend getting a debug X server, catching the crash in GDB, and then getting a backtrace. It's possible that the nv driver is doing something funky to the modepool that confuses xf86SetDesiredModes, but your modes look pretty normal. > Does anyone of you know a revision which doesn't stuck on startup including > the nv-driver? > Pls, correct me if I'm wrong with the nv driver thang. > > I also check out the xorg tinderbox from time to time ... seems that the last > time the master branch compiled > successfully was 2009-01-20. > > cheers, fl0 _______________________________________________ xorg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xorg
