Created attachment 17566 [details] Xorg.0.log with compiz frozen I have a Intel 915GM Chipset which ran without problems with Mesa from mesa_7_0_branch and XServer from server-1.4-branch on Linux 2.6.25.1 stock drm and libdrm-2.3.0 When updated to Mesa git: 056689d457924ba4d8a0723d0c5f24383d1757d9 XServer: server-1.5-branch c30f36c8c1dfd85deaf1c109823a1f15dd218ac7 with libdrm version 2.3.1 and xf86-video-intel 2.3.2 any running GLX apps freeze after a VT Switch is performed (pressing CTRL-ALT-F1 followed by CTRL-ALT-F7) and leave black windows until killed. If compiz is running the whole screen remains black and neither keyboard nor mouse respond. I can login over the network or press the ACPI Power button to do a normal shutdown. Same behaviour also seen with libdrm and drm modules from git master: 401f77a2ef1d55feaccc13cdae1e5379f4cfec7e xf86-video-intel git master: f2ec3fd8f2c63b1bc0745802dcf737eda4bb42b6 Xorg.0.log is attached.
Created attachment 17567 [details] xorg.conf xorg.conf attached
Created attachment 17568 [details] Xorg.0.log with compiz frozen Sorry wrong log previously. This is the right one.
Created attachment 17571 [details] Xorg.0.log with compiz frozen without TTM This is the Xorg.0.log with the same behaviour seen with stock drm from kernel 2.6.25.1 and libdrm 2.3.1 with xf86-video-intel 2.3.2 ( compiled with commit 55678c64bc6e3ed613ea6db14c105c18a0cf28ce cherry-picked to fix build without TTM ). This one has a lot of lines at the end with: [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnequeue: out-of-order valuator event; dropping.
Frozen screen also with KDE4/Kwin4 (RC1) using OpenGL compositing after VT Switch. (Selection in systemsettings -> Desktop -> Desktop Effects -> Advanced Options). When using XRender compositing in KWin4 instead, there is no problem, and the screen resumes after VT switch normally. Does anyone else see the same behaviour or am I doing something wrong?
Well it seems fixed after updating to libdrm and drm kernel modules to commit id b5cddbcc1536d70dfa9fec833732b2a715d82e65 I guess it was related to the vblank rework, which was committed recently.
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.