<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Bisected: cc2d0e6][HSW] "GPU HANG" msg after autologin to gnome-session"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96878#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Bisected: cc2d0e6][HSW] "GPU HANG" msg after autologin to gnome-session"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96878">bug 96878</a>
from <span class="vcard"><a class="email" href="mailto:arek.rusi@gmail.com" title="Arek Ruśniak <arek.rusi@gmail.com>"> <span class="fn">Arek Ruśniak</span></a>
</span></b>
<pre>And it is all happen after this:
cc2d0e64c0b10884bc12d80018b622911e8b152f is the first bad commit
commit cc2d0e64c0b10884bc12d80018b622911e8b152f
Author: Topi Pohjolainen <<a href="mailto:topi.pohjolainen@intel.com">topi.pohjolainen@intel.com</a>>
Date: Fri May 20 11:15:35 2016 +0300
i965/blorp/gen7+: Stop trashing push constant allocation
Packet 3DSTATE_CONSTANT_PS is still emitted explicitly as ps stage
itself is enabled and hardware may try to prefetch constants from
the buffer. From the BSpec: 3D Pipeline - Windower -
3DSTATE_PUSH_CONSTANT_ALLOC_PS
"Specifies the size of the PS constant buffer. This value will
determine the amount of data the command stream can pre-fetch
before the buffer is full."
This is not possible on gen6. From the BSpec about 3DSTATE_CONSTANT_PS:
"This packet must be followed by WM_STATE."
Binding table emissions for stages other than PS can be now dropped,
they were only needed for the 3DSTATE_CONSTANT_XS to be effective:
From the BSpec:
"The 3DSTATE_CONSTANT_* command is not committed to the shader unit
until the corresponding (same shader) 3DSTATE_BINDING_TABLE_POINTER_*
command is parsed."
Signed-off-by: Topi Pohjolainen <<a href="mailto:topi.pohjolainen@intel.com">topi.pohjolainen@intel.com</a>>
Reviewed-by: Jason Ekstrand <<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>></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>