<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [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#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [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 <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>(In reply to Jakub Okoński from <a href="show_bug.cgi?id=108820#c19">comment #19</a>) > It helps and I get reliable output, although I don't understand how the GLSL > caching option is relevant. Shader compiler is shared between Vulkan and GL drivers. > I use vulkan without VkPipelineCache, and yet it > is being cached anyway? Aren't pipeline objects higher level concept than shaders? Shader caching underneath should be invisible to the upper layers (except for performance and debug output), and not affect the resulting shader binaries (unless it's buggy). Lionel, do you think the shader assembly changes between working and non-working work group sizes has anything to do with the hangs? There's no code-flow difference, few instruction changes (shift -> mul, and -> 2x intmod) look innocent to me. -> seems that minimal reproduction code would help. :-)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>