After resume from S3 sleep: couldn't schedule ib on ring <sdma0>
Brief summary of the problem:
I woke up my system from S3 sleep and the sdma0 ring was non-functional.
Frequency: Rare
Hardware description:
- CPU: AMD Ryzen 9 5950X
- GPU: 0c:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0)
- System Memory: 32GB
- Display(s): 1
- Type of Display Connection: DisplayPort
System information:
- Distro name and Version: Arch Linux
- Kernel version: 6.0.12-arch1-1
- Mesa: 23.0.0-devel (git-57b7102ef9)
Log messages
Jan 06 11:10:16 spydo kernel: ACPI: PM: Waking up from system sleep state S3
Jan 06 11:10:16 spydo kernel: sd 3:0:0:0: [sda] Starting disk
Jan 06 11:10:16 spydo kernel: sd 8:0:0:0: [sdd] Starting disk
Jan 06 11:10:16 spydo kernel: sd 4:0:0:0: [sdb] Starting disk
Jan 06 11:10:16 spydo kernel: sd 9:0:0:0: [sde] Starting disk
Jan 06 11:10:16 spydo kernel: sd 5:0:0:0: [sdc] Starting disk
Jan 06 11:10:16 spydo kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Jan 06 11:10:16 spydo kernel: [drm] PSP is resuming...
Jan 06 11:10:16 spydo kernel: [drm] reserve 0xa00000 from 0x8001000000 for PSP TMR
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resuming...
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5400 (58.84.0)
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: SMU driver if version not matched
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: use vbios provided pptable
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resumed successfully!
Jan 06 11:10:16 spydo kernel: [drm] DMUB hardware initialized: version=0x02020013
Jan 06 11:10:16 spydo kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jan 06 11:10:16 spydo kernel: usb 5-4: reset full-speed USB device number 10 using xhci_hcd
Jan 06 11:10:16 spydo kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 06 11:10:16 spydo kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 06 11:10:16 spydo kernel: ata6.00: supports DRM functions and may not be fully accessible
Jan 06 11:10:16 spydo kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 06 11:10:16 spydo kernel: ata6.00: NCQ Send/Recv Log not supported
Jan 06 11:10:16 spydo kernel: ata6.00: supports DRM functions and may not be fully accessible
Jan 06 11:10:16 spydo kernel: ata6.00: NCQ Send/Recv Log not supported
Jan 06 11:10:16 spydo kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 06 11:10:16 spydo kernel: ata6.00: configured for UDMA/133
Jan 06 11:10:16 spydo kernel: ata5.00: configured for UDMA/133
Jan 06 11:10:16 spydo kernel: ata5.00: Enabling discard_zeroes_data
Jan 06 11:10:16 spydo kernel: [drm] kiq ring mec 2 pipe 1 q 0
Jan 06 11:10:16 spydo kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Jan 06 11:10:16 spydo kernel: [drm] JPEG decode initialized successfully.
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 1
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 1
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 1
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 1
Jan 06 11:10:16 spydo kernel: [drm:sdma_v5_2_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on sdma0 (-110).
Jan 06 11:10:16 spydo kernel: [drm:process_one_work] *ERROR* ib ring test failed (-110).
Jan 06 11:10:16 spydo kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 06 11:10:16 spydo kernel: ata9.00: configured for UDMA/133
Jan 06 11:10:16 spydo kernel: igc 0000:06:00.0 enp6s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Jan 06 11:10:16 spydo kernel: ata10: found unknown device (class 0)
Jan 06 11:10:16 spydo kernel: ata4: found unknown device (class 0)
Jan 06 11:10:16 spydo kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 06 11:10:16 spydo kernel: ata10.00: configured for UDMA/133
Jan 06 11:10:16 spydo kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 06 11:10:16 spydo kernel: ata4.00: configured for UDMA/133
Jan 06 11:10:16 spydo kernel: OOM killer enabled.
Jan 06 11:10:16 spydo kernel: Restarting tasks ...
Jan 06 11:10:16 spydo kernel: input: Microsoft X-Box One S pad as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3/usb5/5-4/5-4:1.0/input/input44
Jan 06 11:10:16 spydo kernel: done.
Jan 06 11:10:16 spydo kernel: random: crng reseeded on system resumption
Jan 06 11:10:16 spydo kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_copy_buffer [amdgpu]] *ERROR* Trying to move memory with ring turned off.
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_copy_buffer [amdgpu]] *ERROR* Trying to move memory with ring turned off.
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
Jan 06 11:10:16 spydo kernel: amdgpu: Move buffer fallback to memcpy unavailable
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* amdgpu_vm_validate_pt_bos() failed.
Jan 06 11:10:16 spydo kernel: amdgpu 0000:0c:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -22!
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_copy_buffer [amdgpu]] *ERROR* Trying to move memory with ring turned off.
Jan 06 11:10:16 spydo kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
Jan 06 11:10:16 spydo kernel: amdgpu: Move buffer fallback to memcpy unavailable
*** Repeats ***
Edited by John Brooks