<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:0x84dfbefc"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110277">110277</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU hang ecode 9:0:0x84dfbefc
</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>bugtracker@othram.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=143802" name="attach_143802" title="output of lspci -vvn and /sys/class/drm/card0/error">attachment 143802</a> <a href="attachment.cgi?id=143802&action=edit" title="output of lspci -vvn and /sys/class/drm/card0/error">[details]</a></span>
output of lspci -vvn and /sys/class/drm/card0/error
First bug report in a loooong time, so please forgive any novice mistakes.
About once a week or so I will receive the following log entries:
18.586285] [drm] GPU HANG: ecode 9:0:0x84dfbefc, in Xorg [4800], reason: Hang
on render ring, action: reset
Mar 28 10:37:35 ispy kernel: [151918.586288] [drm] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Mar 28 10:37:35 ispy kernel: [151918.586289] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 28 10:37:35 ispy kernel: [151918.586290] [drm] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Mar 28 10:37:35 ispy kernel: [151918.586292] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Mar 28 10:37:35 ispy kernel: [151918.586293] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Mar 28 10:37:35 ispy kernel: [151918.586361] drm/i915: Resetting chip after gpu
hang
Mar 28 10:37:47 ispy kernel: [151930.617861] drm/i915: Resetting chip after gpu
hang
The only consistent action that I can correlate is this always happens after
engaging xscreensaver. It does not appear to be related to a particular
screensaver though (I have my system set to pick a random one every time). I
have never caught it in the act. My first clue is returning to the system to
find that my session has been logged out and I am presented with the login
screen. My system is a Librem 15, V3. Additional information:
# uname -a
Linux mybox 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64
GNU/Linux
# cat /etc/debian_version
9
# cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux ascii"
NAME="Devuan GNU/Linux"
ID=devuan
ID_LIKE=debian
HOME_URL="<a href="https://www.devuan.org/">https://www.devuan.org/</a>"
SUPPORT_URL="<a href="https://devuan.org/os/community">https://devuan.org/os/community</a>"
BUG_REPORT_URL="<a href="https://bugs.devuan.org/">https://bugs.devuan.org/</a>"
contents of lspci -vvn attached, as is /sys/class/drm/card0/error. I will be
happy to provide any additional requested information.
KR
Patrick Krepps</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>