<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [polaris11] - GPU Hang - ring gfx timeout" href="https://bugs.freedesktop.org/show_bug.cgi?id=108854#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [polaris11] - GPU Hang - ring gfx timeout" href="https://bugs.freedesktop.org/show_bug.cgi?id=108854">bug 108854</a> from <a class="email" href="mailto:tseewald@gmail.com" title="Tom Seewald <tseewald@gmail.com>"> Tom Seewald</a> <pre>(In reply to Tom St Denis from <a href="show_bug.cgi?id=108854#c13">comment #13</a>) > The wave dump seems to be empty... Is that the complete output? Was there > anything printed to stderr (like there are no waves)? Yes it says "no active waves!" - so it makes sense that is empty. Is there something else you'd like me to try? Currently I'm running "umr -i 1 -O verbose,halt_waves -wa" immediately after I see the "ring gfx timeout" in dmesg. I also just rebuilt UMR so I should be up to date. Some potentially good news though, after upgrading from mesa 18.3.1 to 18.3.3, I have not been able to reproduce the issue. On mesa 18.3.1 and earlier I can reproduce it in under 20 seconds (I did so today on the latest amd-staging-drm-next), and I have tested mesa 18.3.3 for about an hour now. But I believe this is still something to look into as user space should probably not be able to hang the entire system, even if the user is running an older version of Mesa.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>