<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [i9xx TV][BISECT] vblank wait timeout on crtc" href="https://bugs.freedesktop.org/show_bug.cgi?id=93782#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [i9xx TV][BISECT] vblank wait timeout on crtc" href="https://bugs.freedesktop.org/show_bug.cgi?id=93782">bug 93782</a> from <a class="email" href="mailto:mariusz.g.mazur@gmail.com" title="Mariusz Mazur <mariusz.g.mazur@gmail.com>"> Mariusz Mazur</a> <pre>I don't see myself having much success (or time for) bisecting this, so maybe somebody else will find this info useful: - 4.1 and 4.2 are perfectly fine (which is why I suggest 4.1.x for anybody using gm965 and seeing this problem) - 4.3-rc1 has a ton of i915/drm changes, which result in a (not obviously harmful) call traces in kernel logs that end in drm_atomic_check_only() - traces ending in drm_atomic_check_only persist into official 4.3.0, though the full trace differs somewhat from 4.3rc1 - around 4.4-rc1 or 4.4-rc2 (I only have rc3 to test, but that has zero i915 changes in the commit log, so it must've been one one the former two) drm_atomic_check_only disappears and the thread initiator, drm_wait_one_vblank (along with "vblank wait timed out on crtc 0"), appears. - this persists up until at least ubuntu's 4.8.0</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>