<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 8:0:0x85dffffb, in steam [3539], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=93166#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 8:0:0x85dffffb, in steam [3539], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=93166">bug 93166</a> from <a class="email" href="mailto:bugs.freedesktop.org@hypfer.de" title="Sören Beye <bugs.freedesktop.org@hypfer.de>"> Sören Beye</a> <pre>This is NOT fixed with Linux 4.7-rc3 Jun 15 13:52:43 ishimura kernel: [ 654.787660] [drm] stuck on render ring Jun 15 13:52:43 ishimura kernel: [ 654.788282] [drm] GPU HANG: ecode 8:0:0x85dffffb, in chrome [3661], reason: Engine(s) hung, action: reset Jun 15 13:52:43 ishimura kernel: [ 654.788284] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jun 15 13:52:43 ishimura kernel: [ 654.788285] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jun 15 13:52:43 ishimura kernel: [ 654.788286] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jun 15 13:52:43 ishimura kernel: [ 654.788287] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jun 15 13:52:43 ishimura kernel: [ 654.788288] [drm] GPU crash dump saved to /sys/class/drm/card0/error Jun 15 13:52:43 ishimura kernel: [ 654.789653] drm/i915: Resetting chip after gpu hang Crashdump follows</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>