<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [regression][hang] Trine1EE hangs GPU after loading screen on Mesa3D-17.3 and later" href="https://bugs.freedesktop.org/show_bug.cgi?id=105670#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [regression][hang] Trine1EE hangs GPU after loading screen on Mesa3D-17.3 and later" href="https://bugs.freedesktop.org/show_bug.cgi?id=105670">bug 105670</a> from <a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> Roland Scheidegger</a> <pre>(In reply to almos from <a href="show_bug.cgi?id=105670#c4">comment #4</a>) > The problem is not loop unrolling. The problem is that userspace code can > hang the GPU unrecoverably, and thus bringing down the entire system. > > BTW I can confirm this on Pitcairn with radeon drm in linux 4.15. There isn't much you can do about shaders not terminating (loop limiting in llvmpipe is quite a hack, you could legitimately have a loop which has more iterations). But yes, gpu reset actually working reliably would be nice. I haven't really seen it succeed lately neither (but it can happen...). I disagree that loop unrolling isn't a problem. Clearly there's two problems: - loop unrolling shouldn't turn perfectly fine loops into loops which don't terminate, this is what this bug is about. - gpu reset should work reliably</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>