<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111812#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111812">bug 111812</a>
from <span class="vcard"><a class="email" href="mailto:kenny@panix.com" title="Kenneth C <kenny@panix.com>"> <span class="fn">Kenneth C</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=145638" name="attach_145638" title="/sys/class/drm/card0/error">attachment 145638</a> <a href="attachment.cgi?id=145638&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
This was encouraging; I'm running the latest drm-tip and this time, it managed
to recover:
----
Oct 4 00:32:54 hp-x360n kernel: [10308.045206] i915 0000:00:02.0: GPU HANG:
ecode 9:1:0x00000000, hang on rcs0
Oct 4 00:32:54 hp-x360n kernel: [10308.045210] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Oct 4 00:32:54 hp-x360n kernel: [10308.045212] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Oct 4 00:32:54 hp-x360n kernel: [10308.045213] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Oct 4 00:32:54 hp-x360n kernel: [10308.045214] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Oct 4 00:32:54 hp-x360n kernel: [10308.045216] GPU crash dump saved to
/sys/class/drm/card0/error
Oct 4 00:32:54 hp-x360n kernel: [10308.046223] i915 0000:00:02.0: Resetting
rcs0 for hang on rcs0
Oct 4 00:32:54 hp-x360n kernel: [10308.046988] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Oct 4 00:32:54 hp-x360n kernel: [10308.047094] i915 0000:00:02.0: Resetting
chip for hang on rcs0
Oct 4 00:32:54 hp-x360n kernel: [10308.048105] [drm] GuC communication stopped
Oct 4 00:32:54 hp-x360n kernel: [10308.048847] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Oct 4 00:32:54 hp-x360n kernel: [10308.049582] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Oct 4 00:32:54 hp-x360n kernel: [10308.051162] [drm] GuC communication enabled
Oct 4 00:32:54 hp-x360n kernel: [10308.051208] i915 0000:00:02.0: GuC firmware
i915/kbl_guc_33.0.0.bin version 33.0 submission:disabled
Oct 4 00:32:54 hp-x360n kernel: [10308.051212] i915 0000:00:02.0: HuC firmware
i915/kbl_huc_4.0.0.bin version 4.0 authenticated:yes
Oct 4 00:33:02 hp-x360n kernel: [10316.044654] i915 0000:00:02.0: Resetting
rcs0 for hang on rcs0
Oct 4 00:33:10 hp-x360n kernel: [10324.044128] i915 0000:00:02.0: Resetting
rcs0 for hang on rcs0
----
Error report is attached.</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>