<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [drm] GPU HANG: ecode 9:0:0x85dffffd, in chrome [18418], reason: hang on rcs0, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108717#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [drm] GPU HANG: ecode 9:0:0x85dffffd, in chrome [18418], reason: hang on rcs0, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108717">bug 108717</a>
from <span class="vcard"><a class="email" href="mailto:mail@muradm.net" title="muradm <mail@muradm.net>"> <span class="fn">muradm</span></a>
</span></b>
<pre>Just happened again, after enable_guc is removed.
kernel: [drm] GPU HANG: ecode 9:0:0x87f5fff9, in chrome [1909], reason: hang
on rcs0, action: reset
kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack,
including userspace.
kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against
DRI -> DRM/Intel
kernel: [drm] drm/i915 developers can then reassign to the right component if
it's not a kernel issue.
kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please
always attach it.
kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
I'm adding drmi915kblcrash_no_guc.dump also.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>