System frequently crashing after GPU drivers update

Support KDE Plasma
, , ,
83

I’ll be looking into this today since I just got bit with this after the update this month.

I’m running on 5.4 and being affected by this. I think I’m going to try the kernel param first, and see where that gets me before jumping up kernel versions. I like to stay on the LTS if possible.

EDIT:

System information. It’s notable that I have a Ryzen 5 3400G - so similar to the other integrated graphics APUs mentioned in this thread.

System:    Kernel: 5.4.114-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
           parameters: initrd=\amd-ucode.img initrd=\intel-ucode.img initrd=\initramfs-5.4-x86_64.img quiet splash 
           rd.luks.name=95325077-53fb-4bfd-a79d-4a4d07f916f6=crypt-system 
           rd.luks.name=ff8cb4ed-4d53-44ca-a2f9-3923f70cf65c=md127 root=/dev/vg-system/root rw resume=/dev/vg-system/swap 
           loglevel=3 rd.udev.log_priority=3 vt.global_cursor_default=0 fbcon=nodefer i915.fastboot=1 vga=current 
           rcu_nocbs=0-7 
           Desktop: Cinnamon 4.8.6 tk: GTK 3.24.29 vt: 7 dm: LightDM 1.30.0 Distro: Manjaro Linux base: Arch Linux 
Machine:   Type: Desktop Mobo: ASRock model: A300M-STX serial: <filter> UEFI: American Megatrends v: P3.60 date: 10/28/2019 
Battery:   Message: No system battery data found. Is one present? 
Memory:    RAM: total: 29.39 GiB used: 4.81 GiB (16.4%) 
           RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:       Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen/Zen+ note: check 
           family: 17 (23) model-id: 18 (24) stepping: 1 microcode: 8108102 cache: L2: 2 MiB bogomips: 59217 
           Speed: 3052 MHz min/max: N/A Core speeds (MHz): 1: 3052 2: 2874 3: 2915 4: 2938 5: 3048 6: 2910 7: 2948 8: 2918 
           Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext clflush clflushopt clzero cmov 
           cmp_legacy constant_tsc cpb cpuid cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid fma fpu 
           fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor movbe msr 
           mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb 
           perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rdrand rdseed rdtscp rep_good sep sev 
           sha_ni skinit smap smca sme smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock syscall tce topoext 
           tsc tsc_scale v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel bus-ID: 04:00.0 chip-ID: 1002:15d8 
           class-ID: 0300 
           Device-2: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-3.3:4 chip-ID: 046d:081b 
           class-ID: 0102 serial: <filter> 
           Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa 
           display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 4890x1680 s-dpi: 96 s-size: 1294x445mm (50.9x17.5") s-diag: 1368mm (53.9") 
           Monitor-1: DisplayPort-0 res: 1920x1200 hz: 60 dpi: 94 size: 519x324mm (20.4x12.8") diag: 612mm (24.1") 
           Monitor-2: HDMI-A-0 res: 1920x1200 hz: 60 dpi: 94 size: 519x324mm (20.4x12.8") diag: 612mm (24.1") 
           Monitor-3: DisplayPort-2 res: 1050x1680 hz: 60 
           OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.35.0 5.4.114-1-MANJARO LLVM 11.1.0) v: 4.6 Mesa 21.0.3 
           direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel 
           bus-ID: 04:00.1 chip-ID: 1002:15de class-ID: 0403 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Device-3: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-3.3:4 chip-ID: 046d:081b 
           class-ID: 0102 serial: <filter> 
           Device-4: PreSonus Audio AudioBox USB type: USB driver: snd-usb-audio bus-ID: 1-3.4:5 chip-ID: 194f:0302 
           class-ID: 0103 
           Sound Server-1: ALSA v: k5.4.114-1-MANJARO running: yes 
           Sound Server-2: JACK v: 0.125.0 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: yes 
           Sound Server-4: PipeWire v: 0.3.26 running: no 
Network:   Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus-ID: 02:00.0 
           chip-ID: 8086:24fb class-ID: 0280 
           IF: wlp2s0 state: down mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: f000 
           bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           IP v4: <filter> type: dynamic noprefixroute scope: global broadcast: <filter> 
           IP v6: <filter> type: noprefixroute scope: link 
           IF-ID-1: br-45db66d3253f state: down mac: <filter> 
           IP v4: <filter> scope: global broadcast: <filter> 
           IF-ID-2: docker0 state: down mac: <filter> 
           IP v4: <filter> scope: global broadcast: <filter> 
           WAN IP: <filter> 
Bluetooth: Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-3.1:3 chip-ID: 8087:0aa7 
           class-ID: e001 
           Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends 
Logical:   Message: Unable to run lvs. Root privileges required. 
           Device-1: md127 maj-min: 254:0 type: LUKS dm: dm-0 size: 119.18 GiB 
           Components: 
           c-1: md127 maj-min: 9:127 size: 119.18 GiB 
           pp-1: sda1 maj-min: 8:1 size: 119.24 GiB 
           pp-2: sdb1 maj-min: 8:17 size: 119.24 GiB 
           Device-2: luks-6bc77c7d-f14a-4127-939a-e672a87c167f maj-min: 254:6 type: LUKS dm: dm-6 size: 3.64 TiB 
           Components: 
           p-1: sdc1 maj-min: 8:33 size: 3.64 TiB 
           Device-3: crypt-system maj-min: 254:1 type: LUKS dm: dm-1 size: 224.88 GiB 
           Components: 
           p-1: nvme0n1p2 maj-min: 259:2 size: 224.88 GiB 
RAID:      Supported mdraid levels: raid1 
           Device-1: md127 maj-min: 9:127 type: mdraid level: mirror status: active size: 119.18 GiB 
           Info: report: 2/2 UU blocks: 124967232 chunk-size: N/A super-blocks: 1.2 
           Components: Online: 
           0: sda1 maj-min: 8:1 size: 119.24 GiB 
           1: sdb1 maj-min: 8:17 size: 119.24 GiB 
Drives:    Local Storage: total: 4.1 TiB used: 314.8 GiB (7.5%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB block-size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 2B2QEXE7 scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 PRO 128GB size: 119.24 GiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 PRO 128GB size: 119.24 GiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 2B6Q scheme: GPT 
           ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate model: ST4000DM006-2G5107 size: 3.64 TiB block-size: 
           physical: 4096 B logical: 512 B rotation: 7200 rpm serial: <filter> rev: 235C scheme: GPT 
           Message: No optical or floppy data found. 
Partition: ID-1: / raw-size: 100 GiB size: 97.93 GiB (97.93%) used: 14.65 GiB (15.0%) fs: ext4 dev: /dev/dm-4 maj-min: 254:4 
           mapped: vg--system-root label: N/A uuid: N/A 
           ID-2: /boot raw-size: 8 GiB size: 7.98 GiB (99.80%) used: 73.7 MiB (0.9%) fs: vfat dev: /dev/nvme0n1p1 
           maj-min: 259:1 label: N/A uuid: 4128-03BE 
           ID-3: /home raw-size: 119.18 GiB size: 116.8 GiB (98.01%) used: 57.04 GiB (48.8%) fs: ext4 dev: /dev/dm-0 
           maj-min: 254:0 mapped: md127 label: N/A uuid: N/A 
           ID-4: /run/media/andrewcz/Halman raw-size: 3.64 TiB size: 3.58 TiB (98.40%) used: 230.02 GiB (6.3%) fs: ext4 
           dev: /dev/dm-6 maj-min: 254:6 mapped: luks-6bc77c7d-f14a-4127-939a-e672a87c167f label: Halman 
           uuid: 10a726dc-7fb7-46ea-8c6b-c4a163a988a3 
           ID-5: /var raw-size: 34 GiB size: 33.4 GiB (98.25%) used: 13.02 GiB (39.0%) fs: ext4 dev: /dev/dm-3 maj-min: 254:3 
           mapped: vg--system-var label: N/A uuid: N/A 
Swap:      Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-2 maj-min: 254:2 
           mapped: vg--system-swap label: N/A uuid: 03be70e2-8fa2-4fe1-87f5-ec15990aaa41 
Unmounted: ID-1: /dev/dm-5 maj-min: 254:5 mapped: docker-254:3-786567-pool size: 100 GiB fs: <superuser required> label: N/A 
           uuid: N/A 
USB:       Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
           Hub-2: 1-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA chip-ID: 05e3:0608 
           class-ID: 0900 
           Device-1: 1-3.1:3 info: Intel Wireless-AC 3168 Bluetooth type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 
           speed: 12 Mb/s power: 100mA chip-ID: 8087:0aa7 class-ID: e001 
           Device-2: 1-3.3:4 info: Logitech Webcam C310 type: Video,Audio driver: snd-usb-audio,uvcvideo interfaces: 4 
           rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 046d:081b class-ID: 0102 serial: <filter> 
           Device-3: 1-3.4:5 info: PreSonus Audio AudioBox USB type: Audio driver: snd-usb-audio interfaces: 5 rev: 1.1 
           speed: 12 Mb/s power: 500mA chip-ID: 194f:0302 class-ID: 0103 
           Hub-3: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 
           Device-1: 2-2:2 info: LaCie d2 Professional type: Mass Storage driver: uas interfaces: 1 rev: 3.1 speed: 5 Gb/s 
           power: 8mA chip-ID: 059f:10b8 class-ID: 0806 serial: <filter> 
           Hub-4: 3-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
           Device-1: 3-1:2 info: ZSA Labs ErgoDox EZ type: Keyboard,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.1 
           speed: 12 Mb/s power: 500mA chip-ID: 3297:4974 class-ID: 0300 
           Hub-5: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 
Sensors:   System Temperatures: cpu: 46.2 C mobo: 0 C gpu: amdgpu temp: 46.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 343 Uptime: 9m wakeups: 0 Init: systemd v: 247 tool: systemctl Compilers: gcc: 10.2.0 clang: 11.1.0 
           Packages: pacman: 1570 lib: 418 flatpak: 0 Shell: Zsh v: 5.8 running-in: gnome-terminal inxi: 3.3.04
1 Like
84

I got a coredump with that same kinda behavior.

Uploaded the .txt file of the failure here: Nextcloud

Probably look at updating the kernel next.

85

Looks familiar. My setup is almost identical (3400G on ASRock DeskMini).

We know already, that Kernel 5.12 alone does not solve the problem.

Did you install the Mesa update mentioned above?

1 Like
86

So I haven’t had an issue in a while i’m guessing i did the mesa updates i don’t always read what gets updated (I know it’s baaaaaaaaaad)

87

You can just check what mesa version you’ve got by running sudo pacman -Q --info mesa, or even do the same with its dependencies.

To know what got updated at a certain date, you could just check the content of the /var/log/pacman.log file – it’s where every update that was ran, either by plain pacman or another AUR package manager (like yay).

88

so i have
Name : mesa
Version : 21.0.3-2

The version that alledgedly integrates corrections is 21.0.3-1 so i’m up to date on this.

Today i got 2 freeze in a row after 2 days of no problemo. The one thing that might have made a difference is that i put the comp on standby a couple times but not sure if that can impact.

May 04 18:27:05 systemd[1407]: tracker-extract-3.service: Succeeded.
May 04 18:27:14 kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
May 04 18:27:14 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=1606824, emitted seq=1606825
May 04 18:27:14 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset begin!
May 04 18:27:14 kernel: [drm] free PSP TMR buffer
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: MODE2 reset
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset succeeded, trying to resume
May 04 18:27:14 kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).
May 04 18:27:14 kernel: [drm] PSP is resuming...
May 04 18:27:14 kernel: [drm] reserve 0x400000 from 0xf47fc00000 for PSP TMR
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
May 04 18:27:14 kernel: [drm] kiq ring mec 2 pipe 1 q 0
May 04 18:27:14 kernel: [drm] VCN decode and encode initialized successfully(under SPG Mode).
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: recover vram bo from shadow start
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: recover vram bo from shadow done
May 04 18:27:14 kernel: [drm] Skip scheduling IBs!
May 04 18:27:14 kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset(1) succeeded!
May 04 18:27:15 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-BEACON-LOSS
May 04 18:27:16 kernel: sched: RT throttling activated
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119b802e0 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119b80300 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119b80320 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119b80340 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119b80360 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x119b80380 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119b803a0 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119b803c0 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119b803e0 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119b80400 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119bc0000 flags=0x0070]
May 04 18:27:24 kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x119b80420 flags=0x0070]
May 04 18:27:24 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=5852587, emitted seq=5852590
May 04 18:27:24 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 1531 thread Xwayland:cs0 pid 1908
May 04 18:27:24 kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset begin!
May 04 18:27:25 kernel: [drm] free PSP TMR buffer
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: MODE2 reset
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset succeeded, trying to resume
May 04 18:27:25 kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).
May 04 18:27:25 kernel: [drm] PSP is resuming...
May 04 18:27:25 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=ac:f8:cc:07:dc:b2 reason=4 locally_generated=1
May 04 18:27:25 kernel: rtw_8822be 0000:04:00.0: sta ac:f8:cc:07:dc:b2 with macid 0 left
May 04 18:27:25 kernel: [drm] reserve 0x400000 from 0xf47fc00000 for PSP TMR
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
May 04 18:27:25 kernel: [drm] kiq ring mec 2 pipe 1 q 0
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
May 04 18:27:25 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v4_0> failed -110
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset(3) failed
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: GPU reset end with ret = -110
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 kernel: amdgpu 0000:05:00.0: amdgpu: couldn't schedule ib on ring <sdma0>
May 04 18:27:25 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
May 04 18:27:25 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 04 18:27:25 NetworkManager[542]: <info>  [1620145645.6914] device (wlp4s0): supplicant interface state: completed -> scanning
May 04 18:27:27 audit[10228]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 subj==unconfined pid=10228 comm="GpuWatchdog" exe="/app/extra/share/skypeforlinux/skypeforlinux" sig=11 res=1
May 04 18:27:27 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
May 04 18:27:27 audit: BPF prog-id=35 op=LOAD
May 04 18:27:27 audit: BPF prog-id=36 op=LOAD
May 04 18:27:27 systemd[1]: Started Process Core Dump (PID 33633/UID 0).
May 04 18:27:27 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@0-33633-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 04 18:27:32 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
May 04 18:27:32 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
May 04 18:27:35 wpa_supplicant[686]: wlp4s0: SME: Trying to authenticate with ac:f8:cc:07:dc:b2 (SSID='V&T' freq=5500 MHz)
May 04 18:27:35 kernel: wlp4s0: authenticate with ac:f8:cc:07:dc:b2
May 04 18:27:35 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
May 04 18:27:35 NetworkManager[542]: <info>  [1620145655.9486] device (wlp4s0): supplicant interface state: scanning -> authenticating
May 04 18:27:35 kernel: wlp4s0: send auth to ac:f8:cc:07:dc:b2 (try 1/3)
May 04 18:27:35 wpa_supplicant[686]: wlp4s0: Trying to associate with ac:f8:cc:07:dc:b2 (SSID='V&T' freq=5500 MHz)
May 04 18:27:35 kernel: wlp4s0: authenticated
May 04 18:27:35 kernel: wlp4s0: associate with ac:f8:cc:07:dc:b2 (try 1/3)
May 04 18:27:35 NetworkManager[542]: <info>  [1620145655.9670] device (wlp4s0): supplicant interface state: authenticating -> associating
May 04 18:27:36 wpa_supplicant[686]: wlp4s0: Associated with ac:f8:cc:07:dc:b2
May 04 18:27:36 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 04 18:27:36 kernel: wlp4s0: RX AssocResp from ac:f8:cc:07:dc:b2 (capab=0x11 status=0 aid=5)
May 04 18:27:36 kernel: rtw_8822be 0000:04:00.0: sta ac:f8:cc:07:dc:b2 joined with macid 0
May 04 18:27:36 kernel: wlp4s0: associated
May 04 18:27:36 NetworkManager[542]: <info>  [1620145656.0204] device (wlp4s0): supplicant interface state: associating -> 4way_handshake
May 04 18:27:36 NetworkManager[542]: <info>  [1620145656.0205] device (wlp4s0): DHCPv4 lease renewal requested
May 04 18:27:36 NetworkManager[542]: <info>  [1620145656.0206] dhcp4 (wlp4s0): canceled DHCP transaction
May 04 18:27:36 NetworkManager[542]: <info>  [1620145656.0206] dhcp4 (wlp4s0): state changed extended -> terminated
May 04 18:27:36 NetworkManager[542]: <info>  [1620145656.0213] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
May 04 18:27:36 wpa_supplicant[686]: wlp4s0: WPA: Key negotiation completed with ac:f8:cc:07:dc:b2 [PTK=CCMP GTK=CCMP]
May 04 18:27:36 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to ac:f8:cc:07:dc:b2 completed [id=0 id_str=]
May 04 18:27:36 NetworkManager[542]: <info>  [1620145656.0607] device (wlp4s0): supplicant interface state: 4way_handshake -> completed
May 04 18:27:36 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-45 noise=9999 txrate=585000
May 04 18:27:38 NetworkManager[542]: <info>  [1620145658.0661] dhcp4 (wlp4s0): state changed unknown -> bound, address=192.168.1.50
May 04 18:27:38 dbus-daemon[541]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=542 comm="/usr/bin/NetworkManager --no-daemon ")
May 04 18:27:38 systemd[1]: Starting Network Manager Script Dispatcher Service...
May 04 18:27:39 geoclue[1602]: Failed to query location: Error resolving “location.services.mozilla.com”: Name or service not known
May 04 18:27:39 wpa_supplicant[686]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 04 18:27:45 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
May 04 18:28:00 audit[33645]: USER_AUTH pid=33645 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 kernel: kauditd_printk_skb: 156 callbacks suppressed
May 04 18:28:00 kernel: audit: type=1100 audit(1620145680.567:378): pid=33645 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 dbus-daemon[541]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.384' (uid=0 pid=33645 comm="sshd: gh0st [priv]  ")
May 04 18:28:00 dbus-daemon[541]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
May 04 18:28:00 sshd[33645]: pam_systemd_home(sshd:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 04 18:28:00 audit[33645]: USER_ACCT pid=33645 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 sshd[33645]: Accepted password for gh0st from 192.168.1.201 port 44582 ssh2
May 04 18:28:00 audit[33645]: CRED_ACQ pid=33645 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 audit[33645]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=3 a1=7ffcf36e2010 a2=4 a3=3e8 items=0 ppid=568 pid=33645 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=5 comm="sshd" exe="/usr/bin/sshd" subj==unconfined key=(null)
May 04 18:28:00 audit: PROCTITLE proctitle=737368643A206768307374205B707269765D
May 04 18:28:00 sshd[33645]: pam_unix(sshd:session): session opened for user gh0st(uid=1000) by (uid=0)
May 04 18:28:00 kernel: audit: type=1101 audit(1620145680.577:379): pid=33645 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 kernel: audit: type=1103 audit(1620145680.577:380): pid=33645 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 kernel: audit: type=1006 audit(1620145680.577:381): pid=33645 uid=0 subj==unconfined old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=5 res=1
May 04 18:28:00 kernel: audit: type=1300 audit(1620145680.577:381): arch=c000003e syscall=1 success=yes exit=4 a0=3 a1=7ffcf36e2010 a2=4 a3=3e8 items=0 ppid=568 pid=33645 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=5 comm="sshd" exe="/usr/bin/sshd" subj==unconfined key=(null)
May 04 18:28:00 kernel: audit: type=1327 audit(1620145680.577:381): proctitle=737368643A206768307374205B707269765D
May 04 18:28:00 systemd-logind[546]: New session 5 of user gh0st.
May 04 18:28:00 systemd[1]: Started Session 5 of user gh0st.
May 04 18:28:00 sshd[33645]: pam_env(sshd:session): deprecated reading of user environment enabled
May 04 18:28:00 audit[33645]: USER_START pid=33645 uid=0 auid=1000 ses=5 subj==unconfined msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 audit[33647]: CRED_ACQ pid=33647 uid=0 auid=1000 ses=5 subj==unconfined msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 kernel: audit: type=1105 audit(1620145680.593:382): pid=33645 uid=0 auid=1000 ses=5 subj==unconfined msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:00 kernel: audit: type=1103 audit(1620145680.593:383): pid=33647 uid=0 auid=1000 ses=5 subj==unconfined msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="gh0st" exe="/usr/bin/sshd" hostname=192.168.1.201 addr=192.168.1.201 terminal=ssh res=success'
May 04 18:28:03 dbus-daemon[541]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out (service_start_timeout=25000ms)
89

I’m really sorry to hear that you got random freezes after some hopeful days. I guess none of us has the evidence (nor the guts) to state they found a solution for this. I’d have thought that the microcode update that came with the 5.12 update solved the page faults issue, but it seems not.

Guess that all we can do is enjoy the freeze-less streaks we may have as randomly as the freezes we get. I’ll keep y’all updated on any new failure or any succesful combination of drivers, kernel parameters and packages I may try. :pray:

90

Once linux grows based on community, how could all people here that have the same or very similar issue prepare data to proper report the issue? maybe someone from Manjaro development could guide us in order to collect the right information to report to kernel developers. Looks like there is a lot of cases here.

By the way, mine is from AMD GPU RX 570. completely random but the log said it is always triggered with this log:

kernel [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] ERROR Waiting for fences timed out!

1 Like
91

Searching for that message brings up several bug reports:

92

The link you share is the right and the best place to post about this issue? any one can post there? what information should I post to proper contribute? Ksystemlog is enough?

Sorry for too many questions, i’m still learning about Linux.

93

It is the GitLab instance for kernel graphics development, specificly the repository for collecting issues regarding amd drivers. Quote:

amd (amdgpu, amdkfd, radeon) drm project, currently for issues only.

I suggest you scan/search the existing bug reports if one already matches your problem and open a new one only if no other fits.

1 Like
94

When you create a new issue there, you can select a template which gives you a predefined structure with the things that you should provide.

Template

Brief summary of the problem:

<TODO: Briefly describe your issue>

Hardware description:

  • CPU:
  • GPU:
  • System Memory:
  • Display(s):
  • Type of Diplay Connection: <TODO: DP, HDMI, DVI, etc>

System information:

  • Distro name and Version: <TODO: e.g., Ubuntu 20.04.1>
  • Kernel version: <TODO: e.g., 5.6.11>
  • Custom kernel: <TODO: e.g., Kernel from drm-misc-next, commit: “Message”>
  • AMD package version: <TODO: e.g., “20.02” or “No package”>

How to reproduce the issue:

< TODO: Describe step-by-step how to reproduce the issue >
< NOTE: Add as much detail as possible >

Attached files:

  • Dmesg log
  • Xorg log
  • Any other log
1 Like
95

Thank you.

I post my contribution here:

https://gitlab.freedesktop.org/drm/amd/-/issues/1322

2 Likes
96

No worries! (unless it’s your fault :wink: ) just passing information in case it can help :slight_smile:

1 Like
97

Thank you! I hope I don’t have to use it in the future, but this template seems great; if I start experiencing this kind of issues again, I’ll definitely post my issue on their site.

98

still, latest mesa drive, 5.10 kernel

5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080011ba00000 from client 27
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x003C0071
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: CB (0x0)
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x1
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x7
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x1
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 4170 thread Xorg:cs0 pid 4171)
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080011ba01000 from client 27
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x003C0071
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: CB (0x0)
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x1
    5月 08 11:18:57 self kernel: amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
100

5.11.14 is better

101

Hi, everyone c: It’s second day when I don’t have any crash by amdgpu. What have I done: add amdgpu.noretry, move to 5.12 and disable iommu in bios. (or maybe last update fix it?)

1 Like
102

Hope it is a fix for you! :crossed_fingers: In my case, when I set the amdgpu.noretry=0 kernel parameter I couldn’t even boot into Manjaro, just getting a black screen after picking the option in GRUB.

An update on my end: Until yesterday, I had spent slightly more than a week with no GPU-related freezing or crashing. I left my computer on for a while and, when I went back to use it, a lot of page faults had happened and my system was completely frozen (I’m remarking the fact that this time I wasn’t even using it, it was just running some processes on the foreground and had a couple of applications open). All of this happened while using the 5.12.0-1 kernel and the mesa updates that came with the April 28th system upgrade.

So I guess I can call it a freeze-less personal record since I first experienced this issues around a month ago. I’m glad my performance is improving, but yet I can’t state my problem is solved. I’ve seen that a system update came out on May the 6th, including some mesa updates, but haven’t dared to try it :sweat_smile: . I will do so in the next days, probably.

1 Like
103

I’ve been having the freezings less frequently, but still randomly after installing the mesa drivers. So I just updated to the latest packages, and updated to the 5.10 kernel. We’ll see how long it takes with this combo to go belly-up.