<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 - [KBL] GPU HANG: ecode 9:0:0x87d6fffe, in Xorg [25978], reason: Engine(s) hung, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100870">100870</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[KBL] GPU HANG: ecode 9:0:0x87d6fffe, in Xorg [25978], 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>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>simon.deziel@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=131130" name="attach_131130" title="/sys/class/drm/card0/error">attachment 131130</a> <a href="attachment.cgi?id=131130&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
I don't exactly know what happened but I found this in my logs:
Apr 28 09:29:45 simon-laptop kernel: [140726.749554] [drm] stuck on render ring
Apr 28 09:29:45 simon-laptop kernel: [140726.749859] [drm] GPU HANG: ecode
9:0:0x87d6fffe, in Xorg [25978], reason: Engine(s) hung, action: reset
Apr 28 09:29:45 simon-laptop kernel: [140726.749861] [drm] GPU hangs can
indicate a bug anywhere in the entire gfx stack, including userspace.
Apr 28 09:29:45 simon-laptop kernel: [140726.749862] [drm] Please file a _new_
bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Apr 28 09:29:45 simon-laptop kernel: [140726.749863] [drm] drm/i915 developers
can then reassign to the right component if it's not a kernel issue.
Apr 28 09:29:45 simon-laptop kernel: [140726.749864] [drm] The gpu crash dump
is required to analyze gpu hangs, so please always attach it.
Apr 28 09:29:45 simon-laptop kernel: [140726.749866] [drm] GPU crash dump saved
to /sys/class/drm/card0/error
Apr 28 09:29:45 simon-laptop kernel: [140726.751659] drm/i915: Resetting chip
after gpu hang
Apr 28 09:29:47 simon-laptop kernel: [140728.749834] [drm] RC6 on
I searched my logs for previous GPU hangs and found another case on April 1st
with the same "signature":
Apr 1 21:07:25 simon-laptop kernel: [ 3281.489363] [drm] GPU HANG: ecode
9:0:0x87d6fffe, in Xorg [4906], reason: Engine(s) hung, action: reset
So not a frequent issue but I thought I should still report it.
Machine informations:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="<a href="http://www.ubuntu.com/">http://www.ubuntu.com/</a>"
SUPPORT_URL="<a href="http://help.ubuntu.com/">http://help.ubuntu.com/</a>"
BUG_REPORT_URL="<a href="http://bugs.launchpad.net/ubuntu/">http://bugs.launchpad.net/ubuntu/</a>"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
$ uname -a
Linux simon-laptop 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
My external display is connected through VGA.</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>