<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL] (recoverable) GPU hangs in benchmarks using compute shaders with drm-tip v4.20-rc kernels"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108820#c34">Comment # 34</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL] (recoverable) GPU hangs in benchmarks using compute shaders with drm-tip v4.20-rc kernels"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108820">bug 108820</a>
from <span class="vcard"><a class="email" href="mailto:jakub@okonski.org" title="Jakub Okoński <jakub@okonski.org>"> <span class="fn">Jakub Okoński</span></a>
</span></b>
<pre>I hope I'm not going crazy, but on 5.0-rc5 with mesa 19.0-rc2, the goal post
has moved to 32 shader invocations in a local group. So <a href="show_bug.cgi?id=108820#c12">comment #12</a> is outdated
when it comes to the number. Otherwise, the behavior is the same, it's the
combination of > 32 items AND conditional early return statements that cause
the hang.
So in the end I only have one repro case I think, it's this:
#version 450
layout (local_size_x = 33) in;
void main() {
if (gl_GlobalInvocationID.x >= 20) {
return;
}
barrier();
}
>From here, I can do any of:
1) comment out barrier() call
2) comment out the return statement (the if can stay)
3) decrease local_size_x to 32
And it will prevent the crash from happening. The drm/card0 error that I
uploaded on February 5th is the only crash I can provide.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>