2007/10/17, Michel Dänzer <[EMAIL PROTECTED]>: > > Here's what I get if I attach a debugger : > > > > (gdb) bt > > #0 0x00002aed809c16c7 in ioctl () from /lib/libc.so.6 > > #1 0x00002aed81fc2926 in drmFenceWait (fd=10, flags=<value optimized out>, > > fence=0x1611fa0, flush_type=<value optimized out>) at xf86drm.c:2520 > > #2 0x00002aed9300b9e6 in dri_ttm_fence_wait (fence=0x1611f80) > > at intel_bufmgr_ttm.c:694 > > #3 0x00002aed92fee12e in intelFinish (ctx=0x15f79a0) at intel_context.c:318 > > #4 0x00002aed8175e8be in __glXDisp_Finish (cl=0x1627f48, > > pc=<value optimized out>) at ../../../GL/glx/single2.c:238 > > Looks like a GPU lockup. Does this also happen if you use the i915 > kernel module from your kernel instead of from drm Git? The Mesa i915 > driver is currently very slow using the TTM due to issues to be worked > out in the DRM anyway.
Indeed the non-git i195 kernel module makes things working again with compiz, except that I now occasionnaly get some screen corruption (a typical case occurs when minimising/maximising some windows, it looks like the some parts of the screen are not refreshed correctly). How can I help debug this issue better ? Vincent ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel