<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 9:0:0xef9ffffd, in chrome [1777], reason: Ring hung, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100614">100614</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU HANG: ecode 9:0:0xef9ffffd, in chrome [1777], reason: Ring hung, action: reset
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</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>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/DRI/i915
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>ravi4tablet@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=130752" name="attach_130752" title="GPU crash dump saved to /sys/class/drm/card0/error">attachment 130752</a> <a href="attachment.cgi?id=130752&action=edit" title="GPU crash dump saved to /sys/class/drm/card0/error">[details]</a></span>
GPU crash dump saved to /sys/class/drm/card0/error
Encountered GPU hang on Chromebook while doing Google hangouts + video(youtube)
+ few (5) tabs opened simultaneously. Reproducility is nearly 20% but requires
overnight to reproduce this issue.
GPU crash dump saved to /sys/class/drm/card0/error and logs are attached.
Kernel log says:
2017-03-26T15:51:27.709098-07:00 INFO kernel: [ 8104.736419] [drm] stuck on
render ring
2017-03-26T15:51:27.709145-07:00 INFO kernel: [ 8104.737420] [drm] GPU HANG:
ecode 9:0:0xef9ffffd, in chrome [1869], reason: Ring hung, action: reset
2017-03-26T15:51:27.709150-07:00 INFO kernel: [ 8104.737439] [drm] GPU hangs
can indicate a bug anywhere in the entire gfx stack, including userspace.
Few more details:
>From "change_card0_drm.20170406.193114.0.log" attachment, I saw it suffered GPU
command (MI_STORE_DATA_IMM) blocked in render ring and guess some batch buffers
from mesa cause this issue.
...
0x01028a90: 0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0x01028a94: 0x00101001: destination address
0x01028a98: 0x00000080: immediate dword low
0x01028a9c: 0x00000000: immediate dword high
0x01028aa8: 0x10400002: MI_STORE_DATA_IMM <------------blocked
0x01028aac: 0x000020c0: dword 1
0x01028ab0: 0x00000000: dword 2
0x01028ab4: 0x0014d95b: dword 3
0x01028ab8: 0x01000000: MI_USER_INTERRUPT
0x01028abc: 0x00000000: MI_NOOP
0x01028ac0: 0x00000000: MI_NOOP
0x01028ac4: 0x00000000: MI_NOOP
0x01028ac8: 0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0x01028acc: 0x00000000: destination address
0x01028ad0: 0x00000000: immediate dword low
0x01028ad4: 0x00000000: immediate dword high
...</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>