<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#c6">Comment # 6</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:conselvan2@gmail.com" title="Ander Conselvan de Oliveira <conselvan2@gmail.com>"> Ander Conselvan de Oliveira</a> <pre>(In reply to tuxgirl from <a href="show_bug.cgi?id=90342#c3">comment #3</a>) > What kernel version is this fixed in? I just got this error on 4.0.4-1-ARCH. > Unfortunately, the GPU crash dump is 0b, so I don't think there's much point > to me creating a new ticket. The GPU crash dump file is never 0b, but ls lies. Just do $ cat /sys/class/drm/card0/error | bz2 > error.bz2 once you get the GPU hang and attach that to a *new* ticket. (In reply to Jerome from <a href="show_bug.cgi?id=90342#c5">comment #5</a>) > I may have been too optimistic in <a href="show_bug.cgi?id=90342#c4">comment #4</a> unfortunately... > With kernel 4.0.8 the bug seems much less frequent (2 times over a dozen > suspend/resume). Unfortunately when it hangs it locks solid and requires a > forced power down. No log on reboot. Your symptoms are different so lets not jump to conclusions and assume it's the same bug. Please open a *new* ticket, following the instructions in <a href="https://01.org/linuxgraphics/documentation/how-report-bugs">https://01.org/linuxgraphics/documentation/how-report-bugs</a></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>