[Driver] ERROR MES failed to response msg=2

Triggered by running https://github.com/RadeonOpenCompute/rocm_bandwidth_test in a loop while running https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/master/gpu-burn in a loop.
1x 7900XTX
ASROCK ROMED8-2T
EPYC 7662
Ubuntu 22.04, Kernel 6.2.14-060214-generic, ROCm 5.5
sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover will recover the GPU.
[  111.406216] amdgpu 0000:83:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:10 pasid:32769, for process rocm-bandwidth- pid 3286 thread rocm-bandwidth- pid 3286)
[  111.406237] amdgpu 0000:83:00.0: amdgpu:   in page starting at address 0x00007f0000000000 from client 10
[  111.406246] amdgpu 0000:83:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00A01A30
[  111.406253] amdgpu 0000:83:00.0: amdgpu:      Faulty UTCL2 client ID: SDMA0 (0xd)
[  111.406259] amdgpu 0000:83:00.0: amdgpu:      MORE_FAULTS: 0x0
[  111.406265] amdgpu 0000:83:00.0: amdgpu:      WALKER_ERROR: 0x0
[  111.406270] amdgpu 0000:83:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[  111.406275] amdgpu 0000:83:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  111.406280] amdgpu 0000:83:00.0: amdgpu:      RW: 0x0
[  114.188710] amdgpu 0000:83:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:10 pasid:32769, for process rocm-bandwidth- pid 3286 thread rocm-bandwidth- pid 3286)
[  114.188729] amdgpu 0000:83:00.0: amdgpu:   in page starting at address 0x00007f0000000000 from client 10
[  114.188738] amdgpu 0000:83:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00A01A30
[  114.188746] amdgpu 0000:83:00.0: amdgpu:      Faulty UTCL2 client ID: SDMA0 (0xd)
[  114.188754] amdgpu 0000:83:00.0: amdgpu:      MORE_FAULTS: 0x0
[  114.188759] amdgpu 0000:83:00.0: amdgpu:      WALKER_ERROR: 0x0
[  114.188765] amdgpu 0000:83:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[  114.188770] amdgpu 0000:83:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  114.188776] amdgpu 0000:83:00.0: amdgpu:      RW: 0x0
[  114.302856] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=2
[  114.303173] amdgpu: failed to add hardware queue to MES, doorbell=0x1202
[  114.303176] amdgpu: MES might be in unrecoverable state, issue a GPU reset
[  114.303179] amdgpu: Failed to restore queue 0
[  114.303182] amdgpu: Failed to restore process queues
[  114.303184] amdgpu: Failed to restore queues of pasid 0x8001
[  114.303450] amdgpu 0000:83:00.0: amdgpu: GPU reset begin!
[  114.303477] amdgpu: Failed to evict queue 1
[  114.303483] amdgpu: Failed to suspend process 0x8002
[  114.309700] amdgpu 0000:83:00.0: amdgpu: recover vram bo from shadow start
[  114.309705] amdgpu 0000:83:00.0: amdgpu: recover vram bo from shadow done
[  114.412749] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[  114.413073] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
[  114.420094] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[  114.420379] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
[  114.523222] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[  114.523499] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
[  114.530476] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[  114.530750] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
[  114.634108] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[  114.634391] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
...
[  117.293167] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=2
[  117.293439] [drm:amdgpu_mes_add_hw_queue [amdgpu]] *ERROR* failed to add hardware queue to MES, doorbell=0x2200
[  117.293712] [drm:amdgpu_mes_self_test [amdgpu]] *ERROR* failed to add ring
[  117.294161] amdgpu 0000:83:00.0: amdgpu: GPU reset(1) succeeded!

Thanks for connecting @realGeorgeHotz. Appreciate the work you and tiny corp are doing. We are committed to working with the community and improving our support.  Lots of work ahead but excited about what we can do together.— Lisa Su (@LisaSu) June 16, 2023

I can reproduce this on my 7900 XTX as well

I am also hitting this

I am seeing similar messages from kernel on boot with phoenix apu based system and without the ROCM Stack
1637.604718] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14 [ 1637.605055] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait [ 1637.607290] [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000). [ 1637.607422] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming... [ 1637.610838] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully! [ 1637.803597] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 1637.803867] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully. [ 1637.804227] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 1637.804231] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 1637.804234] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 1637.804235] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [ 1637.804237] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [ 1637.804239] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 [ 1637.804241] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 [ 1637.804243] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 [ 1637.804245] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 [ 1637.804246] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 1637.804248] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8 [ 1637.804250] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8 [ 1637.804252] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0 [ 1637.809886] [drm] ring gfx_32803.1.1 was added [ 1637.810426] [drm] ring compute_32803.2.2 was added [ 1637.810934] [drm] ring sdma_32803.3.3 was added [ 1637.810962] [drm] ring gfx_32803.1.1 ib test pass [ 1637.810991] [drm] ring compute_32803.2.2 ib test pass [ 1637.811092] [drm] ring sdma_32803.3.3 ib test pass [ 1637.820482] PM: resume devices took 0.362 seconds [ 1637.820898] OOM killer enabled. [ 1637.820902] Restarting tasks ... done. [ 1637.822675] random: crng reseeded on system resumption [ 1637.829255] PM: suspend exit [ 1640.456439] wlp1s0: authenticate with 24:4b:fe:62:67:04 (local address=14:ac:60:46:7b:f9) [ 1640.479251] wlp1s0: send auth to 24:4b:fe:62:67:04 (try 1/3) [ 1640.499491] wlp1s0: authenticate with 24:4b:fe:62:67:04 (local address=14:ac:60:46:7b:f9) [ 1640.508904] wlp1s0: send auth to 24:4b:fe:62:67:04 (try 1/3) [ 1640.512391] wlp1s0: authenticated [ 1640.515427] wlp1s0: associate with 24:4b:fe:62:67:04 (try 1/3) [ 1640.526627] wlp1s0: RX AssocResp from 24:4b:fe:62:67:04 (capab=0x1511 status=0 aid=1) [ 1640.558571] wlp1s0: associated [ 1640.613407] wlp1s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 24:4b:fe:62:67:04 [ 1642.696635] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110) [ 1648.577999] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110) [ 2325.112034] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration [ 2531.128560] wlp1s0: deauthenticating from 24:4b:fe:62:67:04 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2531.678155] PM: suspend entry (s2idle) [ 2531.701397] Filesystems sync: 0.023 seconds [ 2531.710174] Freezing user space processes [ 2531.712040] Freezing user space processes completed (elapsed 0.001 seconds) [ 2531.712044] OOM killer disabled. [ 2531.712045] Freezing remaining freezable tasks [ 2531.713066] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 2531.713070] printk: Suspending console(s) (use no_console_suspend to debug) [ 2532.645147] PM: suspend devices took 0.932 seconds [ 2532.647493] ACPI: EC: interrupt blocked [ 9429.864695] ACPI: EC: interrupt unblocked [ 9430.036343] nvme nvme0: 16/0/0 default/read/poll queues [ 9430.088770] atkbd serio0: Unknown key pressed (translated set 2, code 0x6b on isa0060/serio0). [ 9430.088779] atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known. [ 9430.089328] atkbd serio0: Unknown key released (translated set 2, code 0x6b on isa0060/serio0). [ 9430.089336] atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known. [ 9430.175277] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14 [ 9430.175614] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait [ 9430.177835] [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000). [ 9430.177942] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming... [ 9430.181299] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully! [ 9430.286638] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 9430.286884] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully. [ 9430.287225] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 9430.287229] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 9430.287231] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 9430.287233] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [ 9430.287234] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [ 9430.287236] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 [ 9430.287237] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 [ 9430.287239] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 [ 9430.287241] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 [ 9430.287242] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 9430.287244] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8 [ 9430.287246] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8 [ 9430.287247] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0 [ 9430.292387] [drm] ring gfx_32803.1.1 was added [ 9430.292929] [drm] ring compute_32803.2.2 was added [ 9430.293440] [drm] ring sdma_32803.3.3 was added [ 9430.293469] [drm] ring gfx_32803.1.1 ib test pass [ 9430.293499] [drm] ring compute_32803.2.2 ib test pass [ 9430.293598] [drm] ring sdma_32803.3.3 ib test pass
💻 Framework Laptop 13 (AMD Ryzen 7040Series) (Laptop) running BIOS 3.3 (03.03) released 10/17/2023 and EC unknown
🐧 Fedora Linux 40 (KDE Plasma Prerelease)
🐧 Kernel 6.7.0fw13ec-rc1+
✅ AMD Ryzen 7 7840U w/ Radeon  780M Graphics (family 19 model 74)
✅ HSMP driver amd_hsmp not detected (blocked: False)
✅ PMC driver amd_pmc loaded (Program 0 Firmware 76.70.0)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.0.0-devel

Similar issue with 7900 XT, ROCm 5.7, kernel 6.5.11 (Fedora 39)
Although GPU recovery doesn't fully help it seems. While there are no MES errors and GPU stats (usage, power draw) seem to be back to normal, there's a lot of the following in the kernel logs:

[drm] Skip scheduling IBs!

Which keeps happening until a reboot.

I've had this exact issue frequently with ROCm 5.7 on Radeon RX 7900 XTX.
Upgrading to ROCm 6.0 has solved it for me.
At least Stable Diffusion with torch-2.3.0+rocm5.7 still works on ROCm 6.0, and without crashes now, no need to restart after a failed GPU reset.
The non-critical GCVM_L2_PROTECTION_FAULT_STATUS errors are still there, but they don't force me to restart after MES failure and a GPU reset attempt.
Currently working:
Linux moon 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
amdgpu-dkms/jammy,now 1:<IP_ADDRESS>000-1697589.22.04 all [installed]
amdgpu-install/jammy,now 6.0.60000-1697589.22.04 all [installed]

Also seeing this issue, on ROCm 6.0.2, Ubuntu 22.04 fresh setup when running llama.cpp. Hardware is a AMD 7940HS CPU w/ Radeon 780M GPU. When loading up larger models and offloading more layers to the GPU, most of the time the GPU will reset with the MES panic, or just hang with hundreds of [drm] Skip scheduling IBs! messages. When the GPU hangs like this, modprobe -r amdgpu causes a segfault (!?), and a dmesg report about a kernel bug (!?x2):
[ 6854.988626] ------------[ cut here ]------------
[ 6854.988627] kernel BUG at mm/slub.c:384!
[ 6854.988635] invalid opcode: 0000 [#1] SMP NOPTI
[ 6854.988637] CPU: 1 PID: 193444 Comm: modprobe Tainted: G           OE     5.15.0-94-generic #104-Ubuntu
[ 6854.988640] Hardware name: Micro Computer (HK) Tech Limited Venus series/F7BSC, BIOS 1.09 11/20/2023
[ 6854.988641] RIP: 0010:__slab_free+0x1f3/0x370

If an AMD engineer (or anyone else!) could point to a place to investigate, or has any other idea, that would be helpful!

5.15.0-94-generic

Any reason you want to run the older kernel?
A few people are experiencing better results on the newer kernels, and the 6.0.2 drivers.
I got to a running setup (with some minor issues) with the 6.5.x stock one - ended up closing my ticket too. #2689

I have no idea actually, I just went through a standard ubuntu server 22.04 setup from what I recall (via a netboot, so maybe the installer is missing the HWE option? I did not see it at least), after a quick sudo apt install -y linux-image-generic-hwe-22.04 and reboot, now on kernel 6.5.0-17-generic #17~22.04.1-Ubuntu things don't seem to have improved for me - I still get gpu resets:
│[33693.746423] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
│[33693.746596] amdgpu: failed to remove hardware queue from MES, doorbell=0x1002
│[33693.746606] amdgpu: MES might be in unrecoverable state, issue a GPU reset
│[33693.746614] amdgpu: Failed to evict queue 1
│[33693.746620] amdgpu: Failed to evict process queues
│[33693.746949] amdgpu 0000:c5:00.0: amdgpu: GPU reset begin!
│[33693.917504] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
│[33693.917664] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
│[33693.924953] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
│[33693.925108] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
│[33694.045099] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
│[33694.045218] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
│[33694.052583] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
│[33694.052702] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
│[33694.172644] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3

After that happens, the GPU is unusable until a full reboot.

 I've just captured a log with MES-related messages (and some others) from a system that was idle and hadn't even run a real workload yet. I don't know if this bug is related (because I don't have a clue what's on the other side of your blob wall or what much of this opaque code does) but there are MES messages, so, well, here we go.
[31317.644104] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005
[31317.644111] amdgpu 0000:0d:00.0: amdgpu: Failed to export SMU metrics table!
[31317.644112] amdgpu 0000:0d:00.0: amdgpu: Failed to get current clock freq!
[31321.920024] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005
[31321.920028] amdgpu 0000:0d:00.0: amdgpu: Failed to export SMU metrics table!
[31326.191767] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005
[31326.191772] amdgpu 0000:0d:00.0: amdgpu: Failed to export SMU metrics table!
[31327.729436] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=613206, emitted seq=613208
[31327.729995] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process plasmashell pid 3182 thread plasmashel:cs0 pid 3224
[31327.730545] amdgpu 0000:0d:00.0: amdgpu: GPU reset begin!
[31328.743414] amdgpu 0000:0d:00.0: amdgpu: IP block:gfx_v11_0 is hung!
[31329.767382] [drm:sdma_v6_0_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out
[31329.767916] amdgpu 0000:0d:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[31329.768161] [drm] kiq ring mec 3 pipe 1 q 0
[31330.008807] amdgpu 0000:0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring mes_kiq_3.1.0 test failed (-110)
[31330.009039] [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed
[31330.009290] amdgpu 0000:0d:00.0: amdgpu: soft reset failed, will fallback to full reset!
[31330.479483] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005
[31330.479487] amdgpu 0000:0d:00.0: amdgpu: Failed to export SMU metrics table!
[31334.746500] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005
[31334.746505] amdgpu 0000:0d:00.0: amdgpu: Failed to disable gfxoff!
[31339.013104] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005
[31339.013107] amdgpu 0000:0d:00.0: amdgpu: [SetDfCstate] failed!
[31339.013109] amdgpu 0000:0d:00.0: amdgpu: Failed to disallow df cstate
[31341.566559] [drm] psp gfx command INVOKE_CMD(0x3) failed and response status is (0x0)
[31345.514564] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31345.514834] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31345.636256] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31345.636512] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31345.757963] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31345.758218] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31345.879631] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31345.879887] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31346.001297] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31346.001552] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31346.122973] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31346.123230] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31346.244645] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31346.244900] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31346.366313] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31346.366568] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31346.487977] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[31346.488232] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[31348.539759] [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x0)
[31348.539764] [drm:psp_suspend [amdgpu]] *ERROR* Failed to terminate ras ta
[31348.540218] [drm:amdgpu_device_ip_suspend_phase2 [amdgpu]] *ERROR* suspend of IP block <psp> failed -22
[31348.541779] amdgpu 0000:0d:00.0: amdgpu: MODE1 reset
[31348.541783] amdgpu 0000:0d:00.0: amdgpu: GPU mode1 reset
[31348.541843] amdgpu 0000:0d:00.0: amdgpu: GPU smu mode1 reset
[31352.825254] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005
[31352.825259] amdgpu 0000:0d:00.0: amdgpu: GPU mode1 reset failed
[31352.825334] amdgpu 0000:0d:00.0: amdgpu: ASIC reset failed with error, -62 for drm dev, 0000:0d:00.0
[31357.080573] amdgpu 0000:0d:00.0: amdgpu: GPU reset succeeded, trying to resume
[31357.080830] [drm] PCIE GART of 512M enabled (table at 0x0000008000800000).
[31357.080897] [drm] VRAM is lost due to GPU reset!
[31357.080898] [drm] PSP is resuming...
[31357.320464] [drm:psp_hw_start [amdgpu]] *ERROR* PSP create ring failed!
[31357.320721] [drm:psp_resume [amdgpu]] *ERROR* PSP resume failed
[31357.320968] [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* resume of IP block <psp> failed -62
[31357.321238] [drm] Skip scheduling IBs!
[31357.321257] [drm] Skip scheduling IBs!

I'm thinking it's time to RMA my card. This is unfair to the card manufacturer and retailer who have to deal with this, only reason I've been putting it off. But come on, really, what is this?
Full details:
I returned to my Kubuntu install that I was trying to do real work on, but after cold booting the system and logging in, I ended up just going to bed. Aside from displaying a KDE plasma desktop on Wayland, the GPU didn't do anything taxing. I woke up to find my screen off and system unresponsive, so I logged in over SSH from another computer and retrieved this log from dmesg. Kernel is 6.5.0-17-generic.
So, wait... AMD cards aren't even stable handling a basic plasmashell desktop? Really?
Also I want to take this opportunity to clarify my position to AMD's engineers. I'm not mad at you.  I think we're on the same team. I'm furious at the company and the situation though, because I feel lied to, scammed even. My messages here are not intended to be hostile, however, and I want to indicate that I am, you know, capable of calm discussion. I'm not going to just jump on anyone who tries to help.
PS: if recent kernels help, with patches not backported into the fresh-install Ubuntu kernel the AMD documentation implicitly assumes, then said documentation should include instructions on installing an updated kernel. Thanks for bringing that up terryrankine.

PS: if recent kernels help, with patches not backported into the fresh-install Ubuntu kernel the AMD documentation implicitly assumes, then said documentation should include instructions on installing an updated kernel. Thanks for bringing that up terryrankine.

Sadly it did not help me :( High VRAM workloads still cause the MES unrecoverable error, every time, which requires a reboot to solve.

Sadly it did not help me :( High VRAM workloads still cause the MES unrecoverable error, every time, which requires a reboot to solve.

That is also the case for me - hey, it's weird how using more VRAM makes it more likely, isn't? Maybe some allocator race? ... really though, AMD should be paying me even to speculate about what's going wrong on the proprietary side.
Also I said before that I thought it wasn't helpful for me to add a "same here" but I've realized, anyone having this issue should absolutely post about it here. Let 'em see us.
From statements like "We are hoping that this will improve your perception of AMD products and this will be reflected in your public messaging", we know that public perception is what the company cares about, not whether people are having an issue. Let your public messaging reflect your actual perception.

On my arch installation I have run into this issue multiple times with rocm 5.6-6.0. I can't even open blender or libreoffice with hardware acceleration enabled. llama.cpp (with CLBlast) crashes even without offloading layers to GPU Especially OpenCL workloads seem to be problematic. Running a very simple kernel arr[get_global_id(0)] += num; triggers the page fault error, but that seems to not be a problem. Looping over that code<PHONE_NUMBER>24 times causes the driver to timeout and reset recoverably. I even tried allocating a 16GB buffer, which worked fine. I wasn't able to reproduce the MES error. However starting llama.cpp caused it again. On ubuntu pytorch mostly works, but blender and llama.cpp still cause unrecoverable gpu crashes. I hope this gets fixed soon as I wasn't able to use my card for anything else than graphics. I never really had problems with vulkan or OpenGL, it's just ROCm that appears to be broken.

and just checking - you are on new kernels with the 6.0.2 binaries or your code compiled against the 6.0.2 libs? (yes - i have had to compile pytorch against 6.0.2).
mainly because i finally got there - and closed my ticket.... #2689
Im not saying it wasnt easy or simple but I can hit 20-22Gb consistently somehow now.... and Im over like 3 days of uptime too... which is a first since november last year...
terryr@theblob:~$ uname -a
Linux theblob 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb  7 11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

terryr@theblob:~$ hipconfig
HIP version  : 6.0.32831-204d35d16

== hipconfig
HIP_PATH     : /opt/rocm-6.0.2
ROCM_PATH    : /opt/rocm-6.0.2
HIP_COMPILER : clang
HIP_PLATFORM : amd
HIP_RUNTIME  : rocclr
CPP_CONFIG   :  -D__HIP_PLATFORM_HCC__= -D__HIP_PLATFORM_AMD__= -I/opt/rocm-6.0.2/include -I/opt/rocm-6.0.2/lib/llvm/lib/clang/17.0.0

and here is the worst ever way to show what ubuntu libs got me there....
terryr@theblob:~$ dpkg -l | grep -E "rocm|hip|AMD "
ii  amd-smi-lib                                    <IP_ADDRESS>002-115~22.04                     amd64        AMD System Management libraries
ii  amd64-microcode                                3.20191218.1ubuntu2.2                      amd64        Processor microcode firmware for AMD CPUs
ii  composablekernel-dev                           <IP_ADDRESS>002-115~22.04                      amd64        High Performance Composable Kernel for AMD GPUs
ii  hip-dev                                        6.0.32831.60002-115~22.04                  amd64        HIP:Heterogenous-computing Interface for Portability
ii  hip-doc                                        6.0.32831.60002-115~22.04                  amd64        HIP:Heterogenous-computing Interface for Portability
ii  hip-runtime-amd                                6.0.32831.60002-115~22.04                  amd64        HIP:Heterogenous-computing Interface for Portability
ii  hip-samples                                    6.0.32831.60002-115~22.04                  amd64        HIP: Heterogenous-computing Interface for Portability [HIP SAMPLES]
ii  hipblas                                        <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute BLAS marshalling library
ii  hipblas-dev                                    <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute BLAS marshalling library
ii  hipblaslt                                      <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute BLAS marshalling library
ii  hipblaslt-dev                                  <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute BLAS marshalling library
ii  hipcc                                          <IP_ADDRESS>002-115~22.04                      amd64        HIP Compiler Driver
ii  hipcub-dev                                     <IP_ADDRESS>002-115~22.04                      amd64        hipCUB (rocPRIM backend)
ii  hipfft                                         <IP_ADDRESS>002-115~22.04                     amd64        ROCm FFT marshalling library
ii  hipfft-dev                                     <IP_ADDRESS>002-115~22.04                     amd64        ROCm FFT marshalling library
ii  hipfort-dev                                    <IP_ADDRESS>002-115~22.04                      amd64        Fortran Interface For GPU Kernel Libraries
ii  hipify-clang                                   <IP_ADDRESS>002-115~22.04                     amd64        Hipify CUDA source
ii  hiprand                                        <IP_ADDRESS>002-115~22.04                    amd64        Radeon Open Compute RAND library
ii  hiprand-dev                                    <IP_ADDRESS>002-115~22.04                    amd64        Radeon Open Compute RAND library
ii  hipsolver                                      <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute LAPACK marshalling library
ii  hipsolver-dev                                  <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute LAPACK marshalling library
ii  hipsparse                                      <IP_ADDRESS>002-115~22.04                      amd64        ROCm SPARSE library
ii  hipsparse-dev                                  <IP_ADDRESS>002-115~22.04                      amd64        ROCm SPARSE library
ii  hiptensor                                      <IP_ADDRESS>002-115~22.04                      amd64        Adaptation library of tensor contraction with composable_kernel backend
ii  hiptensor-dev                                  <IP_ADDRESS>002-115~22.04                      amd64        Adaptation library of tensor contraction with composable_kernel backend
ii  hsa-amd-aqlprofile                             <IP_ADDRESS>002.60002-115~22.04                amd64        AQLPROFILE library for AMD HSA runtime API extension support
ii  hsa-rocr                                       <IP_ADDRESS>002-115~22.04                     amd64        AMD Heterogeneous System Architecture HSA - Linux HSA Runtime for Boltzmann (ROCm) platforms
ii  hsa-rocr-dev                                   <IP_ADDRESS>002-115~22.04                     amd64        AMD Heterogeneous System Architecture HSA development package.
ii  libflashrom1:amd64                             1.2-5build1                                amd64        Identify, read, write, erase, and verify BIOS/ROM/flash chips - library
ii  libresid-builder0c2a                           2.1.1-15ubuntu2                            amd64        SID chip emulation class based on resid
ii  miopen-hip                                     <IP_ADDRESS>002-115~22.04                     amd64        AMD's DNN Library
ii  miopen-hip-dev                                 <IP_ADDRESS>002-115~22.04                     amd64        AMD's DNN Library
ii  mivisionx                                      <IP_ADDRESS>002-115~22.04                      amd64        AMD MIVisionX is a comprehensive Computer Vision and ML Inference Toolkit
ii  rocblas                                        <IP_ADDRESS>002-115~22.04                      amd64        rocBLAS is AMD's library for BLAS on ROCm. It is implemented in HIP and optimized for AMD GPUs.
ii  rocblas-dev                                    <IP_ADDRESS>002-115~22.04                      amd64        rocBLAS is AMD's library for BLAS on ROCm. It is implemented in HIP and optimized for AMD GPUs.
ii  rocm                                           <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) software stack meta package
ii  rocm-clang-ocl                                 <IP_ADDRESS>002-115~22.04                      amd64        OpenCL compilation with clang compiler.
ii  rocm-cmake                                     <IP_ADDRESS>002-115~22.04                     amd64        rocm-cmake built using CMake
ii  rocm-core                                      <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-dbgapi                                    <IP_ADDRESS>002-115~22.04                     amd64        Library to provide AMD GPU debugger API
ii  rocm-debug-agent                               <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute Debug Agent (ROCdebug-agent)
ii  rocm-dev                                       <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-developer-tools                           <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-device-libs                               <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute - device libraries
ii  rocm-gdb                                       13.2.60002-115~22.04                       amd64        ROCgdb
ii  rocm-hip-libraries                             <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-hip-runtime                               <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-hip-runtime-dev                           <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-hip-sdk                                   <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-language-runtime                          <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-libs                                      <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-llvm                                      <IP_ADDRESS>12.60002-115~22.04               amd64        ROCm compiler
ii  rocm-ml-libraries                              <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-ml-sdk                                    <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-ocl-icd                                   <IP_ADDRESS>002-115~22.04                      amd64        clr built using CMake
ii  rocm-opencl                                    <IP_ADDRESS>002-115~22.04                      amd64        clr built using CMake
ii  rocm-opencl-dev                                <IP_ADDRESS>002-115~22.04                      amd64        clr built using CMake
ii  rocm-opencl-runtime                            <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-opencl-sdk                                <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocm-openmp-sdk                                <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) OpenMP Software development Kit.
ii  rocm-smi-lib                                   <IP_ADDRESS>002-115~22.04                      amd64        AMD System Management libraries
ii  rocm-utils                                     <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime software stack
ii  rocminfo                                       <IP_ADDRESS>002-115~22.04                      amd64        Radeon Open Compute (ROCm) Runtime rocminfo tool
ii  rocprofiler                                    2.0.60002.60002-115~22.04                  amd64        ROCPROFILER library for AMD HSA runtime API extension support
ii  rocprofiler-dev                                2.0.60002.60002-115~22.04                  amd64        ROCPROFILER library for AMD HSA runtime API extension support
ii  rocprofiler-plugins                            2.0.60002.60002-115~22.04                  amd64        ROCPROFILER library for AMD HSA runtime API extension support
ii  rocsolver                                      <IP_ADDRESS>002-115~22.04                     amd64        AMD ROCm SOLVER library
ii  rocsolver-dev                                  <IP_ADDRESS>002-115~22.04                     amd64        AMD ROCm SOLVER library
ii  roctracer                                      4.1.60002.60002-115~22.04                  amd64        AMD ROCTRACER library
ii  roctracer-dev                                  4.1.60002.60002-115~22.04                  amd64        AMD ROCTRACER library

and then made pytorch find the folder and run the special pytorch convert from cuda to hip and then build, and then build and install, and then build pytorchvision and audio after.... so much faf.....
But - I run now....

Yes, I made sure to reinstall rocm 6.0.2, and do a clean build of llama.cpp - No change for me sadly. I might try it again to see if I missed something, always possible.
Out of curiosity, what mode is you apu in for VRAM? auto or do you have it set to dedicated mode?

I might have a workaround that maybe helps a little, or it might just be placebo / luck so far. There are potential drawbacks, though.
I noticed that sometimes, but not always, there would be IOMMU fault messages prior to the ones from the amdgpu driver itself. So I thought, hey why not, let's try disabling IOMMU in BIOS. And so far, I've been able to run things ... I don't trust it, obviously even if this works it's not a solution, but I thought I'd share. Those faults were obviously happening for a reason and this seems to just be putting a blindfold on.
Here's a chat with Gemini about the consequences of disabling IOMMU https://g.co/gemini/share/5d21ada997c1 , please weigh it up yourself before trying it. I don't understand IOMMU properly myself.
PS: I captured this earlier after booting my system and leaving it idle, not even logging in yet:
[  555.894238] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005

(and then the usual circus follows - this is just the start for demonstration)
So not even 10 minutes, under no load, with nothing loaded except a Kubuntu login screen. Something is very wrong.

Yesterday I tried running some AI workloads with ROCm 6.0.0 and PyTorch ROCm 6.0 on my main system, but already very simple tensor operations with pytorch crashed the driver with the MES failed to response messages. I then booted into ubuntu (the same version of ROCm), retried the same tensor operations there and it worked mostly fine. I then upgraded to ROCm on ubuntu to the newest version and it still worked. Today I booted into my arch installation again, which still has ROCm 6.0.0, but even running heavy workloads like Stable Diffusion and llama.cpp work fine, even at 18/20GB VRAM. My best guess is that upgrading ROCm on ubuntu also installed a firmware update for the GPU, but I'm not certain that the firmware was the root cause.
Anyways, I'll watch how well ROCm performs over the next few days as there are still harmless page faults appearing out of nowhere.

I'm getting "MES failed to response" with ROCM 6.0.2, freshly updated.

Using an RX 7900 XTX with no monitor attached, getting output from another GPU.
Still seeing MES caused hangs with Arch Linux 6.8 / ROCm 6.0.2 / PyTorch 2.4.0.dev20240323+rocm6.0
This MES hang causes other unrelated Python programs to core dump too.
Only way to recover from the hang is running rocm-smi --gpureset -id 0

Yeah it keeps happening here with 6.0.2 as well.

I might have a workaround that maybe helps a little, or it might just be placebo / luck so far. There are potential drawbacks, though.
I noticed that sometimes, but not always, there would be IOMMU fault messages prior to the ones from the amdgpu driver itself. So I thought, hey why not, let's try disabling IOMMU in BIOS. And so far, I've been able to run things ... I don't trust it, obviously even if this works it's not a solution, but I thought I'd share. Those faults were obviously happening for a reason and this seems to just be putting a blindfold on.
Here's a chat with Gemini about the consequences of disabling IOMMU https://g.co/gemini/share/5d21ada997c1 , please weigh it up yourself before trying it. I don't understand IOMMU properly myself.
PS: I captured this earlier after booting my system and leaving it idle, not even logging in yet:
[  555.894238] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000012 SMN_C2PMSG_82:0x00000005

(and then the usual circus follows - this is just the start for demonstration) So not even 10 minutes, under no load, with nothing loaded except a Kubuntu login screen. Something is very wrong.

Hey, I got the same issue that you are having somewhat with my RX 6800 same error you mentioned and exact same command it's trying to sent(SMN_C2PMSG_66) https://gitlab.freedesktop.org/drm/amd/-/issues/3220

Same issue. Any help?

from my own observations, the MES seems to destabilize as the usable VRAM becomes low. I could be very wrong about this, but I tried limiting the amount of usable VRAM with module parameters (vramlimit, vis_vramlimit), and that does seem to help.
Interested to see if this works for others.

Okay, I don't want to hype anybody up unduly, but I haven't seen a MES hang since I installed the week-old AMD firmware update. Can anyone repro on that?

Will see if it fixes my unrelated issue as well, apparently they where working on fixing mine already and had a fixed testing unreleased firmware as of month ago. Hoping AMD gets their act together, not sure if my distro is running it though how could I even tell exactly?

You can just clone the repo (git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git --depth 1, then sudo cp amdgpu/* /lib/firmware/updates/amdgpu/ and reboot (note: this is untested, hot off the presses, and also your system will overwrite this when it updates anyway, I take no responsibility for damages etc.)

I don't want to jinx it but so far I am having no crashes with my SMU bug anymore, also my cursor doesn't freeze like before when generating images. I haven't downloaded the latest firmware though, just using newest from my distro

So far not having any crashes with my distros latest, still having the cursor stutters bug perhaps unrelated and if so that's just mildly annoying and can live with that. Don't want to jinx it though so going to let to generate idle, if it crashes I guess I'll look into updating my firmware

Nevermind everyone, sorry for the premature excitement. Two days later, there it goes again.

grep MES /sys/kernel/debug/dri/{0,1}/amdgpu_firmware_info

Huh mine seems to say
/sys/kernel/debug/dri/1/amdgpu_firmware_info:MES_KIQ feature version: 0, firmware version: 0x00000000
/sys/kernel/debug/dri/1/amdgpu_firmware_info:MES feature version: 0, firmware version: 0x00000000

Could it be that my card is too old or something? Pretty sure it was applied though, running Ubuntu just for testing, also going to try to run ROCm 6.1 which might have some fixes for issue I am having as well as others

This MES crash tends to segfault other unrelated programs as well.
This one in particular was interesting. Entire system locked up a few minutes after this screenshot:
(I use an Intel dGPU for video out.)

Journalctl in reverse order.

(Physically cutted power at this point since nothing on the system was responding to anything)

Apr 29 00:58:23 ArchDesktop kernel: general protection fault, probably for non-canonical address 0x1293823692cd285f: 0000 [#4] PREEMPT SMP NOPTI
Apr 29 00:58:23 ArchDesktop sudo[1733267]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:23 ArchDesktop sudo[1733267]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:23 ArchDesktop sudo[1733187]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:22 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:22 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:22 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:22 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:22 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:22 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:22 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:22 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:22 ArchDesktop sudo[1733187]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:22 ArchDesktop sudo[1733187]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:22 ArchDesktop sudo[1733115]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:21 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:21 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:20 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:20 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:20 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:20 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:20 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:20 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:20 ArchDesktop sudo[1733115]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:20 ArchDesktop sudo[1733115]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:20 ArchDesktop sudo[1732935]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:20 ArchDesktop kernel: ---[ end trace<PHONE_NUMBER>000000 ]---
Apr 29 00:58:20 ArchDesktop kernel:  </TASK>
Apr 29 00:58:20 ArchDesktop kernel: R13: 000000c000a8a530 R14: 000000c000a08380 R15: 0000000fffffffff
Apr 29 00:58:20 ArchDesktop kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000000 R12:<PHONE_NUMBER>64cfa4
Apr 29 00:58:20 ArchDesktop kernel: RBP: 000070489b3ffd78 R08:<PHONE_NUMBER>000020 R09:<PHONE_NUMBER>000001
Apr 29 00:58:20 ArchDesktop kernel: RDX: 000070489b3ffdb8 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>d13d44
Apr 29 00:58:20 ArchDesktop kernel: RAX:<PHONE_NUMBER>000000 RBX:<PHONE_NUMBER>484420 RCX:<PHONE_NUMBER>64cfa4
Apr 29 00:58:20 ArchDesktop kernel: RSP: 002b:000070489b3ffc08 EFLAGS: 00010287
Apr 29 00:58:20 ArchDesktop kernel: Code: 36 45 31 db eb 31 4c 63 de 66 0f 1f 84 00 00 00 00 00 0f 1f 00 49 81 fb 00 00 10 00 0f 83 9b 00 00 00 4c 8b a4 24 68 01 00 00 <41> 84 04 24 49 c1 e3 04 47 0f b6 1c 1c 41 80 fb 16 75 24 44 0f b6
Apr 29 00:58:20 ArchDesktop kernel: RIP: 0033:0xd69e95
Apr 29 00:58:20 ArchDesktop kernel:  rewind_stack_and_make_dead+0x17/0x20
Apr 29 00:58:20 ArchDesktop kernel:  make_task_dead+0x83/0x170
Apr 29 00:58:20 ArchDesktop kernel:  ? do_exit+0x70/0xb70
Apr 29 00:58:20 ArchDesktop kernel:  ? do_exit+0x90f/0xb70
Apr 29 00:58:20 ArchDesktop kernel:  ? asm_exc_invalid_op+0x1a/0x20
Apr 29 00:58:20 ArchDesktop kernel:  ? exc_invalid_op+0x19/0xc0
Apr 29 00:58:20 ArchDesktop kernel:  ? handle_bug+0x3c/0x80
Apr 29 00:58:20 ArchDesktop kernel:  ? report_bug+0x202/0x270
Apr 29 00:58:20 ArchDesktop kernel:  ? do_exit+0x90f/0xb70
Apr 29 00:58:20 ArchDesktop kernel:  ? __warn+0x81/0x1b0
Apr 29 00:58:20 ArchDesktop kernel:  <TASK>
Apr 29 00:58:20 ArchDesktop kernel: Call Trace:
Apr 29 00:58:20 ArchDesktop kernel: PKRU: 55555554
Apr 29 00:58:20 ArchDesktop kernel: CR2:<PHONE_NUMBER>64cfa4 CR3:<PHONE_NUMBER>2c2000 CR4:<PHONE_NUMBER>f50ef0
Apr 29 00:58:20 ArchDesktop kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Apr 29 00:58:20 ArchDesktop kernel: FS:  000070489b4006c0(0000) GS:ffff899c7edc0000(0000) knlGS:0000000000000000
Apr 29 00:58:20 ArchDesktop kernel: R13: ffff899181094a40 R14:<PHONE_NUMBER>000000 R15:<PHONE_NUMBER>000000
Apr 29 00:58:20 ArchDesktop kernel: R10: ffff899caf2478c0 R11:<PHONE_NUMBER>000003 R12:<PHONE_NUMBER>00000b
Apr 29 00:58:20 ArchDesktop kernel: RBP: ffff8991810a3600 R08: 00000000ffffffea R09:<PHONE_NUMBER>01bdd0
Apr 29 00:58:20 ArchDesktop kernel: RDX:<PHONE_NUMBER>000001 RSI:<PHONE_NUMBER>002710 RDI: ffff899181094a40
Apr 29 00:58:20 ArchDesktop kernel: RAX:<PHONE_NUMBER>000000 RBX: ffff8991e52ba380 RCX:<PHONE_NUMBER>000000
Apr 29 00:58:20 ArchDesktop kernel: RSP: 0000:ffff9db8518d3ed8 EFLAGS: 00010282
Apr 29 00:58:20 ArchDesktop kernel: Code: 47 0c 6c 00 e9 f5 fd ff ff 48 8d 7d 18 e8 d9 7e 08 00 e9 fd f7 ff ff 48 8b bb 08 06 00 00 31 f6 e8 76 e0 ff ff e9 42 fd ff ff <0f> 0b e9 68 f7 ff ff 0f 0b e9 25 f7 ff ff 4c 89 e6 bf 05 06 00 00
Apr 29 00:58:20 ArchDesktop kernel: RIP: 0010:do_exit+0x90f/0xb70
Apr 29 00:58:20 ArchDesktop kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 5003 10/07/2023
Apr 29 00:58:20 ArchDesktop kernel: CPU: 15 PID: 1432 Comm: containerd Tainted: G      D    OE      6.8.4-zen1-1-zen #1 4a88f2661038c2a3bb69aa70fb41a5735338823c
Apr 29 00:58:20 ArchDesktop kernel:  acpi_cpufreq k10temp i2c_piix4 mei snd_hwdep ptp xor pps_core raid6_pq dca mousedev joydev libcrc32c ryzen_smu(OE) mac_hid snd_aloop snd_pcm snd_timer snd soundcore i2c_dev sr_mod cdrom v4l2loopback(OE) videodev mc sg crypto_user dm_mod loop fuse nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic xe drm_gpuvm usbhid amdgpu i915 amdxcp drm_ttm_helper intel_gtt drm_exec video gpu_sched i2c_algo_bit ttm drm_suballoc_helper nvme drm_buddy crc32c_intel drm_display_helper nvme_core xhci_pci cec nvme_auth xhci_pci_renesas wmi
Apr 29 00:58:20 ArchDesktop kernel: Modules linked in: ip6table_filter ip6_tables xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter br_netfilter snd_seq_dummy snd_hrtimer snd_seq snd_seq_device macvtap macvlan vhost_net vhost vhost_iotlb tap tun overlay bridge stp llc nct6775 nct6775_core hwmon_vid jc42 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi mei_pxp mei_hdcp cdc_mbim cdc_wdm intel_rapl_msr intel_rapl_common kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel eeepc_wmi sha512_ssse3 asus_wmi sha256_ssse3 ledtrig_audio sha1_ssse3 nls_iso8859_1 platform_profile aesni_intel vfat cdc_ncm i8042 crypto_simd sparse_keymap cdc_ether fat asus_ec_sensors snd_hda_intel cryptd serio usbnet snd_intel_dspcfg mii btrfs rapl rfkill snd_intel_sdw_acpi mei_gsc snd_hda_codec mxm_wmi sp5100_tco igb mei_me pcspkr snd_hda_core ccp wmi_bmof blake2b_generic
Apr 29 00:58:20 ArchDesktop kernel: WARNING: CPU: 15 PID: 1432 at kernel/exit.c:820 do_exit+0x90f/0xb70
Apr 29 00:58:20 ArchDesktop kernel: ------------[ cut here ]------------
Apr 29 00:58:20 ArchDesktop kernel: PKRU: 55555554
Apr 29 00:58:20 ArchDesktop kernel: CR2:<PHONE_NUMBER>64cfa4 CR3:<PHONE_NUMBER>2c2000 CR4:<PHONE_NUMBER>f50ef0
Apr 29 00:58:20 ArchDesktop kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Apr 29 00:58:20 ArchDesktop kernel: FS:  000070489b4006c0(0000) GS:ffff899c7edc0000(0000) knlGS:0000000000000000
Apr 29 00:58:20 ArchDesktop kernel: R13: ffff899180245500 R14:<PHONE_NUMBER>000068 R15:<PHONE_NUMBER>cd282f
Apr 29 00:58:20 ArchDesktop kernel: R10:<PHONE_NUMBER>000001 R11: ffff899caf37bd80 R12:<PHONE_NUMBER>408d40
Apr 29 00:58:20 ArchDesktop kernel: RBP: ffff9db855d07a58 R08:<PHONE_NUMBER>000001 R09:<PHONE_NUMBER>000000
Apr 29 00:58:20 ArchDesktop kernel: RDX:<PHONE_NUMBER>1fb80f RSI:<PHONE_NUMBER>03b580 RDI: ffff89988cf8e3c0
Apr 29 00:58:20 ArchDesktop kernel: RAX:<PHONE_NUMBER>cd285f RBX: 5247cd920044d7d0 RCX:<PHONE_NUMBER>000001
Apr 29 00:58:20 ArchDesktop kernel: RSP: 0018:ffff9db855d07a20 EFLAGS: 00010206
Apr 29 00:58:20 ArchDesktop kernel: Code: 08 48 83 78 10 00 4c 8b 38 0f 84 ab 01 00 00 4d 85 ff 0f 84 a2 01 00 00 41 8b 45 28 49 8b 9d b8 00 00 00 49 8b 75 00 4c 01 f8 <48> 33 18 48 89 c1 4c 89 f8 48 0f c9 48 31 cb 48 8d 8a 00 02 00 00
Apr 29 00:58:20 ArchDesktop kernel: RIP: 0010:kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:20 ArchDesktop kernel: ---[ end trace<PHONE_NUMBER>000000 ]---
Apr 29 00:58:20 ArchDesktop kernel:  acpi_cpufreq k10temp i2c_piix4 mei snd_hwdep ptp xor pps_core raid6_pq dca mousedev joydev libcrc32c ryzen_smu(OE) mac_hid snd_aloop snd_pcm snd_timer snd soundcore i2c_dev sr_mod cdrom v4l2loopback(OE) videodev mc sg crypto_user dm_mod loop fuse nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic xe drm_gpuvm usbhid amdgpu i915 amdxcp drm_ttm_helper intel_gtt drm_exec video gpu_sched i2c_algo_bit ttm drm_suballoc_helper nvme drm_buddy crc32c_intel drm_display_helper nvme_core xhci_pci cec nvme_auth xhci_pci_renesas wmi
Apr 29 00:58:20 ArchDesktop kernel: Modules linked in: ip6table_filter ip6_tables xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter br_netfilter snd_seq_dummy snd_hrtimer snd_seq snd_seq_device macvtap macvlan vhost_net vhost vhost_iotlb tap tun overlay bridge stp llc nct6775 nct6775_core hwmon_vid jc42 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi mei_pxp mei_hdcp cdc_mbim cdc_wdm intel_rapl_msr intel_rapl_common kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel eeepc_wmi sha512_ssse3 asus_wmi sha256_ssse3 ledtrig_audio sha1_ssse3 nls_iso8859_1 platform_profile aesni_intel vfat cdc_ncm i8042 crypto_simd sparse_keymap cdc_ether fat asus_ec_sensors snd_hda_intel cryptd serio usbnet snd_intel_dspcfg mii btrfs rapl rfkill snd_intel_sdw_acpi mei_gsc snd_hda_codec mxm_wmi sp5100_tco igb mei_me pcspkr snd_hda_core ccp wmi_bmof blake2b_generic
Apr 29 00:58:20 ArchDesktop kernel:  </TASK>
Apr 29 00:58:20 ArchDesktop kernel: R13: 000000c000a8a530 R14: 000000c000a08380 R15: 0000000fffffffff
Apr 29 00:58:20 ArchDesktop kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000000 R12:<PHONE_NUMBER>64cfa4
Apr 29 00:58:20 ArchDesktop kernel: RBP: 000070489b3ffd78 R08:<PHONE_NUMBER>000020 R09:<PHONE_NUMBER>000001
Apr 29 00:58:20 ArchDesktop kernel: RDX: 000070489b3ffdb8 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>d13d44
Apr 29 00:58:20 ArchDesktop kernel: RAX:<PHONE_NUMBER>000000 RBX:<PHONE_NUMBER>484420 RCX:<PHONE_NUMBER>64cfa4
Apr 29 00:58:20 ArchDesktop kernel: RSP: 002b:000070489b3ffc08 EFLAGS: 00010287
Apr 29 00:58:20 ArchDesktop kernel: Code: 36 45 31 db eb 31 4c 63 de 66 0f 1f 84 00 00 00 00 00 0f 1f 00 49 81 fb 00 00 10 00 0f 83 9b 00 00 00 4c 8b a4 24 68 01 00 00 <41> 84 04 24 49 c1 e3 04 47 0f b6 1c 1c 41 80 fb 16 75 24 44 0f b6
Apr 29 00:58:20 ArchDesktop kernel: RIP: 0033:0xd69e95
Apr 29 00:58:20 ArchDesktop kernel:  asm_exc_page_fault+0x26/0x30
Apr 29 00:58:20 ArchDesktop kernel:  exc_page_fault+0x7f/0x180
Apr 29 00:58:20 ArchDesktop kernel:  do_user_addr_fault+0x1e1/0xb50
Apr 29 00:58:20 ArchDesktop kernel:  handle_mm_fault+0x1468/0x1510
Apr 29 00:58:20 ArchDesktop kernel:  do_read_fault+0x44/0x1c0
Apr 29 00:58:20 ArchDesktop kernel:  __do_fault+0x35/0x120
Apr 29 00:58:20 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:20 ArchDesktop kernel:  ? try_to_wake_up+0x343/0xcd0
Apr 29 00:58:20 ArchDesktop kernel:  ? filemap_map_pages+0x443/0x500
Apr 29 00:58:20 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:20 ArchDesktop kernel:  filemap_fault+0x54d/0x1240
Apr 29 00:58:20 ArchDesktop kernel:  page_cache_ra_unbounded+0x106/0x180
Apr 29 00:58:20 ArchDesktop kernel:  read_pages+0x85/0x250
Apr 29 00:58:20 ArchDesktop kernel:  ext4_mpage_readpages+0x68e/0xb60 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:20 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:20 ArchDesktop kernel:  ext4_map_blocks+0x270/0x730 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:20 ArchDesktop kernel:  ext4_ext_map_blocks+0xa1/0x1b00 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:20 ArchDesktop kernel:  ext4_find_extent.constprop.0+0x142/0x2f0 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:20 ArchDesktop kernel:  __read_extent_tree_block+0x68/0x170 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:20 ArchDesktop kernel:  ? select_task_rq_fair+0x6c4/0x1ae0
Apr 29 00:58:20 ArchDesktop kernel:  bdev_getblk+0x13b/0x270
Apr 29 00:58:20 ArchDesktop kernel:  folio_alloc_buffers+0xee/0x230
Apr 29 00:58:20 ArchDesktop kernel:  ? folio_alloc_buffers+0xee/0x230
Apr 29 00:58:20 ArchDesktop kernel:  ? kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:20 ArchDesktop kernel:  ? asm_exc_general_protection+0x26/0x30
Apr 29 00:58:20 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:20 ArchDesktop kernel:  ? exc_general_protection+0x388/0x4a0
Apr 29 00:58:20 ArchDesktop kernel:  ? die_addr+0x128/0x130
Apr 29 00:58:20 ArchDesktop kernel:  <TASK>
Apr 29 00:58:20 ArchDesktop kernel: Call Trace:
Apr 29 00:58:20 ArchDesktop kernel: PKRU: 55555554
Apr 29 00:58:20 ArchDesktop kernel: CR2:<PHONE_NUMBER>64cfa4 CR3:<PHONE_NUMBER>2c2000 CR4:<PHONE_NUMBER>f50ef0
Apr 29 00:58:20 ArchDesktop kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Apr 29 00:58:20 ArchDesktop kernel: FS:  000070489b4006c0(0000) GS:ffff899c7edc0000(0000) knlGS:0000000000000000
Apr 29 00:58:20 ArchDesktop kernel: R13: ffff899180245500 R14:<PHONE_NUMBER>000068 R15:<PHONE_NUMBER>cd282f
Apr 29 00:58:20 ArchDesktop kernel: R10:<PHONE_NUMBER>000001 R11: ffff899caf37bd80 R12:<PHONE_NUMBER>400d48
Apr 29 00:58:20 ArchDesktop kernel: RBP: ffff9db8518d3838 R08:<PHONE_NUMBER>000001 R09:<PHONE_NUMBER>00000f
Apr 29 00:58:20 ArchDesktop kernel: RDX:<PHONE_NUMBER>1fb80f RSI:<PHONE_NUMBER>03b580 RDI: ffff8991c7b61280
Apr 29 00:58:20 ArchDesktop kernel: RAX:<PHONE_NUMBER>cd285f RBX: 5247cd920044d7d0 RCX:<PHONE_NUMBER>000001
Apr 29 00:58:20 ArchDesktop kernel: RSP: 0000:ffff9db8518d3800 EFLAGS: 00010206
Apr 29 00:58:20 ArchDesktop kernel: Code: 08 48 83 78 10 00 4c 8b 38 0f 84 ab 01 00 00 4d 85 ff 0f 84 a2 01 00 00 41 8b 45 28 49 8b 9d b8 00 00 00 49 8b 75 00 4c 01 f8 <48> 33 18 48 89 c1 4c 89 f8 48 0f c9 48 31 cb 48 8d 8a 00 02 00 00
Apr 29 00:58:20 ArchDesktop kernel: RIP: 0010:kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:20 ArchDesktop kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 5003 10/07/2023
Apr 29 00:58:20 ArchDesktop kernel: CPU: 15 PID: 1432 Comm: containerd Tainted: G      D    OE      6.8.4-zen1-1-zen #1 4a88f2661038c2a3bb69aa70fb41a5735338823c
Apr 29 00:58:20 ArchDesktop kernel: general protection fault, probably for non-canonical address 0x1293823692cd285f: 0000 [#3] PREEMPT SMP NOPTI
Apr 29 00:58:19 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:19 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:19 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:19 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:19 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:19 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:19 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:19 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:19 ArchDesktop sudo[1732935]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:19 ArchDesktop sudo[1732935]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:19 ArchDesktop sudo[1732870]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:18 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:18 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:17 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:17 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:17 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:17 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:17 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:17 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:17 ArchDesktop sudo[1732870]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:17 ArchDesktop sudo[1732870]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:17 ArchDesktop sudo[1732798]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:16 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:16 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:16 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:16 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:16 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:16 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:16 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:16 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:16 ArchDesktop sudo[1732798]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:16 ArchDesktop sudo[1732798]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:16 ArchDesktop sudo[1732696]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:15 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:15 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:14 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:14 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:14 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:14 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:14 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:14 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:14 ArchDesktop sudo[1732696]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:14 ArchDesktop sudo[1732696]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:14 ArchDesktop sudo[1732634]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:14 ArchDesktop kernel: PKRU: 55555554
Apr 29 00:58:14 ArchDesktop kernel: CR2: 00000e8c5a203d88 CR3: 000000045cd72000 CR4:<PHONE_NUMBER>f50ef0
Apr 29 00:58:14 ArchDesktop kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Apr 29 00:58:14 ArchDesktop kernel: FS:  000070311b6a6080(0000) GS:ffff899c7edc0000(0000) knlGS:0000000000000000
Apr 29 00:58:14 ArchDesktop kernel: R13: ffff899180245500 R14:<PHONE_NUMBER>000068 R15:<PHONE_NUMBER>cd282f
Apr 29 00:58:14 ArchDesktop kernel: R10:<PHONE_NUMBER>000001 R11: ffff899caf37bd80 R12:<PHONE_NUMBER>408d40
Apr 29 00:58:14 ArchDesktop kernel: RBP: ffff9db855d07a58 R08:<PHONE_NUMBER>000001 R09:<PHONE_NUMBER>000000
Apr 29 00:58:14 ArchDesktop kernel: RDX:<PHONE_NUMBER>1fb80f RSI:<PHONE_NUMBER>03b580 RDI: ffff89988cf8e3c0
Apr 29 00:58:14 ArchDesktop kernel: RAX:<PHONE_NUMBER>cd285f RBX: 5247cd920044d7d0 RCX:<PHONE_NUMBER>000001
Apr 29 00:58:14 ArchDesktop kernel: RSP: 0018:ffff9db855d07a20 EFLAGS: 00010206
Apr 29 00:58:14 ArchDesktop kernel: Code: 08 48 83 78 10 00 4c 8b 38 0f 84 ab 01 00 00 4d 85 ff 0f 84 a2 01 00 00 41 8b 45 28 49 8b 9d b8 00 00 00 49 8b 75 00 4c 01 f8 <48> 33 18 48 89 c1 4c 89 f8 48 0f c9 48 31 cb 48 8d 8a 00 02 00 00
Apr 29 00:58:14 ArchDesktop kernel: RIP: 0010:kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:14 ArchDesktop kernel: ---[ end trace<PHONE_NUMBER>000000 ]---
Apr 29 00:58:14 ArchDesktop kernel:  acpi_cpufreq k10temp i2c_piix4 mei snd_hwdep ptp xor pps_core raid6_pq dca mousedev joydev libcrc32c ryzen_smu(OE) mac_hid snd_aloop snd_pcm snd_timer snd soundcore i2c_dev sr_mod cdrom v4l2loopback(OE) videodev mc sg crypto_user dm_mod loop fuse nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic xe drm_gpuvm usbhid amdgpu i915 amdxcp drm_ttm_helper intel_gtt drm_exec video gpu_sched i2c_algo_bit ttm drm_suballoc_helper nvme drm_buddy crc32c_intel drm_display_helper nvme_core xhci_pci cec nvme_auth xhci_pci_renesas wmi
Apr 29 00:58:14 ArchDesktop kernel: Modules linked in: ip6table_filter ip6_tables xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter br_netfilter snd_seq_dummy snd_hrtimer snd_seq snd_seq_device macvtap macvlan vhost_net vhost vhost_iotlb tap tun overlay bridge stp llc nct6775 nct6775_core hwmon_vid jc42 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi mei_pxp mei_hdcp cdc_mbim cdc_wdm intel_rapl_msr intel_rapl_common kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel eeepc_wmi sha512_ssse3 asus_wmi sha256_ssse3 ledtrig_audio sha1_ssse3 nls_iso8859_1 platform_profile aesni_intel vfat cdc_ncm i8042 crypto_simd sparse_keymap cdc_ether fat asus_ec_sensors snd_hda_intel cryptd serio usbnet snd_intel_dspcfg mii btrfs rapl rfkill snd_intel_sdw_acpi mei_gsc snd_hda_codec mxm_wmi sp5100_tco igb mei_me pcspkr snd_hda_core ccp wmi_bmof blake2b_generic
Apr 29 00:58:14 ArchDesktop kernel:  </TASK>
Apr 29 00:58:14 ArchDesktop kernel: R13: 00007ffed58b5380 R14:<PHONE_NUMBER>000005 R15:<PHONE_NUMBER>000006
Apr 29 00:58:14 ArchDesktop kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000202 R12: 00000007f167e000
Apr 29 00:58:14 ArchDesktop kernel: RBP: 00007ffed58b5240 R08: 00000007f167e000 R09:<PHONE_NUMBER>000000
Apr 29 00:58:14 ArchDesktop kernel: RDX:<PHONE_NUMBER>000006 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>000005
Apr 29 00:58:14 ArchDesktop kernel: RAX: ffffffffffffffda RBX: 00000007f167e000 RCX: 000070311c054647
Apr 29 00:58:14 ArchDesktop kernel: RSP: 002b:00007ffed58b5198 EFLAGS: 00000202 ORIG_RAX:<PHONE_NUMBER>000113
Apr 29 00:58:14 ArchDesktop kernel: Code: ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 80 3d 05 6a 0d 00 00 49 89 ca 74 10 b8 13 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 71 c3 55 48 83 ec 30 44 89 4c 24 2c 4c 89 44
Apr 29 00:58:14 ArchDesktop kernel: RIP: 0033:0x70311c054647
Apr 29 00:58:14 ArchDesktop kernel:  entry_SYSCALL_64_after_hwframe+0x73/0x7b
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? syscall_exit_to_user_mode+0x80/0x230
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? switch_fpu_return+0x50/0xe0
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  do_syscall_64+0x89/0x170
Apr 29 00:58:14 ArchDesktop kernel:  __x64_sys_splice+0xb2/0x120
Apr 29 00:58:14 ArchDesktop kernel:  __do_splice+0x1f0/0x220
Apr 29 00:58:14 ArchDesktop kernel:  do_splice+0x312/0x8e0
Apr 29 00:58:14 ArchDesktop kernel:  iter_file_splice_write+0x33d/0x570
Apr 29 00:58:14 ArchDesktop kernel:  ext4_buffered_write_iter+0xa3/0x170 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  ? finish_wait+0x3c/0xa0
Apr 29 00:58:14 ArchDesktop kernel:  generic_perform_write+0xd9/0x240
Apr 29 00:58:14 ArchDesktop kernel:  ext4_da_write_begin+0x1a2/0x2f0 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? __pfx_ext4_da_get_block_prep+0x10/0x10 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ext4_block_write_begin+0x41c/0x520 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  create_empty_buffers+0x1d/0xb0
Apr 29 00:58:14 ArchDesktop kernel:  folio_alloc_buffers+0xee/0x230
Apr 29 00:58:14 ArchDesktop kernel:  ? folio_alloc_buffers+0xee/0x230
Apr 29 00:58:14 ArchDesktop kernel:  ? kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:14 ArchDesktop kernel:  ? asm_exc_general_protection+0x26/0x30
Apr 29 00:58:14 ArchDesktop kernel:  ? exc_general_protection+0x388/0x4a0
Apr 29 00:58:14 ArchDesktop kernel:  ? die_addr+0x128/0x130
Apr 29 00:58:14 ArchDesktop kernel:  <TASK>
Apr 29 00:58:14 ArchDesktop kernel: Call Trace:
Apr 29 00:58:14 ArchDesktop kernel: PKRU: 55555554
Apr 29 00:58:14 ArchDesktop kernel: CR2: 00000e8c5a203d88 CR3: 000000045cd72000 CR4:<PHONE_NUMBER>f50ef0
Apr 29 00:58:14 ArchDesktop kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Apr 29 00:58:14 ArchDesktop kernel: FS:  000070311b6a6080(0000) GS:ffff899c7edc0000(0000) knlGS:0000000000000000
Apr 29 00:58:14 ArchDesktop kernel: R13: ffff899180245500 R14:<PHONE_NUMBER>000068 R15:<PHONE_NUMBER>cd282f
Apr 29 00:58:14 ArchDesktop kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000019 R12:<PHONE_NUMBER>408d40
Apr 29 00:58:14 ArchDesktop kernel: RBP: ffff9db85597fa38 R08:<PHONE_NUMBER>000001 R09:<PHONE_NUMBER>000000
Apr 29 00:58:14 ArchDesktop kernel: RDX:<PHONE_NUMBER>1fb80f RSI:<PHONE_NUMBER>03b580 RDI: ffff8992490ac700
Apr 29 00:58:14 ArchDesktop kernel: RAX:<PHONE_NUMBER>cd285f RBX: 5247cd920044d7d0 RCX:<PHONE_NUMBER>000034
Apr 29 00:58:14 ArchDesktop kernel: RSP: 0018:ffff9db85597fa00 EFLAGS: 00010206
Apr 29 00:58:14 ArchDesktop kernel: Code: 08 48 83 78 10 00 4c 8b 38 0f 84 ab 01 00 00 4d 85 ff 0f 84 a2 01 00 00 41 8b 45 28 49 8b 9d b8 00 00 00 49 8b 75 00 4c 01 f8 <48> 33 18 48 89 c1 4c 89 f8 48 0f c9 48 31 cb 48 8d 8a 00 02 00 00
Apr 29 00:58:14 ArchDesktop kernel: RIP: 0010:kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:14 ArchDesktop kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 5003 10/07/2023
Apr 29 00:58:14 ArchDesktop kernel: CPU: 15 PID: 1729933 Comm: systemd-coredum Tainted: G      D    OE      6.8.4-zen1-1-zen #1 4a88f2661038c2a3bb69aa70fb41a5735338823c
Apr 29 00:58:14 ArchDesktop kernel: general protection fault, probably for non-canonical address 0x1293823692cd285f: 0000 [#2] PREEMPT SMP NOPTI
Apr 29 00:58:14 ArchDesktop kernel: PKRU: 55555554
Apr 29 00:58:14 ArchDesktop kernel: CR2: 00007fae5030cb80 CR3: 00000005ab238000 CR4:<PHONE_NUMBER>f50ef0
Apr 29 00:58:14 ArchDesktop kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Apr 29 00:58:14 ArchDesktop kernel: FS:  000074a9583b8080(0000) GS:ffff899c7edc0000(0000) knlGS:0000000000000000
Apr 29 00:58:14 ArchDesktop kernel: R13: ffff899180245500 R14:<PHONE_NUMBER>000068 R15:<PHONE_NUMBER>cd282f
Apr 29 00:58:14 ArchDesktop kernel: R10:<PHONE_NUMBER>000001 R11: ffff899caf37bd80 R12:<PHONE_NUMBER>408d40
Apr 29 00:58:14 ArchDesktop kernel: RBP: ffff9db855d07a58 R08:<PHONE_NUMBER>000001 R09:<PHONE_NUMBER>000000
Apr 29 00:58:14 ArchDesktop kernel: RDX:<PHONE_NUMBER>1fb80f RSI:<PHONE_NUMBER>03b580 RDI: ffff89988cf8e3c0
Apr 29 00:58:14 ArchDesktop kernel: RAX:<PHONE_NUMBER>cd285f RBX: 5247cd920044d7d0 RCX:<PHONE_NUMBER>000001
Apr 29 00:58:14 ArchDesktop kernel: RSP: 0018:ffff9db855d07a20 EFLAGS: 00010206
Apr 29 00:58:14 ArchDesktop kernel: Code: 08 48 83 78 10 00 4c 8b 38 0f 84 ab 01 00 00 4d 85 ff 0f 84 a2 01 00 00 41 8b 45 28 49 8b 9d b8 00 00 00 49 8b 75 00 4c 01 f8 <48> 33 18 48 89 c1 4c 89 f8 48 0f c9 48 31 cb 48 8d 8a 00 02 00 00
Apr 29 00:58:14 ArchDesktop kernel: RIP: 0010:kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:14 ArchDesktop kernel: ---[ end trace<PHONE_NUMBER>000000 ]---
Apr 29 00:58:14 ArchDesktop kernel:  acpi_cpufreq k10temp i2c_piix4 mei snd_hwdep ptp xor pps_core raid6_pq dca mousedev joydev libcrc32c ryzen_smu(OE) mac_hid snd_aloop snd_pcm snd_timer snd soundcore i2c_dev sr_mod cdrom v4l2loopback(OE) videodev mc sg crypto_user dm_mod loop fuse nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic xe drm_gpuvm usbhid amdgpu i915 amdxcp drm_ttm_helper intel_gtt drm_exec video gpu_sched i2c_algo_bit ttm drm_suballoc_helper nvme drm_buddy crc32c_intel drm_display_helper nvme_core xhci_pci cec nvme_auth xhci_pci_renesas wmi
Apr 29 00:58:14 ArchDesktop kernel: Modules linked in: ip6table_filter ip6_tables xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter br_netfilter snd_seq_dummy snd_hrtimer snd_seq snd_seq_device macvtap macvlan vhost_net vhost vhost_iotlb tap tun overlay bridge stp llc nct6775 nct6775_core hwmon_vid jc42 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi mei_pxp mei_hdcp cdc_mbim cdc_wdm intel_rapl_msr intel_rapl_common kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel eeepc_wmi sha512_ssse3 asus_wmi sha256_ssse3 ledtrig_audio sha1_ssse3 nls_iso8859_1 platform_profile aesni_intel vfat cdc_ncm i8042 crypto_simd sparse_keymap cdc_ether fat asus_ec_sensors snd_hda_intel cryptd serio usbnet snd_intel_dspcfg mii btrfs rapl rfkill snd_intel_sdw_acpi mei_gsc snd_hda_codec mxm_wmi sp5100_tco igb mei_me pcspkr snd_hda_core ccp wmi_bmof blake2b_generic
Apr 29 00:58:14 ArchDesktop kernel:  </TASK>
Apr 29 00:58:14 ArchDesktop kernel: R13: 00007fff0370fde0 R14:<PHONE_NUMBER>000005 R15:<PHONE_NUMBER>000006
Apr 29 00:58:14 ArchDesktop kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000202 R12: 000000064b326000
Apr 29 00:58:14 ArchDesktop kernel: RBP: 00007fff0370fca0 R08: 000000064b326000 R09:<PHONE_NUMBER>000000
Apr 29 00:58:14 ArchDesktop kernel: RDX:<PHONE_NUMBER>000006 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>000005
Apr 29 00:58:14 ArchDesktop kernel: RAX: ffffffffffffffda RBX: 000000064b326000 RCX: 000074a958db6647
Apr 29 00:58:14 ArchDesktop kernel: RSP: 002b:00007fff0370fbf8 EFLAGS: 00000202 ORIG_RAX:<PHONE_NUMBER>000113
Apr 29 00:58:14 ArchDesktop kernel: Code: ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 80 3d 05 6a 0d 00 00 49 89 ca 74 10 b8 13 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 71 c3 55 48 83 ec 30 44 89 4c 24 2c 4c 89 44
Apr 29 00:58:14 ArchDesktop kernel: RIP: 0033:0x74a958db6647
Apr 29 00:58:14 ArchDesktop kernel:  entry_SYSCALL_64_after_hwframe+0x73/0x7b
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? syscall_exit_to_user_mode+0x80/0x230
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? do_syscall_64+0x96/0x170
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  do_syscall_64+0x89/0x170
Apr 29 00:58:14 ArchDesktop kernel:  __x64_sys_splice+0xb2/0x120
Apr 29 00:58:14 ArchDesktop kernel:  __do_splice+0x1f0/0x220
Apr 29 00:58:14 ArchDesktop kernel:  do_splice+0x312/0x8e0
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  iter_file_splice_write+0x33d/0x570
Apr 29 00:58:14 ArchDesktop kernel:  ext4_buffered_write_iter+0xa3/0x170 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  generic_perform_write+0xd9/0x240
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? ext4_da_write_end+0xad/0x370 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  ext4_da_write_begin+0x1a2/0x2f0 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  ? __block_commit_write+0x78/0xb0
Apr 29 00:58:14 ArchDesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 29 00:58:14 ArchDesktop kernel:  ? __pfx_ext4_da_get_block_prep+0x10/0x10 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  ext4_block_write_begin+0x41c/0x520 [ext4 4c370ef18dc92096340e0c399349e782617d846c]
Apr 29 00:58:14 ArchDesktop kernel:  create_empty_buffers+0x1d/0xb0
Apr 29 00:58:14 ArchDesktop kernel:  folio_alloc_buffers+0xee/0x230
Apr 29 00:58:14 ArchDesktop kernel:  ? folio_alloc_buffers+0xee/0x230
Apr 29 00:58:14 ArchDesktop kernel:  ? kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:14 ArchDesktop kernel:  ? asm_exc_general_protection+0x26/0x30
Apr 29 00:58:14 ArchDesktop kernel:  ? exc_general_protection+0x388/0x4a0
Apr 29 00:58:14 ArchDesktop kernel:  ? die_addr+0x128/0x130
Apr 29 00:58:14 ArchDesktop kernel:  <TASK>
Apr 29 00:58:14 ArchDesktop kernel: Call Trace:
Apr 29 00:58:14 ArchDesktop kernel: PKRU: 55555554
Apr 29 00:58:14 ArchDesktop kernel: CR2: 00007fae5030cb80 CR3: 00000005ab238000 CR4:<PHONE_NUMBER>f50ef0
Apr 29 00:58:14 ArchDesktop kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Apr 29 00:58:14 ArchDesktop kernel: FS:  000074a9583b8080(0000) GS:ffff899c7edc0000(0000) knlGS:0000000000000000
Apr 29 00:58:14 ArchDesktop kernel: R13: ffff899180245500 R14:<PHONE_NUMBER>000068 R15:<PHONE_NUMBER>cd282f
Apr 29 00:58:14 ArchDesktop kernel: R10:<PHONE_NUMBER>000001 R11: ffff899caf37bd80 R12:<PHONE_NUMBER>408d40
Apr 29 00:58:14 ArchDesktop kernel: RBP: ffff9db855d07a58 R08:<PHONE_NUMBER>000001 R09:<PHONE_NUMBER>000000
Apr 29 00:58:14 ArchDesktop kernel: RDX:<PHONE_NUMBER>1fb80f RSI:<PHONE_NUMBER>03b580 RDI: ffff89988cf8e3c0
Apr 29 00:58:14 ArchDesktop kernel: RAX:<PHONE_NUMBER>cd285f RBX: 5247cd920044d7d0 RCX:<PHONE_NUMBER>000001
Apr 29 00:58:14 ArchDesktop kernel: RSP: 0018:ffff9db855d07a20 EFLAGS: 00010206
Apr 29 00:58:14 ArchDesktop kernel: Code: 08 48 83 78 10 00 4c 8b 38 0f 84 ab 01 00 00 4d 85 ff 0f 84 a2 01 00 00 41 8b 45 28 49 8b 9d b8 00 00 00 49 8b 75 00 4c 01 f8 <48> 33 18 48 89 c1 4c 89 f8 48 0f c9 48 31 cb 48 8d 8a 00 02 00 00
Apr 29 00:58:14 ArchDesktop kernel: RIP: 0010:kmem_cache_alloc+0xc2/0x450
Apr 29 00:58:14 ArchDesktop kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 5003 10/07/2023
Apr 29 00:58:14 ArchDesktop kernel: CPU: 15 PID: 1729951 Comm: systemd-coredum Tainted: G           OE      6.8.4-zen1-1-zen #1 4a88f2661038c2a3bb69aa70fb41a5735338823c
Apr 29 00:58:14 ArchDesktop kernel: general protection fault, probably for non-canonical address 0x1293823692cd285f: 0000 [#1] PREEMPT SMP NOPTI
Apr 29 00:58:13 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:13 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:13 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:13 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:13 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:13 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:13 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:13 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:13 ArchDesktop sudo[1732634]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:13 ArchDesktop sudo[1732634]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:13 ArchDesktop sudo[1732574]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:12 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:12 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:11 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:11 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:11 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:11 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:11 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:11 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:11 ArchDesktop sudo[1732574]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:11 ArchDesktop sudo[1732574]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:11 ArchDesktop sudo[1732373]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:10 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:10 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:10 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:10 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:10 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:10 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:10 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:10 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:10 ArchDesktop sudo[1732373]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:10 ArchDesktop sudo[1732373]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:10 ArchDesktop sudo[1732241]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:09 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:09 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:08 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:08 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:08 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:08 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:08 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:08 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:08 ArchDesktop sudo[1732241]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:08 ArchDesktop sudo[1732241]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:08 ArchDesktop sudo[1732176]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:07 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:07 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:07 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:07 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:07 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:07 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:07 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:07 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:07 ArchDesktop sudo[1732176]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:07 ArchDesktop sudo[1732176]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:07 ArchDesktop sudo[1732037]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:06 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:06 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:05 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:05 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:05 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:05 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:05 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:05 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop sudo[1732037]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:05 ArchDesktop sudo[1732037]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop sudo[1731333]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:05 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.
Apr 29 00:58:05 ArchDesktop gvfsd-wsdd[1731771]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:04 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:04 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:04 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:04 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop sudo[1731333]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:04 ArchDesktop sudo[1731333]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:04 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:04 ArchDesktop sudo[1730715]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.
Apr 29 00:58:03 ArchDesktop gvfsd-wsdd[1731296]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:03 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:03 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.
Apr 29 00:58:02 ArchDesktop gvfsd-wsdd[1730857]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:02 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:02 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Apr 29 00:58:02 ArchDesktop kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop sudo[1730715]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:02 ArchDesktop sudo[1730715]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop sudo[1730017]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:02 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.
Apr 29 00:58:02 ArchDesktop gvfsd-wsdd[1730551]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: GPU reset(52) succeeded!
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: recover vram bo from shadow done
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: recover vram bo from shadow start
Apr 29 00:58:01 ArchDesktop kernel: [drm] kiq ring mec 3 pipe 1 q 0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x1
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x1
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x5
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x1
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x1
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CPC (0x5)
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B53
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
Apr 29 00:58:01 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: IP block:gfx_v11_0 is hung!
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:01 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-wsdd[1730225]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop sudo[1730017]: pam_unix(sudo:session): session opened for user root(uid=0) by disty(uid=1000)
Apr 29 00:58:00 ArchDesktop sudo[1730017]:    disty : TTY=pts/8 ; PWD=/home/disty ; USER=root ; COMMAND=/usr/bin/xpu-smi stats -d 0
Apr 29 00:58:00 ArchDesktop sudo[1729509]: pam_unix(sudo:session): session closed for user root
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop systemd[1]: Started Process Core Dump (PID 1729924/UID 0).
Apr 29 00:58:00 ArchDesktop systemd[1]: Started Process Core Dump (PID 1729925/UID 0).
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop gvfsd-network[1708472]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running
Apr 29 00:58:00 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: GPU reset begin!
Apr 29 00:58:00 ArchDesktop kernel: amdgpu: Failed to evict process queues
Apr 29 00:58:00 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: Failed to evict queue 1
Apr 29 00:58:00 ArchDesktop kernel: amdgpu 0000:0f:00.0: amdgpu: MES might be in unrecoverable state, issue a GPU reset