<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - GPU hang "stuck on render ring" after resume on broadwell" href="https://bugs.freedesktop.org/show_bug.cgi?id=90342#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - GPU hang "stuck on render ring" after resume on broadwell" href="https://bugs.freedesktop.org/show_bug.cgi?id=90342">bug 90342</a> from <a class="email" href="mailto:an.inbox@free.fr" title="Jerome <an.inbox@free.fr>"> Jerome</a> <pre>Hi Ander, Thanks for the feedback. My starting issue is the exact same as Chaskiel, it's just that I then tried different kernels than him (keeping with Debian, testing 4.0.8 and then unstable 4.1.3) and ended up with the non systematic hard system lock on resume from suspend. I filled a Debian bug (794393) and was sent upstream here. Since then I read the "how to" here indeed, compiled the Intel DRM nightly kernel yesterday [1], and it looks fine: I went through 20 suspend / resume cycles without issue (usually I got the lock within 5 resumes typically). So yes, it looks like it's fixed upstream. Thanks [1] Tested with commit fb4572c00fadc1ac94816061e76c65b65607f66a / drm-intel-nightly: 2015y-08m-05d-15h-33m-02s UTC integration manifest Based on 4.2.0 RC5.</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> <li>You are the assignee for the bug.</li> </ul> </body> </html>