<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [SNB regression vsync] WAIT_FOR_EVENT hangs" href="https://bugs.freedesktop.org/show_bug.cgi?id=67092#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [SNB regression vsync] WAIT_FOR_EVENT hangs" href="https://bugs.freedesktop.org/show_bug.cgi?id=67092">bug 67092</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>(In reply to <a href="show_bug.cgi?id=67092#c33">comment #33</a>) > I experience a similar issue with 3.7+ kernels that seems to be caused by > the same underlying cause. > This is a Lenovo X220t, (early) SNB graphics. > I use Metacity without compositing, in a dual-monitor setup (internal LVDS + > external VGA1). > > Launching glxgears on VGA1 causes lots of "Kicking stuck wait on render > ring" messages on dmesg and the framerate (of the entire screen) drops to > something like 0.1 fps. > Glxgears on LVDS is completely fine (60fps). Launching it on LVDS and then > dragging the window to VGA1, however, also causes the problem. > The lockups start the moment the center of the glxgears window crosses > monitors, so I suspected Vsync issue, and found this bug report. > > Adding 'Option "SwapbuffersWait" "false"' workarounds the problem. > As does enabling compositing, or switching to UXA. Please make sure that you're on the latest version of the intel DDX. Early versions of the snb vsync support had bugs with dual-head configurations. If you still experience hangs then please file a new bug report - for us it's much easier to mark duplicates than to untangle multiple bugs in the same report. And there are countless reasons to hang a gpu ;-)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>