<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#c2">Comment # 2</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>Created <a href="attachment.cgi?id=117967" name="attach_117967" title="dmesg with added debug output">attachment 117967</a> <a href="attachment.cgi?id=117967&action=edit" title="dmesg with added debug output">[details]</a> dmesg with added debug output I've done some more testing, turns out that it never reaches amdgpu_ring_unlock_commit on certain cases, and that's what causes it to hang, since the mutex never unlocks. I added some debug output to the code, gfx/sdma0 is ring->name, 0/9 is ring->idx and the address is the address of the ring struct. As you can see in the log, it calls amdgpu_ring_lock on ring 9 with name sdma0, and then afterwards it calls it again on ring 0 with name gfx, without calling amdgpu_ring_unlock_commit. I will add some more debug output in hopes of finding why exactly it's never unlocked, and if it is fixable. I should mention that these random lockups do not happen while using the proprietary catalyst driver, so it must be something in the amdgpu driver.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>