<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 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=101991#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=101991">bug 101991</a> from <a class="email" href="mailto:thiago@kde.org" title="Thiago Macieira <thiago@kde.org>"> Thiago Macieira</a> <pre>Created <a href="attachment.cgi?id=134351" name="attach_134351" title="card0_error 2017-09-19">attachment 134351</a> <a href="attachment.cgi?id=134351&action=edit" title="card0_error 2017-09-19">[details]</a> card0_error 2017-09-19 New crash. [314545.822232] asynchronous wait on fence i915:X[4343]/0:5ff4fe timed out [314547.720790] [drm] GPU HANG: ecode 9:0:0x8b0152ff, in chrome [92664], reason: Hang on rcs, action: reset [314547.720792] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [314547.720792] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [314547.720793] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [314547.720793] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [314547.720794] [drm] GPU crash dump saved to /sys/class/drm/card0/error [314547.720847] drm/i915: Resetting chip after gpu hang [314548.426677] [drm:gen8_reset_engines [i915]] *ERROR* rcs: reset request timeout [314548.426736] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5 This was 4.12.11. That was the last 4.12 crash, I am now running 4.13.</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>