<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 - [i965] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [1674], reason: Hang on render ring, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101041">101041</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[i965] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [1674], 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>cdouglass@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=131354" name="attach_131354" title="/sys/class/drm/card0/error">attachment 131354</a> <a href="attachment.cgi?id=131354&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
I encounter a hang during which X does not respond to key or mouse events and
recovery some seconds later. The following messages are from a tail of dmesg.
```
[ 1204.829037] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [1674], reason:
Hang on render ring, action: reset
[ 1204.829040] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 1204.829041] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 1204.829042] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 1204.829043] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 1204.829044] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1205.136582] drm/i915: Resetting chip after gpu hang
[ 1215.140428] drm/i915: Resetting chip after gpu hang
[ 1413.363513] perf: interrupt took too long (4910 > 4908), lowering
kernel.perf_event_max_sample_rate to 40500
[ 1425.134080] drm/i915: Resetting chip after gpu hang
[ 1437.128358] drm/i915: Resetting chip after gpu hang
[ 1449.123365] drm/i915: Resetting chip after gpu hang
[ 1459.143450] drm/i915: Resetting chip after gpu hang
[ 1462.794884] [drm] HPD interrupt storm detected on connector VGA-1: switching
from hotplug detection to polling
```
Thinkpad R16
uname -a
Linux thicky 4.9.0-0.bpo.2-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.18-1~bpo8+1
(2017-04-10) x86_64 GNU/Linux</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>