<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 0:0x9f47f9fd, in chrome [10834], reason: Ring hung, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93287">93287</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU HANG: ecode 0:0x9f47f9fd, in chrome [10834], reason: Ring hung, 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>gf@riseup.net
</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=120400" name="attach_120400" title="GPU crash dump /sys/class/drm/card0/error">attachment 120400</a> <a href="attachment.cgi?id=120400&action=edit" title="GPU crash dump /sys/class/drm/card0/error">[details]</a></span>
GPU crash dump /sys/class/drm/card0/error
dmesg just told me:
[ 675.816055] [drm] stuck on render ring
[ 675.817138] [drm] GPU HANG: ecode 0:0x9f47f9fd, in chrome [10834], reason:
Ring hung, action: reset
[ 675.817140] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 675.817141] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 675.817143] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 675.817144] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 675.817145] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 675.817288] [drm:i915_reset] *ERROR* Failed to reset chip: -19
[ 676.055584] chrome[12349]: segfault at 1f8 ip 00007fa272c4ae4f sp
00007ffc1dff9240 error 4 in i965_dri.so[7fa2728f5000+51e000]
[ 676.150304] chrome[12357]: segfault at 1f8 ip 00007f138a913e4f sp
00007ffe133a63f0 error 4 in i965_dri.so[7f138a5be000+51e000]
The mentioned gpu crash dump is attached.
Involved software:
# uname -a
Linux debian.local 3.16.0-0.bpo.4-amd64 #1 SMP Debian
3.16.7-ckt11-1+deb8u6~bpo70+1 (2015-11-11) x86_64 GNU/Linux
# cat /etc/debian_version
7.9
# dpkg -l | grep intel
ii libdrm-intel1:amd64 2.4.58-2
ii xserver-xorg-video-intel 2:2.21.15-2+b2
# dpkg -l | grep chrome
ii google-chrome-stable 47.0.2526.73-1
If I'm able to debug or you need further information, please tell me.
Thanks for your work and all the best,
Georg</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 on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>