<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - gpu hang ecode 9:0:0x85df7eff, in gnome-shell, reason: Engine(s) hung, action reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96280">96280</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>gpu hang ecode 9:0:0x85df7eff, in gnome-shell, reason: Engine(s) hung, action reset
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>saul.stjohn@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=124182" name="attach_124182" title="gpu crash dump">attachment 124182</a> <a href="attachment.cgi?id=124182&action=edit" title="gpu crash dump">[details]</a></span>
gpu crash dump
X froze up and I was worried because I had an unsaved document in VSCode, but
it started working again when I switched VTs to a text console and back. dmesg
says this:
[171847.897508] [drm] stuck on render ring
[171847.898299] [drm] GPU HANG: ecode 9:0:0x85df7eff, in gnome-shell [1340],
reason: Engine(s) hung, action: reset
[171847.898300] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[171847.898301] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[171847.898302] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[171847.898302] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[171847.898303] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[171847.900998] drm/i915: Resetting chip after gpu hang
[171848.905509] [drm] RC6 on
[171857.873462] [drm] stuck on render ring
[171857.874186] [drm] GPU HANG: ecode 9:0:0x87f93ff9, in code [7592], reason:
Engine(s) hung, action: reset
[171857.876842] drm/i915: Resetting chip after gpu hang
[171859.873489] [drm] RC6 on
[171867.885616] [drm] stuck on render ring
[171867.886320] [drm] GPU HANG: ecode 9:0:0x85dffeff, in gnome-shell [1340],
reason: Engine(s) hung, action: reset
[171867.887615] drm/i915: Resetting chip after gpu hang
[171869.885604] [drm] RC6 on
[171877.909446] [drm] stuck on render ring
[171877.910100] [drm] GPU HANG: ecode 9:0:0x87f93ff9, in code [7592], reason:
Engine(s) hung, action: reset
[171877.911445] drm/i915: Resetting chip after gpu hang
[171879.909671] [drm] RC6 on
...so I did.</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 on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>