<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [ivb] GPU hang"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75883#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [ivb] GPU hang"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75883">bug 75883</a>
from <span class="vcard"><a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> <span class="fn">Kenneth Graunke</span></a>
</span></b>
<pre>This looks really strange. These look like Mesa (3D driver) batchbuffers
(based on the binding/sampler/constant/unit state sequences), but the sequence
before the hanging flush is:
1. VS related state.
2. GS disable state.
3. PS related state.
4. 3DSTATE_VERTEX_BUFFERS
5. 3DPRIMITIVE.
But, as far as I can tell, Mesa /always/ emits 3DSTATE_VERTEX_ELEMENTS after
3DSTATE_VERTEX_BUFFERS. It's always done in the same function, directly one
after the next. So, I'm not sure what to make of this.
What version of Mesa are you using? It's clearly not 10.1, but I'm not sure
how far back it is.</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>