Created attachment 290797 [details] dmesg Computer fails to resume from suspend. From the logs it looks like AMDGPU fails to resume. It is a thinkpad T14 AMD APU R7 4750U, connected to an external display via USB-C port thru an adapter. I can still ssh to the machine after resume action, but the both internal display and external display stuck at black screen.
Does it work without the external display connected?
(In reply to Alex Deucher from comment #1) > Does it work without the external display connected? Tried several times, Looks like no problem without the external display connected. btw, I have kernel option amd_iommu=off and vt.handoff=7
I am also affected by this. There are a few recent amdgpu suspend bugs open but this one is most similar. My card is a Radeon R7 260X (Bonaire XTX [Radeon R7 260X/360]), so I'm using the experimental amdgpu driver support. 5.4.58 works, 5.4.72 does not, 5.9.1 does not. My computer seems to be completely unresponsive after resuming. I haven't tried SSHing but it does not respond to pressing the power button to put it back into sleep. However there are systemd service logs in the journal after resume. Kernel messages of note, which are not part of working logs: 18:14:26 amdgpu: [powerplay] failed to send message 5e ret is 0 18:14:26 amdgpu: [powerplay] failed to send message 145 ret is 0 ------------------ 18:14:26 [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!! 18:14:26 [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, giving up!!! 18:14:26 [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* set_powergating_state of IP block <uvd_v4_2> failed -1 ------------------ 18:14:26 amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring uvd test failed (-110) 18:14:26 [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <uvd_v4_2> failed -110 18:14:26 [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). 18:14:26 PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -110 18:14:26 PM: Device 0000:01:00.0 failed to resume async: error -110 ------------------ 18:14:27 [drm] Fence fallback timer expired on ring sdma0 Full journalctl from after resume attached.
Created attachment 293321 [details] systemd journal
Can you please re-check this on a recent 5.18.y kernel and latest linux-firmware? I don't believe it should still be an issue. If it is, I would like to see a new log.
I don’t hit this issue anymore, looks it has been fixed. Please close. Thank you!