<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [g4x] Desktop hang with drm:drm_atomic_helper_commit_cleanup_done "flip_done timed out"" href="https://bugs.freedesktop.org/show_bug.cgi?id=98810#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [g4x] Desktop hang with drm:drm_atomic_helper_commit_cleanup_done "flip_done timed out"" href="https://bugs.freedesktop.org/show_bug.cgi?id=98810">bug 98810</a> from <a class="email" href="mailto:cwillu@cwillu.com" title="Carey Underwood <cwillu@cwillu.com>"> Carey Underwood</a> <pre>(In reply to willma from <a href="show_bug.cgi?id=98810#c11">comment #11</a>) > I think this report might be a duplicate of <a class="bz_bug_link bz_status_NEW " title="NEW - [skl dp-mst] oops in atomic commit" href="show_bug.cgi?id=96781">bug 96781</a> It's most definitely _related_ to that bug (I compiled a 4.9 with "drm/i915: Roll out the helper nonblock tracking" reverted last week, and it removes the hangs), but I'd be surprised if it was the same exact issue, at least insofar as the issue is more specific than "the atomic config update code was merged before it was ready". As the likelihood of that patch being reverted upstream is negligible, separate bugs for each of the ensuing issues will be important for the developers to keep track of what is and isn't broken.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>