<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Random crashes/freezing with amdgpu Fury X mesa 11.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=93652#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Random crashes/freezing with amdgpu Fury X mesa 11.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=93652">bug 93652</a> from <a class="email" href="mailto:s@gonx.dk" title="Sebastian Jensen <s@gonx.dk>"> Sebastian Jensen</a> <pre>I can also confirm this bug in form of a full system freeze on an AMD 380X on the latest Mesa revision in addition to running the latest drm-next as of 27th March 2016. To put it short, setting R600_DEBUG=nodcc seems to alleviate the crashes, based on a couple of hours of testing. For some details, I can confirm the crashes in at least Dota 2, Portal, Counter-Strike: Global Offensive - all native applications - and under WINE, Starcraft II and Heroes of the Storm both crash within minutes. On the contrary, the crash never occured in other programs, like Furmark, Battleblock Theater, as well as Awesomenauts. I also tried recording multiple apitraces where the issue occured, but none of the traces would actually reproduce the hang. However, what strikes me as most odd is that the hang generally never occured in games in WINE when using the Gallium Nine patches, while the hangs would occur within minutes otherwise.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>