A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures.
It will manifest as:
[drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v5_2> failed -110 amdgpu 0000:04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu 0000:04:00.0: PM: failed to resume async: error -110
The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. The patch going into 5.15-rcX and 5.14.y is: https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html
A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures.
It will manifest as:
[drm:amdgpu_ device_ ip_resume_ phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v5_2> failed -110 device_ ip_resume failed (-110). resume+ 0x0/0x90 returns -110
amdgpu 0000:04:00.0: amdgpu: amdgpu_
PM: dpm_run_callback(): pci_pm_
amdgpu 0000:04:00.0: PM: failed to resume async: error -110
The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. /lists. freedesktop. org/archives/ amd-gfx/ 2021-September/ 069451. html
The patch going into 5.15-rcX and 5.14.y is: https:/