https://bugzilla.kernel.org/show_bug.cgi?id=209457
--- Comment #15 from fawz (fawz@negentropy.io) --- Hi all,
I'm not sure if I'm experiencing the same bug, but the outcome and some of the log messages seem to be the same.
For me, resuming from suspend is broken with kernel 5.9.0-2 and works when I boot with 5.7.0-1, keeping the rest of my system the same. I'm on debian sid.
For SEO, in dmesg I see messages like
nov. 11 17:27:35 [ 202.045603] amdgpu: [powerplay] nov. 11 17:27:35 failed to send message 146 ret is 0
nov. 11 17:27:35 [ 203.073392] [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
nov. 11 17:27:35 [ 216.242177] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring uvd test failed (-110) nov. 11 17:27:35 [ 216.242245] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <uvd_v4_2> failed -110 nov. 11 17:27:35 [ 216.242312] [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
nov. 11 17:27:44 [ 224.963014] [drm] Fence fallback timer expired on ring sdma0
My hardware:
- CPU: AMD FX-6200 Six-Core Processor - VGA: [AMD/ATI] Hawaii PRO [Radeon R9 290/390] - Motherboard: GA-990FXA-UD3 Firmware F9
Software - debian sid - firmware-amd-graphics: 20200918-1 - libdrm-amdgpu1: 2.4.102-1 - mesa: 20.2.1-1
To reiterate, just booting into kernel 5.7 instead of 5.9, resume from suspend will work, keeping the above software the same.