Hello, i got this while watching a video in totem. linux kernel is git 053fe57ac249a9531c396175778160d9e9509399, the same userspace with kernel 2.6.32-rc8 is fine. Kernel is 64 bit, userspace 32 bit. Backtrace: 0: /usr/bin/X11/X(xorg_backtrace+0x3b) [0x81314cb] 1: /usr/bin/X11/X(xf86SigHandler+0x51) [0x80c1df1] 2: [0xf771a400] 3: /usr/lib/xorg/modules/drivers//intel_drv.so [0xf724ae37] 4: /usr/bin/X11/X(xf86ProbeOutputModes+0x2b3) [0x80eb673] 5: /usr/bin/X11/X [0x80f4c90] 6: /usr/bin/X11/X(RRGetInfo+0x74) [0x815f904] 7: /usr/bin/X11/X(ProcRRGetScreenInfo+0xa5) [0x8163fc5] 8: /usr/bin/X11/X [0x815bd95] 9: /usr/bin/X11/X(Dispatch+0x357) [0x808c8b7] 10: /usr/bin/X11/X(main+0x3aa) [0x8071b8a] 11: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xf73cab55] 12: /usr/bin/X11/X [0x8071051] Fatal server error: Caught signal 11. Server aborting libdrm-intel1 2.4.15-1 xserver-xorg-video-intel 2:2.9.1-1 xserver-xorg 1:7.4+4 xserver-xorg-core 2:1.6.5-1
Created attachment 32021 [details] xorg log
Created attachment 32262 [details] attached bt from crash
I have to add that everytime i open totem i have a couple of this in messages: [drm] TV-16: set mode NTSC 480i 0
Sounds like the same bug I just reported.. I have a diagnosis too: https://bugs.freedesktop.org/show_bug.cgi?id=25912 The bug is in libdrm / the kernel ioctl interface, but Jesse Barnes suggested I file against the 2D driver, since that is where the crash occurred. I'll be cheeky and mark this one as a duplicate of mine.. (since there is already a bit of diagnosis completed there) Do you also get spurious errenous detections of TV-out being connected? *** This bug has been marked as a duplicate of bug 25912 ***
(In reply to comment #4) > Do you also get spurious errenous detections of TV-out being connected? Yes, i see the same in my logs and the stackstraces look similar enough. I'm waiting for the next libdrm release to confirm it's fixed. Thanks for the debugging!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.