For example, glxgears [Switching to Thread 0xb7c036c0 (LWP 17077)] 0xb7df5ca4 in ioctl () from /lib/libc.so.6 (gdb) bt #0 0xb7df5ca4 in ioctl () from /lib/libc.so.6 #1 0xb7c2c35f in drmIoctl (fd=9, request=3222299706, arg=0xbf91c7dc) at xf86drm.c:183 #2 0xb7c2c891 in drmWaitVBlank (fd=9, vbl=0xbf91c7dc) at xf86drm.c:1895 #3 0xb79dc396 in LOCK_HARDWARE (intel=0x805a9a0) at intel_context.c:1013 #4 0xb79d783c in _intel_batchbuffer_flush (batch=0x80799c8, file=0xb7b927cc "intel_context.c", line=514) at intel_batchbuffer.c:243 #5 0xb79dc21e in intelFlush (ctx=0x805a9a0) at intel_context.c:514 #6 0xb79d86b7 in intelClearWithBlit (ctx=0x805a9a0, mask=2) at intel_blit.c:417 #7 0xb79da3a9 in intelClear (ctx=0x805a9a0, mask=258) at intel_buffers.c:602 #8 0xb7a28a1d in _mesa_Clear (mask=16640) at main/clear.c:182 #9 0x08049c21 in ?? () #10 0x00004100 in ?? () #11 0x0804d008 in ?? () #12 0xbf91c9d8 in ?? () #13 0xb7c7ff43 in XPending () from /usr/lib/libX11.so.6 #14 0x0804a5d6 in ?? () #15 0xbf91cb6c in ?? () #16 0xbf91cb9c in ?? () #17 0x3f000000 in ?? () #18 0x3f333333 in ?? () #19 0x00000000 in ?? () (gdb) quit Might report .33 fps, but sits at a black screen. Turning off vsync in driconf will allow it to run properly. git-show reports the following last commits libdrm: commit a59ea02ff839fa0801763a90beb8b232b933c746 xf86-video-intel: commit 9c9c216b1b2656b99846e9e899e108df36f4bedb mesa: commit 0970de31718288e5f2d655147d067ab2e2df5e37 Can someone look into this? P5Q-EM
This also has something to do with dual screens. If it happens on one, I can move the window to the other and vsync starts working again. It can stop on both, though.
This is still happening... Just did a pull, build, and install on mesa, drm, xf86-video-intel, and installed 2.6.28 RC3 Please help, this board doesn't work with the 2.5 drivers or newer.
Anholt's latest patches in for-review tree fixes it, tested, unable to reproduce anymore!
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.