<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 - [SKL] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [956], reason: Hang on render ring, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99536">99536</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[SKL] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [956], reason: Hang on render ring, action: reset
</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>ametzler@bebt.de
</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=129144" name="attach_129144" title="/sys/class/drm/card0/error">attachment 129144</a> <a href="attachment.cgi?id=129144&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
Hello,
Shortly after startup my xserver hangs, and shows some artifacts. After a
couple of seconds it starts usually working again. Today it seem to have
crashed the xserver.
Jän 25 17:38:06 argenau kernel: [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
[956], reason: Hang on render ring, action: reset
Jän 25 17:38:06 argenau kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Jän 25 17:38:06 argenau kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Jän 25 17:38:06 argenau kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Jän 25 17:38:06 argenau kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
Jän 25 17:38:06 argenau kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Jän 25 17:38:06 argenau kernel: drm/i915: Resetting chip after gpu hang
Jän 25 17:38:06 argenau kernel: [drm] RC6 on
Jän 25 17:38:06 argenau kernel: [drm] GuC firmware load skipped
Jän 25 17:38:17 argenau kernel: drm/i915: Resetting chip after gpu hang
Jän 25 17:38:17 argenau kernel: [drm] RC6 on
Jän 25 17:38:17 argenau kernel: [drm] GuC firmware load skipped
This is on Debian/testing on Skylake (Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz)
ametzler@argenau:~$ uname -a
Linux argenau 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64 GNU/Linux
libdrm-intel1:amd64 2.4.74-1
libegl1-mesa:amd64 13.0.3-1
libgl1-mesa-dri:amd64 13.0.3-1
libgl1-mesa-glx:amd64 13.0.3-1
libglapi-mesa:amd64 13.0.3-1
libglu1-mesa:amd64 9.0.0-2.1
libwayland-egl1-mesa:amd64 13.0.3-1
mesa-utils 8.3.0-3
mesa-vdpau-drivers:amd64 13.0.3-1
xorg 1:7.7+18
xorg-docs-core 1:1.7.1-1
xserver-xorg 1:7.7+18
xserver-xorg-core 2:1.19.0-3
xserver-xorg-input-evdev 1:2.10.4-1+b1
xserver-xorg-video-intel 2:2.99.917+git20161206-1</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>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>