Skip to main content
Topic: resuming from S2R broke around the time that 5.16.1-artix1-1 was introduced (Read 484 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

resuming from S2R broke around the time that 5.16.1-artix1-1 was introduced

I have an HP Envy x360 with a Ryzen 4700U processor and an AMD GPU.  After the update to 5.16.1-artix1-1, upon resuming from S2R the GPU (Renoir) whines a fair bit (see below) and the graphics stop working.

Code: [Select]
Jan 24 11:44:45 x360 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Jan 24 11:44:45 x360 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Jan 24 11:44:45 x360 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Jan 24 11:44:45 x360 kernel: [drm] DMUB hardware initialized: version=0x0101001C
Jan 24 11:44:45 x360 kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Jan 24 11:44:45 x360 kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jan 24 11:44:45 x360 kernel: [drm] DP Alt mode state on HPD: 0
Jan 24 11:44:45 x360 kernel: [drm] Alt mode has timed out after 201 ms
Jan 24 11:44:45 x360 kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
Jan 24 11:44:45 x360 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v4_0> failed -110
Jan 24 11:44:45 x360 kernel: amdgpu 0000:04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110).
Jan 24 11:44:45 x360 kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -110
Jan 24 11:44:45 x360 kernel: amdgpu 0000:04:00.0: PM: failed to resume async: error -110

and then a few seconds later many of these

Code: [Select]
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
Jan 24 11:45:09 x360 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
Jan 24 11:45:09 x360 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
Jan 24 11:45:09 x360 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
Jan 24 11:45:09 x360 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)

and then groups of these repeated a number of times

Code: [Select]
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:7 pasid:32769, for process Xorg pid 2618 thread Xorg:cs0 pid 2727)
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu:   in page starting at address 0x0000800106640000 from IH client 0x1b (UTCL2)
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00741051
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: \x09 Faulty UTCL2 client ID: TCP (0x8)
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: \x09 MORE_FAULTS: 0x1
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: \x09 WALKER_ERROR: 0x0
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: \x09 PERMISSION_FAULTS: 0x5
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: \x09 MAPPING_ERROR: 0x0
Jan 24 11:45:09 x360 kernel: amdgpu 0000:04:00.0: amdgpu: \x09 RW: 0x1

I can ssh in, and sometimes I can get to a console, but even in a console the screen lights up and goes dark.

One way or the other, I have to reboot.

I've searched around on the web a bit and found various similar issues, but not (yet, anyway) this exact one. 

Anyone else here seen this?  Or know an easy solution?

Thanks.

Re: resuming from S2R broke around the time that 5.16.1-artix1-1 was introduced

Reply #1
Obviously a kernel issue. For the time being you should either downgrade or use linux-lts. If you don't have the previous kernel in cache, use our packages archive.

 

Re: resuming from S2R broke around the time that 5.16.1-artix1-1 was introduced

Reply #2
Thanks very much, a "downgrade" (it's an upgrade to me) seems to have fixed the issue.