<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 6:0:0x84fefffc, in gnome-shell [1910], reason: Ring hung, action: reset" error in syslog"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96758">96758</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>"GPU HANG: ecode 6:0:0x84fefffc, in gnome-shell [1910], reason: Ring hung, action: reset" error in syslog
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (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>cooks.go.hungry@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=124819" name="attach_124819" title="GPU_Hang_Crash_Dump.gz">attachment 124819</a> <a href="attachment.cgi?id=124819&action=edit" title="GPU_Hang_Crash_Dump.gz">[details]</a></span>
GPU_Hang_Crash_Dump.gz
I was investigating this bug <a href="https://bugzilla.gnome.org/show_bug.cgi?id=767180">https://bugzilla.gnome.org/show_bug.cgi?id=767180</a>
(don't know if there will be any relevance, but thought I would mention it just
in case) and came across the following messages in my syslog:
Jun 30 22:52:18 <Computer-Name> kernel: [16090.619806] [drm] stuck on
render ring
Jun 30 22:52:18 <Computer-Name> kernel: [16090.620319] [drm] GPU HANG:
ecode 6:0:0x84fefffc, in gnome-shell [1910], reason: Ring hung, action: reset
Jun 30 22:52:18 <Computer-Name> kernel: [16090.620321] [drm] GPU hangs can
indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 30 22:52:18 <Computer-Name> kernel: [16090.620322] [drm] Please file a
_new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 30 22:52:18 <Computer-Name> kernel: [16090.620323] [drm] drm/i915
developers can then reassign to the right component if it's not a kernel issue.
Jun 30 22:52:18 <Computer-Name> kernel: [16090.620324] [drm] The gpu crash
dump is required to analyze gpu hangs, so please always attach it.
Jun 30 22:52:18 <Computer-Name> kernel: [16090.620325] [drm] GPU crash dump
saved to /sys/class/drm/card0/error
Jun 30 22:52:18 <Computer-Name> kernel: [16090.622412] drm/i915: Resetting
chip after gpu hang
Jun 30 22:52:24 <Computer-Name> kernel: [16096.656115] [drm] stuck on
render ring
Jun 30 22:52:24 <Computer-Name> kernel: [16096.656640] [drm] GPU HANG:
ecode 6:0:0x84fefffc, in gnome-shell [1910], reason: Ring hung, action: reset
Jun 30 22:52:24 <Computer-Name> kernel: [16096.658736] drm/i915: Resetting
chip after gpu hang
So here I am. I am running Ubuntu GNOME 16.04 64-bit with GNOME 3.20 and Linux
kernel version 4.4.0-28-generic. My machine is a Lenovo B590 laptop. I have
attached the crash dump as instructed.</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>