<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BSW] Aztec Ruins GL version GPU hangs" href="https://bugs.freedesktop.org/show_bug.cgi?id=104636#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BSW] Aztec Ruins GL version GPU hangs" href="https://bugs.freedesktop.org/show_bug.cgi?id=104636">bug 104636</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>(In reply to Sagar Kamble from <a href="show_bug.cgi?id=104636#c2">comment #2</a>) > Created <a href="attachment.cgi?id=137126" name="attach_137126" title="error state for GPU hang with aztec ruins on GLK">attachment 137126</a> <a href="attachment.cgi?id=137126&action=edit" title="error state for GPU hang with aztec ruins on GLK">[details]</a> > error state for GPU hang with aztec ruins on GLK Hi Sagar, Based on your error state, it looks like your Mesa does not have commit 55a97db52347f62111a24715078c6035380d3e19, which ought to fix that hang. We shipped this fix in 18.0-rc1, but it looks like I forgot to get it included in the 17.3.x releases. I just nominated it [ <a href="https://lists.freedesktop.org/archives/mesa-stable/2018-March/007941.html">https://lists.freedesktop.org/archives/mesa-stable/2018-March/007941.html</a> ] so hopefully it'll hit 17.3.7. Your bug is different than Eero's. His is hanging after a BLORP operation. Yours was hanging on a compute shader. I can't reproduce Eero's BSW hang.</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>