<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - NIR GPU HANG: ecode 5:0:0x95defffc"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88617#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - NIR GPU HANG: ecode 5:0:0x95defffc"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88617">bug 88617</a>
from <span class="vcard"><a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> <span class="fn">Ian Romanick</span></a>
</span></b>
<pre>(In reply to dimon from <a href="show_bug.cgi?id=88617#c3">comment #3</a>)
<span class="quote">> (In reply to Matt Turner from <a href="show_bug.cgi?id=88617#c1">comment #1</a>)
> > We'd need
> >
> > - INTEL_DEBUG=fs output
> > - to know what generation of hardware you're using
> > - what application you were using
> > - a bisection would be great
> >
> > But I'm not even sure that we're ready to start taking bug reports on NIR.
>
> - INTEL_DEBUG=fs output attached
> - Ironlake
> - quakelive on wine
> - seems to be this commit: a5ca86a9833d6fd57ee609d8d1e630dc66ebd371</span >
Which is "i965/nir: Enable SIMD16 support in the NIR FS backend." This
probably means that we're generating a SIMD16 shader on ILK that is invalid on
that hardware.
Can you provide the output of 'INTEL_DEBUG=fs' with and without INTEL_USE_NIR?
That should help narrow down which shader is incorrectly getting SIMD16.</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>