<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [SKL] (recoverable) GPU hangs in benchmarks using compute shaders"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108820">bug 108820</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;">Resolution</td>
<td>---
</td>
<td>WORKSFORME
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [SKL] (recoverable) GPU hangs in benchmarks using compute shaders"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108820#c50">Comment # 50</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [SKL] (recoverable) GPU hangs in benchmarks using compute shaders"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108820">bug 108820</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=108820#c46">comment #46</a>)
<span class="quote">> (In reply to Eero Tamminen from <a href="show_bug.cgi?id=108820#c45">comment #45</a>)
> > Added GPU hang tracking so that I can catch these.
>
> Every few days there's recoverable GPU hang on some SKL or BXT device in
> GfxBench Manhattan 3.1, CarChase or AztecRuins.</span >
Last recoverable GfxBench i965 hangs were months ago, with older (5.0 or
realier) kernels.
I've also seen twice Heaven hangs on SKL in June, but not since then.
-> Marking this as WORKSFORME (as I don't know what was fixed).
(In reply to Jakub Okoński from <a href="show_bug.cgi?id=108820#c49">comment #49</a>)
<span class="quote">> I double checked the SPIR-V specification, and I think this shader is
> invalid.</span >
If you think there's a valid issue after all with your compute shaders, could
you file a separate issue about that?
<span class="quote">> > 3.32.20 OpControlBarrier
> > This instruction is only guaranteed to work correctly if placed strictly
> > within uniform control flow within Execution. This ensures that if any
> > invocation executes it, all invocations will execute it.
> > If placed elsewhere, an invocation may stall indefinitely.
>
> I guess RADV and/or AMD hardware can handle this case? Or maybe it's
> compiled differently?</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>