Application: plasmashell (6.3.2) ApplicationNotResponding [ANR]: false Qt Version: 6.8.2 Frameworks Version: 6.11.0 Operating System: Linux 6.13.5-200.fc41.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 41 (KDE Plasma)" DrKonqi: 6.3.2 [CoredumpBackend] -- Information about the crash: =============================== CPU: AMD Ryzen 9 5900 OEM (12 Cores/24 Threads) GPU: AMD Radeon RX 6800 Motherboard: Gigabyte X570SI Aorus Pro AX Memory: Micron 64 GB (2 x 32 GB) DDR4-3200 VLP ECC UDIMM 2Rx8 CL22 Root: Samsung 860 EVO SATA 500GB Home: Samsung 990 Pro NVMe 4TB File System: BTRFS Operating System: Fedora 41 KDE Plasma Kernel: 6.13.5-200.fc41.x86_64 (64-bit) =============================== This crash is a catalyst of another AMDGPU crash that happens when I play Marvel Rivals. In this instance and report, it happened when I merely opened the OBS application. This is par for the course when a crash like this happens. AMDGPU successfully resets, but some of the applications refuse to open, some applications that can open just lead to another crash, and some applications just open normally without problems. This behavior ONLY occurs post initial AMDGPU crash and reset when playing Marvel Rivals, and ONLY if the GPU successfully resets. But, the behavior goes away after a full system restart. =============================== That said, my main issue is with Marvel Rivals. I have a random GPU crash that happens ONLY when I play Marvel Rivals on Steam. I've read on multiple threads that the RDNA 2 GPUs, specifically, don't play too well with Unreal games. One of the threads in question: https://community.amd.com/t5/pc-graphics/my-rx-6800-keeps-crashing-to-desktop/m-p/441086/highlight/true#M71472 The link above mentioned a -100 MHz clock to both the stock minimum and boost clocks, to prevent the GPU from voltage spiking. I did this using a custom power profile in CoreCTRL that activates when the game launches. It also mentioned the issue could be PSU power draw related, and the workaround was to use two PCIe power cable rather than just the one cable with the double connector. I did that, and I even tried to plug the system to the wall rather than the power strip I was using, to see if that helped. These workarounds reduced the crashes, but they're still very much present. The worst part is that it's very RANDOM. Sometimes it crashes in the middle of a game, and sometimes it doesn't. Sometimes it resets to desktop, and sometimes it hangs on a frozen and artifacted screen. Usually, the system just fails to reset AMDGPU after a crash in Marvel Rivals, resulting in a blackscreen and a frozen screen with artifacting that rotates every 10 seconds trying to (unsuccessfully) reset the GPU. 90% of the time, I'm forced to do a hard shutdown of the system, which is not ideal. On an unrelated note, this was also an issue in the Monster Hunter Wilds Beta Test, but it has since been fixed in the full release so far. I'm at a loss, and I'm starting to think the GPU itself is the culprit. =============================== Here's the JournalCTL output from the initial Marvel Rivals crash that came before this current crash report below: user@system:~$ journalctl --system -b Mar 08 22:55:26 system abrt-server[12022]: Deleting problem directory ccpp-2025-03-08-22:55:18.588229-2570 (dup of ccpp-2024-11-24-00:51:53.626220-2389) Mar 08 22:55:26 system abrt-notification[12377]: [🡕] Process 2389 (Xwayland) crashed in amdgpu_ctx_create(radeon_winsys*, radeon_ctx_priority, bool)() Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Dumping IP State Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Dumping IP State Completed Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x1 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301430 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301430 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x1 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301430 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.1.0 timeout, but soft recovered Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in process kwin_wayland pid 2429 thread kwin_wayla:cs0 pid 2491 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800010000000 from client 0x1b (UTCL2) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301430 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 08 22:55:28 system kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0 Mar 08 22:55:34 system abrt-server[12101]: Deleting problem directory ccpp-2025-03-08-22:55:19.786712-2536 (dup of ccpp-2024-12-30-02:34:53.491237-2456) Mar 08 22:55:34 system abrt-notification[12451]: [🡕] Process 2456 (maliit-keyboard) crashed in amdgpu_ctx_create(radeon_winsys*, radeon_ctx_priority, bool)() Mar 08 22:55:34 system abrt-server[12102]: Unsupported container technology Mar 08 22:55:34 system abrt-server[12102]: Lock file '.lock' was locked by process 12456, but it crashed? Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: Dumping IP State Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: Dumping IP State Completed Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=5768386, emitted seq=5768388 Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: Process information: process webcord pid 12114 thread webcord:cs0 pid 12127 Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: Starting gfx_0.0.0 ring reset Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: Ring gfx_0.0.0 reset failure Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset begin! Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: MODE1 reset Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: GPU mode1 reset Mar 08 22:55:39 system kernel: amdgpu 0000:0c:00.0: amdgpu: GPU smu mode1 reset Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset succeeded, trying to resume Mar 08 22:55:40 system kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000). Mar 08 22:55:40 system kernel: [drm] VRAM is lost due to GPU reset! Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: PSP is resuming... Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: reserve 0xa00000 from 0x83fd000000 for PSP TMR Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resuming... Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5a00 (58.90.0) Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: SMU driver if version not matched Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: use vbios provided pptable Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resumed successfully! Mar 08 22:55:40 system kernel: [drm] kiq ring mec 2 pipe 1 q 0 Mar 08 22:55:40 system kernel: [drm] DMUB hardware initialized: version=0x02020020 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma2 uses VM inv eng 15 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma3 uses VM inv eng 16 on hub 0 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8 Mar 08 22:55:40 system kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset(5) succeeded! Mar 08 22:55:40 system kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Mar 08 22:55:41 system audit[12241]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12241 comm="plasmashel:cs0" exe="/usr/bin/plasmashell" sig=6 res=1 Mar 08 22:55:41 system systemd-coredump[12643]: Process 12241 (plasmashell) of user 1000 terminated abnormally with signal 6/ABRT, processing... Mar 08 22:55:41 system audit: BPF prog-id=108 op=LOAD Mar 08 22:55:41 system audit: BPF prog-id=109 op=LOAD Mar 08 22:55:41 system audit: BPF prog-id=110 op=LOAD Mar 08 22:55:41 system systemd[1]: Started systemd-coredump@5-12643-0.service - Process Core Dump (PID 12643/UID 0). Mar 08 22:55:41 system audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@5-12643-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? r> Mar 08 22:55:41 system audit: BPF prog-id=111 op=LOAD Mar 08 22:55:41 system audit: BPF prog-id=112 op=LOAD Mar 08 22:55:41 system audit: BPF prog-id=113 op=LOAD Mar 08 22:55:41 system systemd[1]: Started drkonqi-coredump-processor@5-12643-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. Mar 08 22:55:41 system audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=drkonqi-coredump-processor@5-12643-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te> Mar 08 22:55:41 system abrt-dump-journal-core[1757]: Failed to obtain all required information from journald Mar 08 22:55:41 system abrt-server[12102]: Error: No segments found in coredump './coredump' Mar 08 22:55:41 system abrt-server[12102]: Can't open file 'core_backtrace' for reading: No such file or directory Mar 08 22:55:43 system systemd[1]: systemd-coredump@5-12643-0.service: Deactivated successfully. Mar 08 22:55:43 system audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@5-12643-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re> Mar 08 22:55:43 system systemd[1]: systemd-coredump@5-12643-0.service: Consumed 1.958s CPU time, 794.3M memory peak. Mar 08 22:55:43 system audit: BPF prog-id=110 op=UNLOAD Mar 08 22:55:43 system audit: BPF prog-id=109 op=UNLOAD Mar 08 22:55:43 system audit: BPF prog-id=108 op=UNLOAD Mar 08 22:55:43 system systemd[1]: drkonqi-coredump-processor@5-12643-0.service: Deactivated successfully. Mar 08 22:55:43 system audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=drkonqi-coredump-processor@5-12643-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? ter> Mar 08 22:55:44 system cupsd[1553]: REQUEST localhost - - "POST / HTTP/1.1" 200 564 Create-Printer-Subscriptions successful-ok Mar 08 22:55:44 system abrt-notification[12807]: [🡕] Process 10943 (webcord) crashed in ??() Mar 08 22:55:44 system abrt-server[12194]: Package 'freetube' isn't signed with proper key Mar 08 22:55:44 system abrt-server[12194]: 'post-create' on '/var/spool/abrt/ccpp-2025-03-08-22:55:20.799100-11264' exited with 1 Mar 08 22:55:44 system abrt-server[12194]: Deleting problem directory '/var/spool/abrt/ccpp-2025-03-08-22:55:20.799100-11264' Mar 08 22:55:53 system abrt-server[12221]: Deleting problem directory ccpp-2025-03-08-22:55:21.549042-2701 (dup of ccpp-2024-12-29-02:28:57.806876-2624) Mar 08 22:55:53 system abrt-notification[12893]: [🡕] Process 2624 (plasmashell) crashed in amdgpu_ctx_create(radeon_winsys*, radeon_ctx_priority, bool)() Mar 08 22:56:01 system abrt-server[12688]: Deleting problem directory ccpp-2025-03-08-22:55:43.549079-12241 (dup of ccpp-2024-12-29-02:28:57.806876-2624) Mar 08 22:56:01 system abrt-notification[12952]: [🡕] Process 2624 (plasmashell) crashed in amdgpu_ctx_create(radeon_winsys*, radeon_ctx_priority, bool)() Mar 08 22:56:21 system systemd[1]: pcscd.service: Deactivated successfully. Mar 08 22:56:21 system audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 08 22:57:58 system audit: BPF prog-id=72 op=UNLOAD Mar 08 22:57:58 system audit: BPF prog-id=71 op=UNLOAD Mar 08 22:57:58 system audit: BPF prog-id=114 op=LOAD Mar 08 22:57:58 system audit: BPF prog-id=115 op=LOAD Mar 08 22:57:58 system audit: BPF prog-id=116 op=LOAD Mar 08 22:57:58 system systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Mar 08 22:57:58 system systemd[1]: Started systemd-hostnamed.service - Hostname Service. Mar 08 22:57:58 system audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes> Mar 08 22:57:58 system audit: BPF prog-id=117 op=LOAD Mar 08 22:57:58 system audit: BPF prog-id=118 op=LOAD Mar 08 22:57:58 system audit: BPF prog-id=119 op=LOAD Mar 08 22:57:58 system systemd[1]: Starting systemd-timedated.service - Time & Date Service... Mar 08 22:57:58 system systemd[1]: Started systemd-timedated.service - Time & Date Service. Mar 08 22:57:58 system audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes> Mar 08 22:58:28 system systemd[1]: systemd-hostnamed.service: Deactivated successfully. Mar 08 22:58:28 system audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 08 22:58:28 system audit: BPF prog-id=114 op=UNLOAD Mar 08 22:58:28 system systemd[1]: systemd-timedated.service: Deactivated successfully. Mar 08 22:58:28 system audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 08 22:58:28 system audit: BPF prog-id=119 op=UNLOAD Mar 08 22:58:28 system audit: BPF prog-id=118 op=UNLOAD Mar 08 22:58:28 system audit: BPF prog-id=117 op=UNLOAD =============================== Let me know if more detail is needed, and I will happily provide it. Thanks! =============================== The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x00007f0ff5c80183 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78 #7 0x00007f0ff5c26f9e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f0ff5c0e942 in __GI_abort () at abort.c:79 #9 0x00007f0fd1bbbad0 in amdgpu_ctx_set_sw_reset_status(radeon_winsys_ctx*, pipe_reset_status, char const*, ...) () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so Reported using DrKonqi
Created attachment 179243 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Searchable backtrace Thread 1 (Thread 0x7f0fc95ff6c0 (LWP 31135)): [KCrash Handler] #5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x00007f0ff5c80183 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78 #7 0x00007f0ff5c26f9e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f0ff5c0e942 in __GI_abort () at abort.c:79 #9 0x00007f0fd1bbbad0 in amdgpu_ctx_set_sw_reset_status(radeon_winsys_ctx*, pipe_reset_status, char const*, ...) () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #10 0x00007f0fd1bbfa44 in void amdgpu_cs_submit_ib<(queue_type)0>(void*, void*, int) () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #11 0x00007f0fd16b1ca1 in util_queue_thread_func () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #12 0x00007f0fd16e719c in impl_thrd_routine () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #13 0x00007f0ff5c7e168 in start_thread (arg=<optimized out>) at pthread_create.c:448 #14 0x00007f0ff5d0214c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
This is a duplicate of 493679. The fix requires Qt changes which are in progress with https://codereview.qt-project.org/c/qt/qtbase/+/606100 and https://codereview.qt-project.org/c/qt/qtwayland/+/606101 *** This bug has been marked as a duplicate of bug 493679 ***
> This is a duplicate of 493679. The fix requires Qt changes which are in > progress with https://codereview.qt-project.org/c/qt/qtbase/+/606100 and > https://codereview.qt-project.org/c/qt/qtwayland/+/606101 Gotcha! But, does this fix "fix" the underlying crash event in Marvel Rivals? Correct me if I'm wrong (I'm not a developer), but it looks like this fix helps with plasma-shell recovery during and after the crash. However, the main crash in Marvel Rivals, that led with all of this, will still be present. Should I file a separate bug report (with back traces and all) for the main crash event in Marvel Rivals? Can KDE even deal with such a bug report? If not, what channels and forums do I need to contact to report this crash event?
(In reply to adros from comment #4) > But, does this fix "fix" the underlying crash event in Marvel Rivals? QT bug 606100 makes information available to applications that their developers need to do something with. QT 606101 provides support for GPU resets, which should fix crashes caused by that. > However, the > main crash in Marvel Rivals, that led with all of this, will still be > present. > > Should I file a separate bug report (with back traces and all) for the main > crash event in Marvel Rivals? If you have a crash from Marvel Rivals and the backtrace is different than the one in this report, we can take a look. Please open a new bug report for it. If it needs to be reported somewhere else, we'll let you know. We're happy to help determine what the right course of action is.