<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - TONGA hang in amdgpu_ring_lock" href="https://bugs.freedesktop.org/show_bug.cgi?id=91790#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - TONGA hang in amdgpu_ring_lock" href="https://bugs.freedesktop.org/show_bug.cgi?id=91790">bug 91790</a> from <a class="email" href="mailto:master.homer@gmail.com" title="Mathias Tillman <master.homer@gmail.com>"> Mathias Tillman</a> <pre>(In reply to Christian König from <a href="show_bug.cgi?id=91790#c3">comment #3</a>) > That could just be a symptom of a hardware hang which isn't detected for > some reason. > > Please take a look at amdgpu_fence_info as well to see if there are any > outstanding submissions. If it's a hardware hang, wouldn't it also happen when using catalyst? It doesn't happen there, so it should at least be possible to work around (if it is a hardware problem). I will continue investigating why this happens, but it does seem to me like this, #91278, and #91676 all are caused by the same thing, but with different log output depending on if you use drm-next-4.3 or drm-next-4.2.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>