<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#c9">Comment # 9</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>GPU hang on 4.13. Couldn't capture the card0 error log this time because it happened while no other networking was available. How many more hangs are necessary? [drm] GPU HANG: ecode 9:0:0x2296f923, in kmail [56266], reason: Hang on rcs0, action: reset [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [drm] GPU crash dump saved to /sys/class/drm/card0/error drm/i915: Resetting chip after gpu hang [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5</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>