Bug#478893: libgl1-mesa-dri: stalls or crashes on GLX
Yaroslav Halchenko wrote:
> Package: libgl1-mesa-dri
> Version: 7.0.3-1
> Severity: normal
>
>
> I was trying to run freesurfer (1GB monster download which is not in
> Debian unfortunately) on some dataset on my laptop.
> When GL window appears system freezes (doesn't response to Ctrl-Alt-BS),
> and in xorg.log.old (after SysRq forced reboot) I find:
>
> ,---
> | (II) intel(0): Modeline "1280x1024"x59.9 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync (63.7 kHz)
> | (II) intel(0): EDID vendor "LEN", prod id 16389
> |
> | Backtrace:
> | 0: /usr/bin/X(xf86SigHandler+0x6a) [0x4755da]
> | 1: /lib/libc.so.6 [0x2b1aee99c240]
> | 2: /usr/lib/dri/i965_dri.so [0x2b1b019a1ceb]
> | 3: /usr/lib/dri/i965_dri.so(brw_upload_vertices+0x20a) [0x2b1b019a222a]
> | 4: /usr/lib/dri/i965_dri.so [0x2b1b019a1769]
> | 5: /usr/lib/dri/i965_dri.so(brw_draw_prims+0xb0) [0x2b1b019a1a00]
> | 6: /usr/lib/dri/i965_dri.so [0x2b1b01a378eb]
> | 7: /usr/lib/xorg/modules/extensions//libglx.so [0x2b1aefa83295]
> | 8: /usr/lib/xorg/modules/extensions//libglx.so(DoRenderLarge+0x356) [0x2b1aefa64da6]
> | 9: /usr/lib/xorg/modules/extensions//libglx.so [0x2b1aefa6872c]
> | 10: /usr/bin/X(Dispatch+0x2e0) [0x44e300]
> | 11: /usr/bin/X(main+0x47d) [0x436add]
> | 12: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b1aee9891c4]
> | 13: /usr/bin/X(FontFileCompleteXLFD+0x281) [0x435e19]
> |
> | Fatal server error:
> | Caught signal 11. Server aborting
> |
> | (II) AIGLX: Suspending AIGLX clients for VT switch
> `---
> Full log is at: http://www.onerussian.com/Linux/bugs/xorg.crash/Xorg.0.log.stalled_at_12:29:40
>
> Looking at #473551, I've decided to enable
> Option "NoTrapSignals" "True"
> and then system doesn't halt but it restarts X. Corresponding xorg.0.log is at
> http://www.onerussian.com/Linux/bugs/xorg.crash/Xorg.0.log.justrestarted
>
> My xorg.conf can be found at
> http://www.onerussian.com/Linux/bugs/xorg.crash/xorg.conf
> and dmesg
> http://www.onerussian.com/Linux/bugs/xorg.crash/dmesg
>
> Please let me know what other troubleshooting I should do to come closer to help to pin down the problem?
>
Could you install xserver-xorg-core-dbg and libgl1-mesa-dri-dbg and try
to catch a better backtrace with gdb? The easiest way would be to ssh
from another host, attach gdb with "gdb -p $(pidof X)", reproduce the
crash, enter "bt full" in gdb, and send us the output.
By the way, if you don't want X to restart X automatically after X
crashed, you can disable gdm/xdm/kdm and just startx from a VT text
console with startx.
Brice
Reply to: