Comment 5 for bug 348450

I noticed same freeze in xmoto after upgrading everything earlier today. System is stuck in drm call from r300 dri driver. This drm call then blocks whole xserver.

Here is backtrace from blocked xserver:
#0 0x00007f3b05c15cd7 in ioctl () from /lib/libc.so.6
#1 0x00007f3b04233343 in drmIoctl () from /usr/lib/libdrm.so.2
#2 0x00007f3b042335cb in drmCommandWrite () from /usr/lib/libdrm.so.2
#3 0x00007f3af9071f20 in ?? () from /usr/lib/dri/r300_dri.so
#4 0x00007f3b0488967f in __glXDisp_Finish (cl=0x1da3650, pc=<value optimized out>) at ../../glx/single2.c:233
#5 0x00007f3b04885de2 in __glXDispatch (client=0x1df8370) at ../../glx/glxext.c:523
#6 0x000000000044e304 in Dispatch () at ../../dix/dispatch.c:437
#7 0x0000000000433d8d in main (argc=10, argv=0x7fff1003a868, envp=<value optimized out>) at ../../dix/main.c:397

yes. btw, I thought that installing libgl1-mesa-dri-dbg would give debug symbols r300 dri driver.

Nothing is printed to dmesg. (thanks to watch not reacting fast enough) Does anyone know easy way to set kernel watchdog to something like 5 seconds? /sys maybe?

So this seems like bug in kernele side that causes for ever loop or some hard lock in mutex. No more idea about it yet as Machine is not main and I only have ssh access currently.