<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:yann.argotti@intel.com" title="yann <yann.argotti@intel.com>"> <span class="fn">yann</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SNB] GPU HANG: ecode 6:0:0x85fffffc, in compiz [17500], reason: Hang on render ring, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99566">bug 99566</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>yann.argotti@intel.com
</td>
<td>ted@digistate.nl
</td>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>[gen6] GPU hang in compiz
</td>
<td>[SNB] GPU HANG: ecode 6:0:0x85fffffc, in compiz [17500], reason: Hang on render ring, action: reset
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SNB] GPU HANG: ecode 6:0:0x85fffffc, in compiz [17500], reason: Hang on render ring, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99566#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SNB] GPU HANG: ecode 6:0:0x85fffffc, in compiz [17500], reason: Hang on render ring, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99566">bug 99566</a>
from <span class="vcard"><a class="email" href="mailto:yann.argotti@intel.com" title="yann <yann.argotti@intel.com>"> <span class="fn">yann</span></a>
</span></b>
<pre>According to mesa engineers, mesa only emits 3DSTATE_VERTEX_ELEMENTS on-demand
right before 3DPRIMITIVE.
Chris has changed SNA to emit a dummy primitive between VertexElements in
4acd4a7d3d2f41227022fa7581cfb85a0b124eae in xf86-video-intel (thanks to
<a href="https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=4acd4a7d3d2f41227022fa7581cfb85a0b124eae">https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=4acd4a7d3d2f41227022fa7581cfb85a0b124eae</a>)
So I recommend to update to latest version of xf86-video-intel since fix should
be already in and mark as REOPENED if you can reproduce (and attach fresh gpu
error dump) and RESOLVED/* if you cannot reproduce.
An alternate solution is to use Glamor/modesetting, but 1st try this one.
========================
*Details:
- Kernel: 4.8.0-34-generic
- Platform: SandyBridge (PCI ID: 0x0116, PCI Revision: 0x09, PCI Subsystem:
144d:c0b2)
- Mesa: [Please confirm your version]
- xf86-video-intel: [Please confirm your version]
>From this error dump, hung is happening in render ring batch with active head
at 0x7a09d574, with 0x7a000003 (PIPE_CONTROL) as IPEHR.
Batch extract (around 0x7a09d574):
0x7a09d52c: 0x78090005: 3DSTATE_VERTEX_ELEMENTS
0x7a09d530: 0x02000000: buffer 0: valid, type 0x0000, src offset 0x0000
bytes
0x7a09d534: 0x11110000: (X, Y, Z, W), dst offset 0x00 bytes
0x7a09d538: 0x02000010: buffer 0: valid, type 0x0000, src offset 0x0010
bytes
0x7a09d53c: 0x11110000: (X, Y, Z, W), dst offset 0x00 bytes
0x7a09d540: 0x02000020: buffer 0: valid, type 0x0000, src offset 0x0020
bytes
0x7a09d544: 0x11110000: (X, Y, Z, W), dst offset 0x00 bytes
0x7a09d548: 0x7b001804: 3DPRIMITIVE: tri fan sequential
0x7a09d54c: 0x00000004: vertex count
0x7a09d550: 0x00000000: start vertex
0x7a09d554: 0x00000001: instance count
0x7a09d558: 0x00000000: start instance
0x7a09d55c: 0x00000000: index bias
0x7a09d560: 0x7a000003: PIPE_CONTROL
0x7a09d564: 0x00100002: no write, cs stall, stall at scoreboard,
0x7a09d568: 0x00000000: destination address
0x7a09d56c: 0x00000000: immediate dword low
0x7a09d570: 0x00000000: immediate dword high
0x7a09d574: 0x7a000003: PIPE_CONTROL
0x7a09d578: 0x00004000: qword write,
0x7a09d57c: 0x00b57004: destination address
0x7a09d580: 0x00000000: immediate dword low
0x7a09d584: 0x00000000: immediate dword high
0x7a09d588: 0x780e0002: 3DSTATE_CC_STATE_POINTERS
0x7a09d58c: 0x00007c01: blend change 1
0x7a09d590: 0x00000000: depth stencil change 0
0x7a09d594: 0x00000000: cc change 0</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>