<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - GPU crash on VegaM (amdgpu: The CS has been rejected)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111921#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - GPU crash on VegaM (amdgpu: The CS has been rejected)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111921">bug 111921</a>
from <span class="vcard"><a class="email" href="mailto:rverschelde@gmail.com" title="Rémi Verschelde <rverschelde@gmail.com>"> <span class="fn">Rémi Verschelde</span></a>
</span></b>
<pre>(In reply to Andrey Grodzovsky from <a href="show_bug.cgi?id=111921#c4">comment #4</a>)
<span class="quote">> What happens if you disable GPU reset by loading the kernel with
> amdgpu.gpu_recovery=0 ?</span >
Good point, I forgot to mention that I added `amdgpu.dc=0
amdgpu.gpu_recovery=1` in an attempt to work around this issue just before
reproducing it again. So I can confirm that I could reproduce this issue both
without any amdgpu kernel parameters and with the above two.
I now did some more testing with kernel 5.3.2 and `amdgpu.gpu_recovery=0`
(removing the `amdgpu.dc=0` too). Initially I could not trigger the bug, but I
got it when letting the desktop environment (KDE) trigger its screensaver while
Godot was running on the AMD GPU. Once I resumed from the screensaver, the GPU
crashed (note: I did trigger suspend-to-RAM, the laptop was still powered).
The dmesg output is attached.
To compare, I did another test with kernel 5.1.20 (using `amdgpu.dc=0
amdgpu.gpu_recovery=1`), letting it go to sleep with Godot running on the AMD
GPU, and it resumed without crashing. I also attach the dmesg output for
comparison.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>