<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [i915] GPU HANG: ecode 9:0:0xfffffffe (Team Fortress 2)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97968#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [i915] GPU HANG: ecode 9:0:0xfffffffe (Team Fortress 2)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97968">bug 97968</a>
from <span class="vcard"><a class="email" href="mailto:snrub@rkive.org" title="snrub@rkive.org">snrub@rkive.org</a>
</span></b>
<pre>
And the dmesg / debug output: (and uploading the new crashdump)
$ dmesg
....
[ 180.764441] [drm] GPU HANG: ecode 9:0:0x85dffffb, in MatQueue0 [4771],
reason: Engine(s) hung, action: reset
[ 180.764443] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 180.764444] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 180.764445] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 180.764445] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 180.764446] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 180.765925] drm/i915: Resetting chip after gpu hang
[ 181.793871] [drm] RC6 off
[ 190.793791] [drm] stuck on render ring
[ 190.799477] [drm] GPU HANG: ecode 9:0:0xfefffffe, in MatQueue0 [4771],
reason: Engine(s) hung, action: reset
[ 190.801365] drm/i915: Resetting chip after gpu hang
[ 192.793828] [drm] RC6 off</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>