<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - RX580 ~ ring gfx timeout ~ particular shaders created by a dolphin-emu game can crash AMDGPU, with both RadeonSI and RADV ~ attached apitrace for RadeonSI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107991#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - RX580 ~ ring gfx timeout ~ particular shaders created by a dolphin-emu game can crash AMDGPU, with both RadeonSI and RADV ~ attached apitrace for RadeonSI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107991">bug 107991</a>
from <span class="vcard"><a class="email" href="mailto:kyle.devir@mykolab.com" title="kyle.devir@mykolab.com">kyle.devir@mykolab.com</a>
</span></b>
<pre>Hi Rob,
You can capture a dolphin-emu apitrace with:
MESA_EXTENSION_OVERRIDE="-GL_AMD_pinned_memory -GL_ARB_buffer_storage" apitrace
trace dolphin-emu
You need to override these because apitrace doesn't like them.
I got my original advice from here:
<a href="https://forums.dolphin-emu.org/Thread-dumping-shaders-to-diagnose-gpu-kernel-driver-crashes">https://forums.dolphin-emu.org/Thread-dumping-shaders-to-diagnose-gpu-kernel-driver-crashes</a>
Just make a save state right before where it crashes, exit, then run the above,
load the save state, and apitrace should capture the crashy frame before the
driver carks it, which REISUB should allow you to properly commit to disk.
Then, trying running it to see if it crashes. If so, compress with the heaviest
level of XZ compression you can, because it'll be rather large.
I'll trying running on my system, to see if it crashes. ;)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>