https://bugs.freedesktop.org/show_bug.cgi?id=108854
--- Comment #12 from Tom Seewald tseewald@gmail.com --- (In reply to Alex Deucher from comment #11)
The reset was actually successful. The problem is, userspace components need to be aware of the reset and recreate their contexts. As a workaround, you can kill the problematic app or restart X.
Hmm, but then why will the machine not restart unless I use sysrq keys? I would think a userspace issue wouldn't cause hung kernel tasks like that.
I'm also curious regarding why this program is causing the GPU to reset to begin with, I have not seen others reporting issues on other platforms with this program.
Is this ring gfx timeout purely a problem with userspace?
e.g. [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=32203, emitted seq=32205