<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106342#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106342">bug 106342</a>
from <span class="vcard"><a class="email" href="mailto:thiago@kde.org" title="Thiago Macieira <thiago@kde.org>"> <span class="fn">Thiago Macieira</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=140944" name="attach_140944" title="card0_error 2018-07-30">attachment 140944</a> <a href="attachment.cgi?id=140944&action=edit" title="card0_error 2018-07-30">[details]</a></span>
card0_error 2018-07-30
4.17.6
[200509.348277] [drm] GPU HANG: ecode 9:0:0xa3edbc82, in chrome [4770], reason:
Hang on rcs0, action: reset
[200509.348279] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[200509.348280] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[200509.348280] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[200509.348281] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[200509.348282] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[200509.348297] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[200510.549451] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[200510.549500] i915 0000:00:02.0: Resetting chip after gpu hang
[200511.750749] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[200513.061331] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[200514.369250] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[200514.474645] i915 0000:00:02.0: Failed to reset chip
[200515.646641] i915 0000:00:02.0: i915_reset_device timed out, cancelling all
in-flight rendering.
[200515.710684] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>