Since this update, I sometimes have random (PC) freezes. I then have to restart the PC using the power button. Before this update it was rock solid stable 
Do you have any tips on how I can find out what is causing these freezes since the last update?
I did not change any Settings after the update and i do not overlocking my Hardware.
Welcome to the forum! 
Please take the time to read through the following links… 
How to Request Support
ttyTips and Tricks
Resources
And, every time you force a hard shutdown you risk damage to your system, which not only makes it less stable but also compounds the problem.
There’s an alternative to a hard reset or shutdown:
Regards.
Thanks, I have added the REISUB method and will test it with the next freeze 
Unfortunately the method itself doesn’t fix the freezes, any ideas on how we can figure out why it’s been so unstable since the last update?
None whatsoever.
However, once you provide information that might be useful for those wishing to help, that might generate a few clues.
See the previous post from @Aragorn .
Regards.
Output of journalctl --boot=-1 --unit=<service_name> --no-pager:
Jun 28 11:26:03 fye-linux pipewire[2492]: spa.alsa: 'front:3': playback open failed: Das Gerät oder die Ressource ist belegt
Jun 28 11:26:03 fye-linux pipewire[2492]: spa.alsa: 'front:3': capture open failed: Das Gerät oder die Ressource ist belegt
Jun 28 11:26:04 fye-linux org_kde_powerdevil[2723]: [ 2857] busno=8, All features that should not exist detected. Monitor does not indicate unsupported
Jun 28 11:26:04 fye-linux org_kde_powerdevil[2723]: [ 2856] busno=7, All features that should not exist detected. Monitor does not indicate unsupported
Jun 28 11:26:04 fye-linux pulseaudio[2562]: Failed to open connection to session manager: None of the authentication protocols specified are supported
Jun 28 11:26:04 fye-linux pulseaudio[2562]: Failed to load module "module-x11-xsmp" (argument: "display=:1 xauthority=/run/user/1000/xauth_kpGxuF session_manager=local/fye-linux:@/tmp/.ICE-unix/2597,unix/fye-linux:/tmp/.ICE-unix/2597"): initialization failed.
Jun 28 11:31:38 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:31:43 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:31:43 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to enable GFXCLK DS!
Jun 28 11:31:47 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:31:47 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to set workload mask 0x00000001
Jun 28 11:31:47 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:31:53 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:31:53 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 28 11:31:57 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:31:57 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 28 11:32:01 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:32:01 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 28 11:32:06 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:32:06 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 28 11:32:06 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=37933, emitted seq=37935
Jun 28 11:32:06 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Process information: process Xwayland pid 2511 thread Xwayland:cs0 pid 2514
Jun 28 11:32:06 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Jun 28 11:32:08 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: MES(1) failed to respond to msg=RESET
Jun 28 11:32:08 fye-linux kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Jun 28 11:32:08 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: reset via MES failed -110
Jun 28 11:32:08 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Ring gfx_0.0.0 reset failure
Jun 28 11:32:17 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:32:17 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 28 11:32:21 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:32:21 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to enable GFXCLK DS!
Jun 28 11:32:25 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:32:25 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to set workload mask 0x00000001
Jun 28 11:32:29 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 28 11:32:29 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: [SetDfCstate] failed!
Jun 28 11:32:30 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:30 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:34 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:34 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:34 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:35 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:41 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:41 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:48 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:48 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:32:48 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 28 11:34:03 fye-linux kernel: INFO: task kworker/u102:1:404 blocked for more than 122 seconds.
Jun 28 11:34:03 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:34:03 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:34:03 fye-linux kernel: INFO: task kworker/u103:4:3760 blocked for more than 122 seconds.
Jun 28 11:34:03 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:34:03 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/u96:0:12 blocked for more than 122 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:1H:327 blocked for more than 122 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:1H:327 is blocked on a mutex likely owned by task kworker/u96:0:12.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/u102:1:404 blocked for more than 245 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/u103:4:3760 blocked for more than 245 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:0H:4510 blocked for more than 122 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:0H:4510 is blocked on a mutex likely owned by task kworker/1:1H:327.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:3H:4513 blocked for more than 122 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:3H:4513 is blocked on a mutex likely owned by task kworker/1:1H:327.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:4H:4515 blocked for more than 122 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:4H:4515 is blocked on a mutex likely owned by task kworker/1:1H:327.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:5H:4516 blocked for more than 122 seconds.
Jun 28 11:36:06 fye-linux kernel: Tainted: G S OE 6.15.3-1-MANJARO #1
Jun 28 11:36:06 fye-linux kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 28 11:36:06 fye-linux kernel: INFO: task kworker/1:5H:4516 is blocked on a mutex likely owned by task kworker/1:1H:327.
I think after this, the pc crashes (i was not at the pc at this time).
OK, let’s do this the longer way. Logs can be useful tools, but without knowing anything about your system, there is little context with it.
Please provide system information as described (below) - the command for that was also in one of the linked pages given by @Aragorn - in fact, the very first command example;
Without sufficient information, guesses are often difficult to formulate, and blaming sudden freezes (crashes) on cosmic rays becomes within the realm of possibility.
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; 
Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Sorry for the inconvenience, I’ve been using Linux and Manjaro for quite a while and have been able to solve superficial problems myself by googling, but with this problem here I didn’t get any further with googling and the troubleshooting process in the Manjaro forum is therefore still a bit new to me.
Output of inxi -zv8:
System:
Kernel: 6.15.3-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.15-x86_64
root=UUID=7855555d-0a93-4424-b16e-369377dc824d rw quiet apparmor=1
security=apparmor resume=UUID=9741a237-6f5f-4b60-aca6-67430dbb7d5f
udev.log_priority=3
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.15.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: X570 Taichi serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends v: P4.60
date: 08/03/2021
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 32 GiB available: 31.26 GiB used: 15.2 GiB (48.6%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
max-module-size: 32 GiB note: est.
Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 3600 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3600C16-8GVK serial: N/A
Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 3600 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3600C16-8GVK serial: N/A
Device-3: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 3600 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3600C16-8GVK serial: N/A
Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 3600 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3600C16-8GVK serial: N/A
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 gen: 2
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2
smt: enabled cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB
desc: 12x512 KiB L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 4198 min/max: 563/4674 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 4198 2: 4198 3: 4198
4: 4198 5: 4198 6: 4198 7: 4198 8: 4198 9: 4198 10: 4198 11: 4198 12: 4198
13: 4198 14: 4198 15: 4198 16: 4198 17: 4198 18: 4198 19: 4198 20: 4198
21: 4198 22: 4198 23: 4198 24: 4198 bogomips: 182390
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs
irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
rdtscp rep_good sep sev sev_es sha_ni skinit smap smca smep ssbd sse sse2
sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme
vmmcall wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xtopology
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: ghostwrite status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
protection
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [RX 9070/9070 XT]
vendor: ASUSTeK driver: amdgpu v: kernel pcie: gen: 5 speed: 32 GT/s
lanes: 16 ports: active: DP-1,DP-2,HDMI-A-1 empty: DP-3,Writeback-1
bus-ID: 10:00.0 chip-ID: 1002:7550 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu d-rect: 9600x3240
display-ID: 0
Monitor-1: DP-1 pos: top-center model: LG (GoldStar) Ultra HD
serial: <filter> built: 2017 res: mode: 3840x2160 hz: 60 scale: 125% (1.25)
to: 3072x1728 dpi: 163 gamma: 1.2 chroma: red: x: 0.655 y: 0.333 green:
x: 0.306 y: 0.639 blue: x: 0.149 y: 0.059 white: x: 0.314 y: 0.329
size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9
modes: 3840x2160, 2560x1440, 1920x1200, 1920x1080, 1600x1200, 1680x1050,
1600x900, 1280x1024, 1440x900, 1280x800, 1152x864, 1280x720, 1024x768,
800x600, 720x480, 640x480
Monitor-2: DP-2 pos: top-right model: LG (GoldStar) Ultra HD
serial: <filter> built: 2019 res: mode: 3840x2160 hz: 60 scale: 125% (1.25)
to: 3072x1728 dpi: 163 gamma: 1.2 chroma: red: x: 0.655 y: 0.333 green:
x: 0.306 y: 0.639 blue: x: 0.149 y: 0.059 white: x: 0.314 y: 0.329
size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9
modes: 3840x2160, 2560x1440, 1920x1200, 1920x1080, 1600x1200, 1680x1050,
1600x900, 1280x1024, 1440x900, 1280x800, 1152x864, 1280x720, 1024x768,
800x600, 720x480, 640x480
Monitor-3: HDMI-A-1 pos: bottom-l model: Idek Iiyama PLX2783H
serial: <filter> built: 2013 res: mode: 1920x1080 hz: 60 scale: 100% (1)
dpi: 82 gamma: 1.2 chroma: red: x: 0.647 y: 0.329 green: x: 0.314 y: 0.620
blue: x: 0.153 y: 0.063 white: x: 0.314 y: 0.329
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9
modes: 1920x1080, 1600x1200, 1680x1050, 1280x1024, 1440x900, 1280x960,
1280x800, 1280x720, 1152x720, 1024x768, 800x600, 720x576, 720x480,
640x480
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 9070 XT (radeonsi
gfx1201 LLVM 20.1.6 DRM 3.63 6.15.3-1-MANJARO) device-ID: 1002:7550
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.313 layers: 15 device: 0 type: discrete-gpu name: AMD
Radeon RX 9070 XT (RADV GFX1201) driver: mesa radv v: 25.1.4-arch1.1
device-ID: 1002:7550 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: lact wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Creative Labs EMU20k2 [Sound Blaster X-Fi Titanium Series]
driver: snd_ctxfi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 09:00.0 chip-ID: 1102:000b class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel v: kernel
pcie: gen: 5 speed: 32 GT/s lanes: 16 bus-ID: 10:00.1 chip-ID: 1002:ab40
class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 12:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-4: ABC MIC_TEST driver: hid-generic,snd-usb-audio,usbhid type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4:3 chip-ID: 3142:0001
class-ID: 0300
API: ALSA v: k6.15.3-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.4.5 status: active with: 1: pipewire-media-session
status: active 2: pipewire-alsa type: plugin tools: pw-cat,pw-cli
Server-4: PulseAudio v: 17.0-43-g3e2bb status: active with:
1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
tools: pacat,pactl,pamixer,pavucontrol
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: N/A modules: iwlwifi pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
IF-ID-1: virbr0 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
Info: services: NetworkManager,systemd-timesyncd
WAN IP: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-2:2 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 11.37 TiB used: 3.84 TiB (33.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT2000P5PSSD8
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P7CR403 temp: 67.8 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD30EFRX-68AX9N0 size: 2.73 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD30EURS-63SPKY0 size: 2.73 TiB block-size: physical: 4096 B
logical: 512 B speed: 3.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT500MX500SSD1
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 023 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 020 scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Crucial model: CT2000MX500SSD1
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 033 scheme: GPT
ID-7: /dev/sdf maj-min: 8:80 vendor: Samsung model: ST1000LM024 HN-M101MBB
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: HDD rpm: 5400
serial: <filter> scheme: GPT
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 247.72 GiB size: 243.53 GiB (98.31%)
used: 149.96 GiB (61.6%) fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:1
label: Manjaro OS uuid: 7855555d-0a93-4424-b16e-369377dc824d
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 292 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p3 maj-min: 259:3
label: NO_LABEL uuid: 4148-1A1C
ID-3: /home raw-size: 1.56 TiB size: 1.53 TiB (98.36%)
used: 991.32 GiB (63.1%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
label: Home uuid: 79dfb248-3e66-47a6-b718-732bd89492d7
ID-4: /run/media/fye/Backup raw-size: 2.73 TiB size: 2.69 TiB (98.39%)
used: 5.14 GiB (0.2%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: Backup
uuid: 74172308-6968-487b-b454-2e62d451af7e
ID-5: /run/media/fye/Daten_Backup raw-size: 2.73 TiB
size: 2.69 TiB (98.39%) used: 1.16 TiB (43.2%) fs: ext4 dev: /dev/sdb1
maj-min: 8:17 label: Daten_Backup
uuid: 29a19eac-3e7e-4042-866c-bf8b21b01242
ID-6: /run/media/fye/Development-SSD raw-size: 931.51 GiB
size: 915.82 GiB (98.31%) used: 591.85 GiB (64.6%) fs: ext4 dev: /dev/sdd1
maj-min: 8:49 label: Development-SSD
uuid: 11a4923a-9057-49cc-a75f-e1d2b3ea6bd9
ID-7: /run/media/fye/Spiele_2TB raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
used: 1009.15 GiB (55.1%) fs: ext4 dev: /dev/sde1 maj-min: 8:65
label: Spiele_2TB uuid: 8ff8a1cd-a686-4c3e-ac2f-c9200a97d0ec
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 17.5 GiB used: 597.1 MiB (3.3%)
priority: -2 dev: /dev/nvme0n1p4 maj-min: 259:4 label: Swap
uuid: 9741a237-6f5f-4b60-aca6-67430dbb7d5f
Unmounted:
ID-1: /dev/sdc1 maj-min: 8:33 size: 465.14 GiB fs: ntfs label: N/A
uuid: 68B03161B0313742
ID-2: /dev/sdc2 maj-min: 8:34 size: 100 MiB fs: vfat label: N/A
uuid: 2C65-47BA
ID-3: /dev/sdc3 maj-min: 8:35 size: 531 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-4: /dev/sdf1 maj-min: 8:81 size: 931.51 GiB fs: btrfs
label: Btrfs_1TB_HDD uuid: bcba95e2-e197-466d-bce0-0f0ef78e6e63
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-2: 1-2:2 info: Genesys Logic Hub ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 2-2:2 info: ASMedia Ugreen Storage Device type: mass storage
driver: uas interfaces: 1 rev: 3.1 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
mode: 3.2 gen-1x1 chip-ID: 174c:235c class-ID: 0806 serial: <filter>
Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 3-2:2 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
power: 100mA chip-ID: 8087:0029 class-ID: e001
Device-2: 3-4:3 info: ABC MIC_TEST type: audio,HID
driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 3142:0001 class-ID: 0300
Hub-5: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-6: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-7: 5-1:2 info: Genesys Logic Hub ports: 2 rev: 2.1
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 05e3:0610
class-ID: 0900
Device-1: 5-1.1:5 info: Razer USA DeathAdder V2 Pro type: mouse,keyboard
driver: razermouse,usbhid interfaces: 5 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 100mA chip-ID: 1532:007d class-ID: 0300
serial: <filter>
Device-2: 5-1.2:4 info: Razer USA RC30-030502 Mouse Dock
type: mouse,keyboard driver: razeraccessory,usbhid interfaces: 3 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 500mA
chip-ID: 1532:007e class-ID: 0300
Device-3: 5-4:3 info: Razer USA BlackWidow Classic type: keyboard,mouse
driver: razerkbd,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 100mA chip-ID: 1532:011b class-ID: 0300
Hub-8: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 42.5 C mobo: 41.0 C gpu: amdgpu temp: 55.0 C
mem: 72.0 C
Fan Speeds (rpm): fan-1: 1028 fan-2: 2036 fan-3: 4078 fan-4: 953 fan-5: 0
fan-6: 0 fan-7: 0 gpu: amdgpu fan: 46
Repos:
Packages: 2395 pm: pacman pkgs: 2303 libs: 534 tools: pamac pm: flatpak
pkgs: 82 pm: snap pkgs: 10
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://mirrors.manjaro.org/repo/stable/$repo/$arch
2: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
3: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
4: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
5: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
6: https://muug.ca/mirror/manjaro/stable/$repo/$arch
7: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
8: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 575
1: cpu: 202% command: VirtualBoxVM pid: 4333 mem: 4718.7 MiB (14.7%)
2: cpu: 84.0% command: baloo_file_extractor pid: 4416
mem: 188.4 MiB (0.5%)
3: cpu: 42.1% command: floorp pid: 4448 mem: 653.0 MiB (2.0%)
4: cpu: 25.2% command: baloo_file pid: 2448 mem: 74.1 MiB (0.2%)
5: cpu: 12.0% command: floorp pid: 4749 mem: 229.1 MiB (0.7%)
Memory top: 5 of 575
1: mem: 4718.7 MiB (14.7%) command: VirtualBoxVM pid: 4333 cpu: 202%
2: mem: 675.2 MiB (2.1%) command: plasmashell pid: 2744 cpu: 2.9%
3: mem: 653.0 MiB (2.0%) command: floorp pid: 4448 cpu: 42.1%
4: mem: 435.8 MiB (1.3%) command: exe pid: 3845 cpu: 2.6%
5: mem: 415.5 MiB (1.2%) command: floorp pid: 5143 cpu: 8.7%
Info:
Processes: 575 Power: uptime: 3m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,upowerd
Init: systemd v: 257 default: graphical tool: systemctl
Compilers: clang: 20.1.6 gcc: 15.1.1 alt: 11/13/14 Shell: Zsh v: 5.9
default: Bash v: 5.2.37 running-in: konsole inxi: 3.3.38
Had a crash a few Minuts ago, output of journalctl --boot=-1 --priority=3 --catalog --no-pager
Jun 29 11:25:42 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:25:42 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to enable GFXCLK DS!
Jun 29 11:25:47 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:25:47 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to set workload mask 0x00000001
Jun 29 11:25:47 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:25:52 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:25:52 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 29 11:25:56 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:25:56 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 29 11:26:01 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:26:01 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 29 11:26:05 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:26:05 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 29 11:26:05 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=4554323, emitted seq=4554325
Jun 29 11:26:05 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Process information: process Xwayland pid 2506 thread Xwayland:cs0 pid 2510
Jun 29 11:26:05 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Jun 29 11:26:08 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: MES(1) failed to respond to msg=RESET
Jun 29 11:26:08 fye-linux kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Jun 29 11:26:08 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: reset via MES failed -110
Jun 29 11:26:08 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Ring gfx_0.0.0 reset failure
Jun 29 11:26:09 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:09 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:09 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:10 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:10 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:10 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:10 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:11 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:11 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:11 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:11 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:12 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:12 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:12 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:12 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:13 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:16 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:26:16 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to disable gfxoff!
Jun 29 11:26:18 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:18 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:18 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:19 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:19 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:19 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:19 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:19 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:20 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:20 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:20 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:20 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:21 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:26:21 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to enable GFXCLK DS!
Jun 29 11:26:21 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:21 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:21 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:21 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:25 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:26:25 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: Failed to set workload mask 0x00000001
Jun 29 11:26:29 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000008 SMN_C2PMSG_82:0x00000400
Jun 29 11:26:29 fye-linux kernel: amdgpu 0000:10:00.0: amdgpu: [SetDfCstate] failed!
Jun 29 11:26:29 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:26:30 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux kernel: amdgpu 0000:10:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 29 11:27:06 fye-linux systemd[1]: Failed to start CUPS Scheduler.
Jun 29 11:27:06 fye-linux systemd[1]: Failed to start Rule-based Manager for Device Events and Files.
Jun 29 11:27:06 fye-linux systemd[1]: Failed to start Journal Service.
Jun 29 11:26:32 fye-linux pulseaudio[2557]: Failed to release transport /org/bluez/hci0/dev_AC_12_2F_CC_FA_70/fd0: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 29 11:26:32 fye-linux systemd-coredump[17616]: [🡕] Process 1714 (bluetoothd) of user 0 dumped core.
Stack trace of thread 1714:
#0 0x00007f044441574c n/a (libc.so.6 + 0x9774c)
#1 0x00007f04443bbdc0 raise (libc.so.6 + 0x3ddc0)
#2 0x00007f04443a357a abort (libc.so.6 + 0x2557a)
#3 0x00007f04446aa064 n/a (libdbus-1.so.3 + 0xe064)
#4 0x00007f04446d3e50 _dbus_warn_check_failed (libdbus-1.so.3 + 0x37e50)
#5 0x00007f04446c1a42 dbus_message_new_method_call (libdbus-1.so.3 + 0x25a42)
#6 0x000055cf32996723 n/a (/usr/lib/bluetooth/bluetoothd + 0xf723)
#7 0x000055cf3299cccc n/a (/usr/lib/bluetooth/bluetoothd + 0x15ccc)
#8 0x000055cf32a4c496 n/a (/usr/lib/bluetooth/bluetoothd + 0xc5496)
#9 0x000055cf32a4cba0 n/a (/usr/lib/bluetooth/bluetoothd + 0xc5ba0)
#10 0x000055cf32a1710f n/a (/usr/lib/bluetooth/bluetoothd + 0x9010f)
#11 0x00007f0444770be0 g_slist_foreach (libglib-2.0.so.0 + 0x81be0)
#12 0x000055cf329aaa7e n/a (/usr/lib/bluetooth/bluetoothd + 0x23a7e)
#13 0x000055cf32991353 n/a (/usr/lib/bluetooth/bluetoothd + 0xa353)
#14 0x00007f04443a56b5 n/a (libc.so.6 + 0x276b5)
#15 0x00007f04443a5769 __libc_start_main (libc.so.6 + 0x27769)
#16 0x000055cf32992565 n/a (/usr/lib/bluetooth/bluetoothd + 0xb565)
ELF object binary architecture: AMD x86-64
░░ Subject: Memory image generated for process 1714 (bluetoothd)
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░ Process 1714 (bluetoothd) has been aborted and
░░ a memory image has been generated.
░░
░░ This is usually an indication of a program error and should
░░ be reported as an error to the respective manufacturer.
Jun 29 11:26:34 fye-linux systemd-coredump[17617]: [🡕] Process 3249 (ferdium) of user 1000 dumped core.
Stack trace of thread 22:
#0 0x000055d78e4b0aae n/a (/app/Ferdium/ferdium + 0x6c95aae)
#1 0x000055d78e4b058b n/a (/app/Ferdium/ferdium + 0x6c9558b)
#2 0x000055d78e4b0b19 n/a (/app/Ferdium/ferdium + 0x6c95b19)
#3 0x000055d78f28f030 n/a (/app/Ferdium/ferdium + 0x7a74030)
#4 0x00007f17d8a91b51 n/a (/usr/lib/x86_64-linux-gnu/libdbus-1.so.3.32.4 + 0x1bb51)
#5 0x000055d78f28fdda n/a (/app/Ferdium/ferdium + 0x7a74dda)
#6 0x000055d78e4ffcff n/a (/app/Ferdium/ferdium + 0x6ce4cff)
#7 0x000055d78e52e17e n/a (/app/Ferdium/ferdium + 0x6d1317e)
#8 0x000055d78e52d825 n/a (/app/Ferdium/ferdium + 0x6d12825)
#9 0x000055d78e52d420 n/a (/app/Ferdium/ferdium + 0x6d12420)
#10 0x000055d78e541ef5 n/a (/app/Ferdium/ferdium + 0x6d26ef5)
#11 0x000055d78e541ccd n/a (/app/Ferdium/ferdium + 0x6d26ccd)
#12 0x000055d78e541bc7 n/a (/app/Ferdium/ferdium + 0x6d26bc7)
#13 0x000055d78e55e4cc n/a (/app/Ferdium/ferdium + 0x6d434cc)
#14 0x00007f17d79c3eda n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8eeda)
#15 0x00007f17d7a4bac4 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x116ac4)
ELF object binary architecture: AMD x86-64
░░ Subject: Memory image generated for process 3249 (ferdium)
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░ Process 3249 (ferdium) has been aborted and
░░ a memory image has been generated.
░░
░░ This is usually an indication of a program error and should
░░ be reported as an error to the respective manufacturer.
Jun 29 11:26:38 fye-linux pulseaudio[2557]: org.bluez.BatteryProviderManager1.UnregisterBatteryProvider() Failed: org.freedesktop.DBus.Error.Disconnected:Connection is closed
Jun 29 11:26:39 fye-linux systemd-coredump[17650]: [🡕] Process 9706 (steamwebhelper) of user 1000 dumped core.
Module /run/host/usr/lib/libicudata.so.76.1 without build-id.
Module /run/host/usr/lib/libicudata.so.76.1
Module /run/host/usr/lib/libicuuc.so.76.1 without build-id.
Module /run/host/usr/lib/libicuuc.so.76.1
Stack trace of thread 9722:
#0 0x00007f75c7ccb0af n/a (/home/fye/.local/share/Steam/ubuntu12_64/libcef.so + 0x66cb0af)
#1 0x00007f75c7ccab7b n/a (/home/fye/.local/share/Steam/ubuntu12_64/libcef.so + 0x66cab7b)
#2 0x00007f75c7ccb129 n/a (/home/fye/.local/share/Steam/ubuntu12_64/libcef.so + 0x66cb129)
#3 0x00007f75c8c748e0 n/a (/home/fye/.local/share/Steam/ubuntu12_64/libcef.so + 0x76748e0)
#4 0x00007f75c042aa41 n/a (/usr/lib/x86_64-linux-gnu/libdbus-1.so.3.19.17 + 0x17a41)
ELF object binary architecture: AMD x86-64
░░ Subject: Memory image generated for process 9706 (steamwebhelper)
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░ Process 9706 (steamwebhelper) has been terminated and
░░ a memory image has been generated.
░░
░░ This is usually an indication of a program error and should
░░ be reported as an error to the respective manufacturer.
What I could observe during the latest crash was that the mouse started to hang or stutter and the 3 screens then went off. It is noticeable that they keep trying to wake up from “standby mode” (no idea what else to call it), but fail and the keyboard also hangs.
REISUB was able to restart the PC in this case, but unfortunately REISUB did not work during the crash yesterday.
As I said, the problems have only existed since the last Manjaro stable update, before that everything was absolutely stable and problem-free.
If further information is required, I will be happy to provide it.
Well it seems it’s your graphics card crashing, you could try installing another kernel to get a different driver version. Or simply boot into the old kernel from before the update.
Thanks for that.
I see nothing obvious from your system information; plenty of swap; plenty of free space; temperatures seem fine.
On the chance that there is an issue with kernel 6.15 on your system, I suggest reverting to 6.12 (LTS). Generally, unless there is a specific need for the latest-and-greatest kernel, it’s usually best to remain with the current LTS.
Note that kernel 6.14 has already reached EOL and it’s likely 6.15 will follow suit in the near future. Kernel 6.12 (LTS) by comparison is expected to be in service till the end of 2026.
If the crashes magically disappear after reverting to 6.12, I dare say the issue will be resolved. If not, then please report back so that others can dive a little deeper.
In other news, I note your system BIOS is a few years old. It might be a good idea to check the ASRock site and see if they have a non-beta BIOS to update. Updating it may (or may not) help with the issue at hand, but it can’t hurt.
Regards.
It’s an Asus 9070XT, Manjaro removed the 6.14.6 kernel I was using before without any problems, so I can’t go back to that kernel version. LTS kernel 6.12 seems to be a bit too old (because of the AMD drivers in the kernel) and 6.16 is just a RC version
@soundofthunder Kernel 6.12 and 6.13 didn’t run quite smoothly for me, only kernel 6.14 ran pretty clean for me. If necessary I will try kernel 6.12 again, but there were some problems (e.g. freezes) in connection with the new AMD RX9070XT, which only disappeared with 6.14.4. I guess that kernel 6.12 still carries quite old AMD drivers, which is a disadvantage. I also did a lot of googling at the time and saw on Reddit and the like that many other people also had problems with 6.12 and 6.13 in conjunction with the newer AMD cards, so I was probably not an isolated case.
Asrock offers newer bios versions for the mainboard, but I deliberately don’t update because some things can lead to performance losses on AMD CPUs. The bios didn’t seem to be the problem so far, as it ran without any problems until the last update.
As already mentioned, I will probably test the kernel 6.12, but I won’t be able to give feedback on this for a few days, as the crashes occur randomly and I can’t trigger them specifically.
you should be able to install the old kernel from pacman cache, but of course the right thing to do would be to file a bug report so the problem could be fixed.
I now have the kernel 6.12 LTS in use and will observe if the problems are solved or still occur. In a few days I can give feedback on how everything is going
Short update:
Since I switched to kernel 6.12, the crashes have disappeared. So the problem seems to be with kernel 6.15.3.
Kernel 6.14.6 was stable, too bad it is EOL, but maybe the problems will be fixed in 6.15 later.
Thank you very much for your help
Most welcome.
Good to know you’re back on track.
Just a note on;
It’s my opinion that it’s unlikely for AMD graphics to cause much grief (unlike Nvidia), unless other factors might be contributing. Drivers for AMD graphics are generally kernel modules, rather than user-installable drivers. This is why switching to another kernel can seem to magically cure an issue.
So, if there was actually an issue with the 6.12 (LTS) on your hardware, it’s likely (as you suggest) that an update in the meantime had solved that issue.
Once an LTS kernel is known to be stable, it receives a lot of ongoing care an attention; this is why they are recommended.
Regards.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.