<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [!semaphore] Gpu hang recovery fails, causing reset loop" href="https://bugs.freedesktop.org/show_bug.cgi?id=98104#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [!semaphore] Gpu hang recovery fails, causing reset loop" href="https://bugs.freedesktop.org/show_bug.cgi?id=98104">bug 98104</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=98104#c4">comment #4</a>) > So far, I've seen this issue only on GEN9+, with Mesa GPU hangs in GfxBench > 4.0 CarChase offscreen (gl_4_off) GL 4.3 test-case. Yes, but the failure is not specific to that. It just depends on having one engine wait on a fence (that is either another engine without semaphores enabled, or an external fence from another driver) for long enough that it accrues hangcheck's anger. In your case, we have the blitter waiting on the render engine that is hung and hangcheck considers them both hung. As it is likely that the render engine made some forward progress (instdone) whilst the blitter was idle waiting, the blitter gets blamed first for the render hang.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>