<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 4:0:0x8644f8fe, in chrome [12486], reason: Ring hung, action: rese"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90833">90833</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason: Ring hung, action: rese
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>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>sultbab@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=116271" name="attach_116271" title="/sys/class/drm/card0/error">attachment 116271</a> <a href="attachment.cgi?id=116271&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
[13001.000054] [drm] stuck on render ring
[13001.001025] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason:
Ring hung, action: reset
[13001.001028] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[13001.001030] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[13001.001031] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[13001.001033] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[13001.001035] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[13001.252277] drm/i915: Resetting chip after gpu hang
[13016.000105] [drm] stuck on render ring
[13016.001081] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason:
Ring hung, action: reset
[13016.028115] drm/i915: Resetting chip after gpu hang
[13021.988127] [drm] stuck on render ring
[13021.989076] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason:
Ring hung, action: reset
[13022.016069] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast,
banning!
[13022.016147] drm/i915: Resetting chip after gpu hang
[13036.000124] [drm] stuck on render ring
[13036.001073] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13631], reason:
Ring hung, action: reset
[13036.032122] drm/i915: Resetting chip after gpu hang
[13041.988129] [drm] stuck on render ring
[13041.989118] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13631], reason:
Ring hung, action: reset
[13042.020095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast,
banning!
[13042.020177] drm/i915: Resetting chip after gpu hang
[13047.988115] [drm] stuck on render ring
[13047.989089] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13652], reason:
Ring hung, action: reset
[13048.020177] drm/i915: Resetting chip after gpu hang
[13054.000052] [drm] stuck on render ring
[13054.001020] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13652], reason:
Ring hung, action: reset
[13054.028086] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast,
banning!
[13054.028164] drm/i915: Resetting chip after gpu hang</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>