Artix Linux Forum

Hello.

In multiple situations (browsing files in thunar, listening music in Audacious, audio work in Ardour, watching YT videos in LibreWolf, etc.) the picture freezes, although the audio remains playing and the cursor is responsive. I can't turn numlock or capslock on/off and I can't switch to another tty. After some 20 seconds both audio and cursor movement get choppy until everything freezes. Then I have to restart the PC manually.

My system is an Ryzen 5 processor with Radeon Vega 12 graphics.
I'm using Artix with xorg and pipewire, dwm as the window manager. After the initial install a few months ago, the system ran with no issues. I think this started happening after an update but I don't know when exactly.
For the last few weeks I've been running the system mostly to play GZDoom and it never crashed in-game so I noticed the crashing fairly recently.

Originally I've installed linux-rt with it's headers but recently I've tried linux-rt-lts, linux-lts and I'm currently on the latest Linux 6.12.7, all having the same issues.

I've used the bios (HP) memory check and it completed with no errors.


lspci:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex
	Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex
	Flags: fast devsel

00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU
	Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU
	Flags: fast devsel, IRQ 27
	Capabilities: [40] Secure device <?>
	Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
	Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
	Flags: fast devsel, IOMMU group 0

00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
	Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 0
	Bus: primary=00, secondary=01, subordinate=08, sec-latency=0
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: b0800000-b0afffff [size=3M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot+), IntMsgNum 0
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
	Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express
	Capabilities: [370] L1 PM Substates
	Kernel driver in use: pcieport

00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
	Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 0
	Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: b0700000-b07fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot+), IntMsgNum 0
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
	Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express
	Capabilities: [370] L1 PM Substates
	Kernel driver in use: pcieport

00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
	Flags: fast devsel, IOMMU group 1

00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD] Device 0000
	Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 1
	Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
	I/O behind bridge: 2000-2fff [size=4K] [16-bit]
	Memory behind bridge: b0300000-b06fffff [size=4M] [32-bit]
	Prefetchable memory behind bridge: a0000000-b01fffff [size=258M] [32-bit]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot-), IntMsgNum 0
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device 0000
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express
	Kernel driver in use: pcieport

00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD] Device 0000
	Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 1
	Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: b0200000-b02fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot-), IntMsgNum 0
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device 0000
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express
	Kernel driver in use: pcieport

00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: 66MHz, medium devsel, IOMMU group 2
	Kernel modules: i2c_piix4, sp5100_tco

00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 2

00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0
	Flags: fast devsel, IOMMU group 3

00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1
	Flags: fast devsel, IOMMU group 3

00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2
	Flags: fast devsel, IOMMU group 3

00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3
	Flags: fast devsel, IOMMU group 3
	Kernel driver in use: k10temp
	Kernel modules: k10temp

00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4
	Flags: fast devsel, IOMMU group 3

00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5
	Flags: fast devsel, IOMMU group 3

00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6
	Flags: fast devsel, IOMMU group 3

00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7
	Flags: fast devsel, IOMMU group 3

01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset USB 3.1 xHCI Controller (rev 02) (prog-if 30 [XHCI])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 45, IOMMU group 0
	Memory at b0a20000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [50] MSI: Enable+ Count=8/8 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] Secondary PCI Express
	Capabilities: [300] Latency Tolerance Reporting
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: xhci_hcd

01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 0
	Memory at b0a00000 (32-bit, non-prefetchable) [size=128K]
	Expansion ROM at b0a80000 [disabled] [size=512K]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
	Capabilities: [100] Advanced Error Reporting
	Kernel driver in use: ahci

01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b2 (rev 02) (prog-if 00 [Normal decode])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 0
	Bus: primary=01, secondary=02, subordinate=08, sec-latency=0
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: b0800000-b09fffff [size=2M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Upstream Port, IntMsgNum 0
	Capabilities: [c0] Subsystem: Hewlett-Packard Company Device 83e9
	Capabilities: [100] Advanced Error Reporting
	Kernel driver in use: pcieport

02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) (prog-if 00 [Normal decode])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 32, IOMMU group 0
	Bus: primary=02, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Downstream Port (Slot+), IntMsgNum 0
	Capabilities: [c0] Subsystem: Hewlett-Packard Company Device 83e9
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] Secondary PCI Express
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: pcieport

02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) (prog-if 00 [Normal decode])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 0
	Bus: primary=02, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Downstream Port (Slot+), IntMsgNum 0
	Capabilities: [c0] Subsystem: Hewlett-Packard Company Device 83e9
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] Secondary PCI Express
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: pcieport

02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) (prog-if 00 [Normal decode])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 0
	Bus: primary=02, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: b0900000-b09fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Downstream Port (Slot+), IntMsgNum 0
	Capabilities: [c0] Subsystem: Hewlett-Packard Company Device 83e9
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] Secondary PCI Express
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: pcieport

02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3306
	Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 0
	Bus: primary=02, secondary=06, subordinate=06, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: b0800000-b08fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Downstream Port (Slot+), IntMsgNum 0
	Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device 3306
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] Secondary PCI Express
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: pcieport

02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3306
	Flags: bus master, fast devsel, latency 0, IRQ 37, IOMMU group 0
	Bus: primary=02, secondary=07, subordinate=07, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Downstream Port (Slot+), IntMsgNum 0
	Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device 3306
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] Secondary PCI Express
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: pcieport

02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3306
	Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 0
	Bus: primary=02, secondary=08, subordinate=08, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Downstream Port (Slot+), IntMsgNum 0
	Capabilities: [c0] Subsystem: ASMedia Technology Inc. Device 3306
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [200] Secondary PCI Express
	Capabilities: [400] L1 PM Substates
	Kernel driver in use: pcieport

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 0e)
	DeviceName: Onboard LAN
	Subsystem: Hewlett-Packard Company Device 8464
	Flags: bus master, fast devsel, latency 0, IRQ 25, IOMMU group 0
	I/O ports at 3300 [size=256]
	Memory at b0914000 (64-bit, non-prefetchable) [size=4K]
	Memory at b0900000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, IntMsgNum 1
	Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 01-00-a1-6d-52-d1-d8-e8
	Capabilities: [170] Latency Tolerance Reporting
	Capabilities: [178] L1 PM Substates
	Kernel driver in use: r8169
	Kernel modules: r8169

05:00.1 Serial controller: Realtek Semiconductor Co., Ltd. RTL8111xP UART #1 (rev 0e) (prog-if 02 [16550])
	Subsystem: Hewlett-Packard Company Device 8464
	Flags: fast devsel, IRQ 33, IOMMU group 0
	I/O ports at 3200 [size=256]
	Memory at b0915000 (64-bit, non-prefetchable) [size=4K]
	Memory at b0904000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, IntMsgNum 1
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [170] Latency Tolerance Reporting
	Capabilities: [178] L1 PM Substates
	Kernel driver in use: serial

05:00.2 Serial controller: Realtek Semiconductor Co., Ltd. RTL8111xP UART #2 (rev 0e) (prog-if 02 [16550])
	Subsystem: Hewlett-Packard Company Device 8464
	Flags: fast devsel, IRQ 24, IOMMU group 0
	I/O ports at 3100 [size=256]
	Memory at b0916000 (64-bit, non-prefetchable) [size=4K]
	Memory at b0908000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, IntMsgNum 1
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [170] Latency Tolerance Reporting
	Capabilities: [178] L1 PM Substates
	Kernel driver in use: serial

05:00.3 IPMI Interface: Realtek Semiconductor Co., Ltd. RTL8111xP IPMI interface (rev 0e) (prog-if 01 [KCS])
	Subsystem: Hewlett-Packard Company Device 8464
	Flags: fast devsel, IRQ 255, IOMMU group 0
	I/O ports at 3000 [disabled] [size=256]
	Memory at b0917000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Memory at b090c000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, IntMsgNum 1
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [170] Latency Tolerance Reporting
	Capabilities: [178] L1 PM Substates
	Kernel modules: ipmi_si

05:00.4 USB controller: Realtek Semiconductor Co., Ltd. RTL811x EHCI host controller (rev 0e) (prog-if 20 [EHCI])
	Subsystem: Hewlett-Packard Company Device 8464
	Flags: bus master, fast devsel, latency 0, IRQ 44, IOMMU group 0
	Memory at b0918000 (32-bit, non-prefetchable) [size=4K]
	Memory at b0910000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, IntMsgNum 1
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [170] Latency Tolerance Reporting
	Capabilities: [178] L1 PM Substates
	Kernel driver in use: ehci-pci

06:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [Stone Peak 2 AC]
	Flags: bus master, fast devsel, latency 0, IRQ 87, IOMMU group 0
	Memory at b0800000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, IntMsgNum 0
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 14-18-c3-ff-ff-36-eb-51
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] L1 PM Substates
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

09:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. NV2 NVMe SSD [SM2267XT] (DRAM-less) (rev 03) (prog-if 02 [NVM Express])
	Subsystem: Kingston Technology Company, Inc. NV2 NVMe SSD [SM2267XT] (DRAM-less)
	Flags: bus master, fast devsel, latency 0, IRQ 71, IOMMU group 0
	Memory at b0700000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
	Capabilities: [70] Express Endpoint, IntMsgNum 0
	Capabilities: [b0] MSI-X: Enable+ Count=16 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [158] Secondary PCI Express
	Capabilities: [178] Physical Layer 16.0 GT/s <?>
	Capabilities: [19c] Lane Margining at the Receiver
	Capabilities: [1b4] Latency Tolerance Reporting
	Capabilities: [1bc] L1 PM Substates
	Kernel driver in use: nvme
	Kernel modules: nvme

0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev d6) (prog-if 00 [VGA controller])
	DeviceName: Onboard IGD
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 62, IOMMU group 1
	Memory at a0000000 (64-bit, prefetchable) [size=256M]
	Memory at b0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at 2000 [size=256]
	Memory at b0600000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [64] Express Legacy Endpoint, IntMsgNum 0
	Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+
	Capabilities: [c0] MSI-X: Enable+ Count=3 Masked-
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [200] Physical Resizable BAR
	Capabilities: [270] Secondary PCI Express
	Capabilities: [2b0] Address Translation Service (ATS)
	Capabilities: [2c0] Page Request Interface (PRI)
	Capabilities: [2d0] Process Address Space ID (PASID)
	Capabilities: [320] Latency Tolerance Reporting
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

0a:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 86, IOMMU group 1
	Memory at b0680000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [64] Express Legacy Endpoint, IntMsgNum 0
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

0a:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 41, IOMMU group 1
	Memory at b0500000 (32-bit, non-prefetchable) [size=1M]
	Memory at b0684000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [64] Express Endpoint, IntMsgNum 0
	Capabilities: [a0] MSI: Enable- Count=1/2 Maskable- 64bit+
	Capabilities: [c0] MSI-X: Enable+ Count=2 Masked-
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Kernel driver in use: ccp
	Kernel modules: ccp

0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 (prog-if 30 [XHCI])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 53, IOMMU group 1
	Memory at b0300000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [64] Express Endpoint, IntMsgNum 0
	Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+
	Capabilities: [c0] MSI-X: Enable+ Count=8 Masked-
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Kernel driver in use: xhci_hcd

0a:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 (prog-if 30 [XHCI])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 62, IOMMU group 1
	Memory at b0400000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [64] Express Endpoint, IntMsgNum 0
	Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+
	Capabilities: [c0] MSI-X: Enable+ Count=8 Masked-
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Kernel driver in use: xhci_hcd

0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) (prog-if 01 [AHCI 1.0])
	Subsystem: Hewlett-Packard Company Device 83e9
	Flags: bus master, fast devsel, latency 0, IRQ 42, IOMMU group 1
	Memory at b0200000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [64] Express Endpoint, IntMsgNum 0
	Capabilities: [a0] MSI: Enable+ Count=2/2 Maskable- 64bit+
	Capabilities: [d0] SATA HBA v1.0
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express
	Kernel driver in use: ahci

dmesg:

https://paste.artixlinux.org/a8393c87

lsmod:

Module                  Size  Used by
ccm                    20480  6
snd_seq_midi           20480  0
snd_seq_dummy          12288  0
snd_seq_midi_event     16384  1 snd_seq_midi
snd_hrtimer            12288  1
snd_seq               131072  9 snd_seq_midi,snd_seq_midi_event,snd_seq_dummy
vfat                   24576  1
fat                   110592  1 vfat
r8153_ecm              12288  0
cdc_ether              24576  1 r8153_ecm
usbnet                 61440  2 r8153_ecm,cdc_ether
amd_atl                57344  1
intel_rapl_msr         20480  0
intel_rapl_common      53248  1 intel_rapl_msr
iwlmvm                753664  0
kvm_amd               237568  0
kvm                  1388544  1 kvm_amd
mac80211             1638400  1 iwlmvm
crct10dif_pclmul       12288  1
crc32_pclmul           12288  0
polyval_clmulni        12288  0
libarc4                12288  1 mac80211
polyval_generic        12288  1 polyval_clmulni
ptp                    45056  1 iwlmvm
ghash_clmulni_intel    16384  0
sha512_ssse3           53248  0
pps_core               32768  1 ptp
sha1_ssse3             32768  0
snd_hda_codec_hdmi     98304  1
aesni_intel           122880  4
btusb                  77824  0
snd_hda_intel          65536  1
snd_usb_audio         557056  1
gf128mul               16384  2 polyval_generic,aesni_intel
iwlwifi               602112  1 iwlmvm
snd_intel_dspcfg       40960  1 snd_hda_intel
btrtl                  32768  1 btusb
crypto_simd            16384  1 aesni_intel
snd_usbmidi_lib        49152  1 snd_usb_audio
snd_intel_sdw_acpi     16384  1 snd_intel_dspcfg
btintel                69632  1 btusb
cryptd                 28672  2 crypto_simd,ghash_clmulni_intel
snd_ump                40960  1 snd_usb_audio
snd_hda_codec         212992  2 snd_hda_codec_hdmi,snd_hda_intel
hp_wmi                 40960  0
btbcm                  24576  1 btusb
snd_rawmidi            57344  3 snd_seq_midi,snd_usbmidi_lib,snd_ump
r8152                 167936  1 r8153_ecm
rapl                   20480  0
platform_profile       12288  1 hp_wmi
snd_hda_core          147456  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
btmtk                  32768  1 btusb
snd_seq_device         16384  4 snd_seq,snd_seq_midi,snd_ump,snd_rawmidi
snd_hwdep              20480  2 snd_usb_audio,snd_hda_codec
joydev                 28672  0
mousedev               24576  0
mc                     90112  1 snd_usb_audio
wmi_bmof               12288  0
mii                    16384  2 usbnet,r8152
r8169                 126976  0
cfg80211             1396736  3 iwlmvm,iwlwifi,mac80211
sparse_keymap          12288  1 hp_wmi
snd_pcm               200704  5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
bluetooth            1097728  6 btrtl,btmtk,btintel,btbcm,btusb
acpi_cpufreq           32768  0
k10temp                16384  0
pcspkr                 12288  0
realtek                45056  1
mdio_devres            12288  1 r8169
ipmi_devintf           20480  0
snd_timer              57344  3 snd_seq,snd_hrtimer,snd_pcm
libphy                229376  4 r8169,mdio_devres,realtek,r8152
ucsi_acpi              12288  0
sp5100_tco             20480  0
rfkill                 40960  6 hp_wmi,iwlmvm,bluetooth,cfg80211
ipmi_msghandler        94208  1 ipmi_devintf
crypto_user            20480  0
snd                   155648  18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_ump,snd_pcm,snd_rawmidi
i2c_piix4              36864  0
ccp                   184320  1 kvm_amd
typec_ucsi             77824  1 ucsi_acpi
soundcore              16384  1 snd
i2c_smbus              20480  1 i2c_piix4
typec                 110592  1 typec_ucsi
gpio_amdpt             16384  0
roles                  16384  1 typec_ucsi
mac_hid                12288  0
gpio_generic           24576  1 gpio_amdpt
hid_generic            12288  0
usbhid                 86016  0
amdgpu              15421440  5
btrfs                2170880  1
blake2b_generic        24576  0
libcrc32c              12288  1 btrfs
crc32c_generic         12288  0
crc16                  12288  2 bluetooth,amdgpu
xor                    20480  1 btrfs
amdxcp                 12288  1 amdgpu
raid6_pq              122880  1 btrfs
i2c_algo_bit           20480  1 amdgpu
drm_ttm_helper         16384  2 amdgpu
ttm                   106496  2 amdgpu,drm_ttm_helper
drm_exec               12288  1 amdgpu
gpu_sched              65536  1 amdgpu
nvme                   65536  3
drm_suballoc_helper    12288  1 amdgpu
drm_buddy              24576  1 amdgpu
crc32c_intel           16384  2
drm_display_helper    270336  1 amdgpu
sha256_ssse3           36864  0
nvme_core             258048  4 nvme
cec                    94208  1 drm_display_helper
nvme_auth              24576  1 nvme_core
video                  81920  1 amdgpu
wmi                    28672  3 hp_wmi,video,wmi_bmof

lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 1210:0002 DigiTech Lexicon Omega
Bus 004 Device 003: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub             
Bus 004 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 004 Device 005: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 004 Device 006: ID 258a:0049 BY Tech Gaming Keyboard
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

xorg:

https://paste.artixlinux.org/c61b3160

Thanks.

I had the exact same issue, is your box an Elitedesk 705 G4 Tiny? It's almost certainly not the kernel (I tried several versions). I downgraded the entire system to a known working date (my last full system update was in September) and freezes were gone.Then upgraded everything except amd-ucode, xf86-video-amdgpu, linux-firmware and mesa, still no freezes. Can't afford the time and lack the patience to test which one exactly is responsible, it would be nice if you could and reported back.

[    0.000000] DMI: HP HP EliteDesk 705 G4 DM 65W/83E9, BIOS Q26 Ver. 02.14.01 10/16/2020
It is indeed the HP.

Anyway, I've had similar things happening to me when I freshly installed the Artix system exactly 1 year ago and it stopped doing that after I added `sysrq_always_enabled=1` as a kernel parameter setting, but im not sure if that's the case. Also, please try to temporarly remove amd-ucode just for test, refresh your mkinitcpio (sudo mkinitcpio -Pv) and then reboot and test if stuff like this happens again...

These symptoms can indicate some component is overheating, so also keep an eye on the CPU and GPU temps.

artist

Thank you for all the replies.

Before downgrading the packages, I will first try what Shoun2137 suggested.
So, I never even installed the amd-ucode package, I've refreshed the mkinitcpio and added the 'sysrq_always_enabled=1' parameter and rebooted.

As far as I can tell, overheating isn't an issue but I'll add some widgets to my wm bar just to keep an eye on them a bit more closely.

Will report back.

It looks like the culprit was the mesa-1:24.3.2-1 driver.

I've updated the system to the latest packages and downgraded the mesa driver to 1:24.2.2-1. No crashes since.

This is what I've found after some duckduckgoing:

Gitlab issue: mesa 24.3.1 gallium crash/segfault on GPUs without format modifiers (https://gitlab.freedesktop.org/mesa/mesa/-/issues/12253)

Gitlab issue: Systemfreeze from mesa version 1:24.3.0-1-x86_64 and above with Chromium and derivatives (https://gitlab.freedesktop.org/mesa/mesa/-/issues/12310)

Arch Linux Forum post: Issues with Mesa 24.3.x and amdgpu Vega graphics (https://bbs.archlinux.org/viewtopic.php?id=301798)


Thanks again, hopefully they'll fix this this.

It'll probably get fixed once mesa-24.3.x rolls out to more distros and the reports start stacking.

Currently dealing with this issue (or symptoms atleast). Not sure if it stems from the same problem. (I'm thinking since it's the same symptoms the probability of the cause of the problem you and I have might be the same.)

My post in reference to the problem I've mentioned: https://forum.artixlinux.org/index.php/topic,7551.msg45299.html

I've tried everything I can think of used standard, zen, and lts kernels. Used mesa-git and compiled older version as well. (by modifiying the pkgver in PKGBUILD of the mesa-git (though I only changed the version, not the libraries (one that is required to compile it) as well). changed compositors, dwl, sway, and dwm.))

I notice that it crashes more frequently if I used programs that use xorg/xwayland.

There are a few things I would like to ask and if possible ask you to reproduce the freeze. (I found how to do it with mine. I just want to confirm if this bug reproduction will work with you as well)

1. Are you using a window manager?

2. Do you have the packages steam, krita, and mesa-utils?

3. Can you please reproduce the freeze for me? (launch krita and open any image, steam, and glxgears. Then hold the switch focus key binding for the window manager until it freezes the pc). (demo: https://imgur.com/a/2rnuVTF)

4. Optional for the test: install wtype to simulate keyboard press and just loop the focus switching. (I can throw in the script if you want).

Notes.
1. I don't think mine is an overheating issue as well, tried GPU benchmarks, virtual machines and other intensive tasks. It finished it without freezes.

clappingsnowdrop:
I've installed mesa-utils, steam and krita and couldn't reproduce the crash with the older mesa 24.2.2

However, a new mesa 24.3.3 came out, so far I couldn't reproduce your crash using it as well.
I'm going to test it for a while and let you know if the crashes persist.


EDIT: It still crashes, reverted both mesa and lib32-mesa to 24.2.7 (the latest 24.2.x).

Please, keep us updated, I'm still keeping mesa pinned.

Teapotahedron:

Thanks for the heads-up.

At this point I'll probably end up trying to manually compile the kernel. Although it's been a long time since I've done so. So I probably won't be able to do it for quite some time. (Years ago when I think I had to prove to myself I could install Gentoo when I just started my Linux journey.)

Update:

So, a new problem, x wouldn't start and posted an error in tty. I've checked the log and found that the new version of either llvm or llvm-libs (19.1.6 in both cases) causes it.

So, in addition to downgrading mesa to 24.2.7, now I also have to downgrade llvm and llvm-libs to 18.1.8-5.

There were no mesa drivers updates since my last post so no news there.

I had hoped the latest mesa wouldn't freeze the system, but I was wrong. As this is effectively holding the entire system back, I'm thinking of rebuilding v24.2.7...

An update.

So, mesa received a 25.0.0 update on feb.09th (https://docs.mesa3d.org/relnotes/25.0.0.html) and I've been waiting since for it to be included in arch packages but nothing yet. Today I got impatient and built both mesa-git (https://aur.archlinux.org/packages/mesa-git) and lib32-mesa-git (https://aur.archlinux.org/packages/lib32-mesa-git) packages (currently on 25.1.0._devel versions) using yay.

So far, I've tested it scenarios which usually crashed the system and there were none. Let's hope V25 resolved the issue.

Thanks for the info, we put mesa-git to [galaxy] [omniverse].

FYI--and anyone else who might think to use this as a cure for this problem--I just installed the two of these and left my PC to do some other things only to return to another crash. I find disabling display compositing helps a lot, but it doesn't solve the problem completely.

I would like to downgrade both to versions that didn't cause this problem, but the last time I tried, I found multiple programs (specifically games) would not run at all. I'm thinking there were some other dependent or otherwise related packages that also needed to be downgraded to match; if so, can anyone tell me the proper way to downgrade those two packages? That, and/or the proper way to go about downgrading them.

There are two methods that I know of.

1.) Using older downloaded packages.
Check if you have mesa and lib32-mesa packages in your pacman cache: (If you still have these then lucky you.)

find /var/cache/pacman/pkg -iname "*mesa*"  2> /dev/null 

then follow: https://wiki.archlinux.org/title/Downgrading_packages

2.) Manual Compilation.

Note: freedesktop is currently on the process of server migration, might have issues on downloading the files. I did check and it worked fine as of posting this reply. Just a heads up.

I don't know about proper, but I did the downgrade on packages like this by cloning:

https://aur.archlinux.org/packages/mesa-git
https://aur.archlinux.org/packages/lib32-mesa-git

editing the PKGBUILD file's pkgver= (check the available versions on gitlab: https://gitlab.freedesktop.org/mesa/mesa):

pkgver=pkgver=25.0.0_devel.200052.bed748d5f6d.d41d8cd

to 

pkgver=24.2.7 (this is an example, choose the version you want on the gitlab site specified above)

To avoid problems you may want to set the PKGBUILD files as immutable: (I've had the issue where it would compile mesa as the latest version unless I did this.)

chattr +i PKGBUILD
to undo: 
chattr -i PKGBUILD

You may need to edit the dependency requirements too. Such as using an older dependency or add some missing ones.


Hope this works out for you. Cheers.

Thanks for the reply. Fortunately, I do have mesa and lib32-mesa packages dating back to last October. That being said, those instructions (1.1--I didn't think the kernel needed downgrading) were what I followed the last time I tried to downgrade.

Evidently, (https://discussion.fedoraproject.org/t/mesa-25-0-can-cause-sluggishness-black-screen-sudden-freeze-on-amd-and-nvidia-gpus/147143) even 25.* still causes problems, so it seems downgrading is the only option. My problem, however, is finding my games failing to start after such a downgrade. Wine doesn't say anything relevant about the failures, so I don't really know which dependencies are affected or not. EDIT: Lutris has a log I've yet to check, so I'll try that out tomorrow.

Downgrading the kernel isn't necessary(I assume you meant instruction 1.2 in the arch wiki (which is for when you have issues when you have updated the kernel)).

Step 1.1 is good enough for mesa / lib32-mesa.

Still If you want to try older kernel versions, you can just either just do step 1(from my earlier response, not the arch wiki steps), or use an lts kernel.

Yup, tried again--same result. Tried downgrading packages I found to be related to them when I installed mesa-git the other day, but that didn't work either; Fallout NV ran extremely slowly, and graphics card wasn't properly ID. Then it crashed, some time after.

Figured I'd just give up and go with 1:25.0.1-2, as the regular version is on the repository now, and I don't quite trust the snapshot downgrade tactic. We'll see what happens.

EDIT: Found out in roughly one hour.

Partially downgrading mesa won't cut it; it's too important a component to not break stuff. You should downgrade the entire system (https://wiki.archlinux.org/title/Arch_Linux_Archive#How_to_restore_all_packages_to_a_specific_date) to the last days of mesa-24.2.7 (just replace https://archive.archlinux.org/ with https://archive.artixlinux.org/).

Learned something new today, thanks for this. Didn't knew Artix had legacy packages. This makes it easier to go down and untangle through the dependecy hell ball of yarn.

I'm not sure that Antilles' problem is the same as the one I started the topic with.

That being said, I noticed that mesa and lib32-mesa in the arch repo finally reached 25.0.2 so i did a

sudo pacman -S mesa lib32-mesa

and removed the 25.0.1 Git which I installed from the AUR.

After testing I can confirm that everything runs fine, in my instance of the problem, at least (AMD Ryzen related). Solved?

Let's wait for a couple more confirmations.

@nous I came here from:

https://forum.artixlinux.org/index.php/topic,7892.msg47442.html

I tried updating to the latest version of mesa (1:25.0.4-1) and the problem still persists on my end.

@Teapotahedron are you still having issues?

I no longer have issues.

mesa 25.0.5 did solve the issue for some users that experienced issues like this mesa-related.

But there also is a similar issue kernel related.

https://gitlab.freedesktop.org/drm/amd/-/issues/3067 has a long discussion about this.

sounds familiar, AMDGPU here as well.

Not sure if it will work for everyone here, but I've had this fucking problem (Yes I was annoyed. It's been months now.) and I think I may have finally cracked the code. For me at least.

So I disabled steam and librewolf's hardware acceleration. And for a week now it's been deafeningly silence on how smooth and no freezing the computer is. No matter the minor or huge Mesa updates were the freezing never stopped until this solution.

Downside is, no hardware acceleration. So scrolling isn't very smooth on some websites. But other than that it's working great. I'll take it over system freeze anytime.

My best guess of what causes the problem:
This Issue happens when xwayland runs in the background or you're using xorg instead of wayland and then you have a program that has hardware acceleration on.

:(

Isn't mesa a 3d accelerator?

Can elaborate?

That solution (downgrading mesa) was offered, and it worked for others (good for them), but not for me and the others (even though the symptoms are the same (title of this thread)). This solution worked for me, and by posting that solution I hope that works out for others too.

will try.

nope, still crashes.

You still should get something in dmesg, is there any module/driver/library segfault/crash in there? If the system isn't recoverable after the crash, it should still write something to dmesg, but NEXT REBOOT will overwrite that, so you should boot off usb w/ iso and check if there's any clue.

sometimes it's recoverable, I'll try to get into a tty.

https://pastebin.com/6c5c8VRe
dmesg right after a steam error where it tries to quit but it gets stuck and a brave 'aw snap' error

https://files.catbox.moe/8la19n
dmesg output after everything froze and black screened. I managed to get into a tty and to output it to text.

https://files.catbox.moe/f72xb2.txt
happened again.

What is this 'brave' that segfaults? Browser or some kernel process named the same?


I am 99% sure this is effect, not cause, but it wouldn't hurt to take a look at this AMD core dump.

skip

it's brave broswer, it's always a 'your tab just crashed! Aw snap, error code 11' It just happens randomly.
As for the coredump, it seems it's not there anymore, I'll have to wait for another kwin crash to save it to a file.

[28400.731472] ThreadPoolForeg[2359]: segfault at 21ea91276548 ip 00007f6b9d932d20 sp 00007f6b87ffc490 error 4 in libcef.so[4531d20,7f6b9b7ed000+a36d000] likely on CPU 6 (core 0, socket 0)
segfault when starting steam, it just insta crashed. I'll try to induce a kwin crash by playing gmod or something.

Can you figure out what crashed in that quote in my previous post "[   59.968275] brave[2300]: segfault at cfa0fb80000..." and similar?

I had ton of problems before, with steam starting but games crashing, all due to missing lib32-vulkan-nouveau. I have one of those hybrid laptops with AMD and Nvidia so probably not applicable in your case.

I had that too, l4d2 couldn't launch in proton or native vulkan mode because I was missing the 32 bit vulkan drivers. That's a separate issue that is easily fixable by having all the required drivers installed.
https://files.catbox.moe/lg3fjf.txt
I managed to make it crash by launching gmod (in proton, native in both openGL and vulkan can't launch). This is as much of the coredump as I could get into a text file before it errored out for some reason.

Probably obvious and you tried it already: did you try different proton variants? I sometimes have to downgrade until they pass some bump, then it is all safe to use latest again.

This crashed process

process_name: brave PID: 2176

is still confusing, I have steam running and I don't have it. Only reference I found is in

extra/profile-sync-daemon 1:6.50-1
    usr/share/psd/contrib/brave

but it must be something else.

It happens with native games as well like tf2 and even minecraft (with sodium obviously, it gives some sort of indium rendering error usually and exit code 6 though). It also doesn't happen with RE7 running through GE proton 10-4 (RE7's intro cutscene is completely broken with default proton, it's just a bunch of color bars in the car sequence, deck verified game btw). I'll try to run gmod through it.

Brave is a browser... 

That's unfortunate. Things may seem random at first (bugs). So if it's possible, try to remember what you did before it happens. Make notes if you have to, and then try to find the pattern.

Question are you using a window manager by chance?

no, i'm using wayland kde.

Oh okay. If you were I was gonna ask you to do something as an experiment.

everything was fine until today. Now it freezes if I fullscreen youtube.
[  536.008916] ThreadPoolForeg[6656]: segfault at 1f575fda4548 ip 00007f32d8d32d20 sp 00007f32cb3fb490 error 4 in libcef.so[4531d20,7f32d6bed000+a36d000] likely on CPU 1 (core 1, socket 0)
dmesg when trying to launch steam.

Have tried different browser/browser engines?
LTS kernel?

yeah, it's started happening very often again. Steam and discord randomly crash and even freeze the system(discord and QEMU had updated, I can post the pacman log if needed) and brave still freezes everything if youtube is fullscreened.
librewolf has the same issue  last time I checked. LTS and vanilla kernel do not fix it, in fact the vanilla kernel is unusable.

maybe =1 is overkill


Linux Magic System Request Key Hacks

Documentation for sysrq.c
What is the magic SysRq key?

It is a ‘magical’ key combo you can hit which the kernel will respond to regardless of whatever else it is doing, unless it is completely locked up.
How do I enable the magic SysRq key?

You need to say “yes” to ‘Magic SysRq key (CONFIG_MAGIC_SYSRQ)’ when configuring the kernel. When running a kernel with SysRq compiled in, /proc/sys/kernel/sysrq controls the functions allowed to be invoked via the SysRq key. The default value in this file is set by the CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE config symbol, which itself defaults to 1. Here is the list of possible values in /proc/sys/kernel/sysrq:

        0 - disable sysrq completely

        1 - enable all functions of sysrq

        >1 - bitmask of allowed sysrq functions (see below for detailed function description):

          2 =   0x2 - enable control of console logging level
          4 =   0x4 - enable control of keyboard (SAK, unraw)
          8 =   0x8 - enable debugging dumps of processes etc.
         16 =  0x10 - enable sync command
         32 =  0x20 - enable remount read-only
         64 =  0x40 - enable signalling of processes (term, kill, oom-kill)
        128 =  0x80 - allow reboot/poweroff
        256 = 0x100 - allow nicing of all RT tasks

You can set the value in the file by the following command:

echo "number" >/proc/sys/kernel/sysrq

The number may be written here either as decimal or as hexadecimal with the 0x prefix. CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE must always be written in hexadecimal.

Note that the value of /proc/sys/kernel/sysrq influences only the invocation via a keyboard. Invocation of any operation via /proc/sysrq-trigger is always allowed (by a user with admin privileges).
How do I use the magic SysRq key?

On x86 - You press the key combo ALT-SysRq-<command key>.

Note

Some keyboards may not have a key labeled ‘SysRq’. The ‘SysRq’ key is also known as the ‘Print Screen’ key. Also some keyboards cannot handle so many keys being pressed at the same time, so you might have better luck with press Alt, press SysRq, release SysRq, press <command key>, release everything.

On SPARC - You press ALT-STOP-<command key>, I believe.

On the serial console (PC style standard serial ports only)
    You send a BREAK, then within 5 seconds a command key. Sending BREAK twice is interpreted as a normal BREAK.
On PowerPC
    Press ALT - Print Screen (or F13) - <command key>, Print Screen (or F13) - <command key> may suffice.
On other
    If you know of the key combos for other architectures, please let me know so I can add them to this section.
On all

    write a character to /proc/sysrq-trigger. e.g.:

    echo t > /proc/sysrq-trigger

What are the ‘command’ keys?
Command    Function
b    Will immediately reboot the system without syncing or unmounting your disks.
c    Will perform a system crash by a NULL pointer dereference. A crashdump will be taken if configured.
d    Shows all locks that are held.
e    Send a SIGTERM to all processes, except for init.
f    Will call the oom killer to kill a memory hog process, but do not panic if nothing can be killed.
g    Used by kgdb (kernel debugger)
h    Will display help (actually any other key than those listed here will display help. but h is easy to remember :-)
i    Send a SIGKILL to all processes, except for init.
j    Forcibly “Just thaw it” - filesystems frozen by the FIFREEZE ioctl.
k    Secure Access Key (SAK) Kills all programs on the current virtual console. NOTE: See important comments below in SAK section.
l    Shows a stack backtrace for all active CPUs.
m    Will dump current memory info to your console.
n    Used to make RT tasks nice-able
o    Will shut your system off (if configured and supported).
p    Will dump the current registers and flags to your console.
q    Will dump per CPU lists of all armed hrtimers (but NOT regular timer_list timers) and detailed information about all clockevent devices.
r    Turns off keyboard raw mode and sets it to XLATE.
s    Will attempt to sync all mounted filesystems.
t    Will dump a list of current tasks and their information to your console.
u    Will attempt to remount all mounted filesystems read-only.
v    Forcefully restores framebuffer console
v    Causes ETM buffer dump [ARM-specific]
w    Dumps tasks that are in uninterruptable (blocked) state.
x    Used by xmon interface on ppc/powerpc platforms. Show global PMU Registers on sparc64. Dump all TLB entries on MIPS.
y    Show global CPU Registers [SPARC-64 specific]
z    Dump the ftrace buffer
0-9    Sets the console log level, controlling which kernel messages will be printed to your console. (0, for example would make it so that only emergency messages like PANICs or OOPSes would make it to your console.)
Okay, so what can I use them for?

Well, unraw(r) is very handy when your X server or a svgalib program crashes.

sak(k) (Secure Access Key) is useful when you want to be sure there is no trojan program running at console which could grab your password when you would try to login. It will kill all programs on given console, thus letting you make sure that the login prompt you see is actually the one from init, not some trojan program.

Important

In its true form it is not a true SAK like the one in a c2 compliant system, and it should not be mistaken as such.

It seems others find it useful as (System Attention Key) which is useful when you want to exit a program that will not let you switch consoles. (For example, X or a svgalib program.)

reboot(b) is good when you’re unable to shut down. But you should also sync(s) and umount(u) first.

crash(c) can be used to manually trigger a crashdump when the system is hung. Note that this just triggers a crash if there is no dump mechanism available.

sync(s) is great when your system is locked up, it allows you to sync your disks and will certainly lessen the chance of data loss and fscking. Note that the sync hasn’t taken place until you see the “OK” and “Done” appear on the screen. (If the kernel is really in strife, you may not ever get the OK or Done message...)

umount(u) is basically useful in the same ways as sync(s). I generally sync(s), umount(u), then reboot(b) when my system locks. It’s saved me many a fsck. Again, the unmount (remount read-only) hasn’t taken place until you see the “OK” and “Done” message appear on the screen.

The loglevels 0-9 are useful when your console is being flooded with kernel messages you do not want to see. Selecting 0 will prevent all but the most urgent kernel messages from reaching your console. (They will still be logged if syslogd/klogd are alive, though.)

term(e) and kill(i) are useful if you have some sort of runaway process you are unable to kill any other way, especially if it’s spawning other processes.

“just thaw it(j)” is useful if your system becomes unresponsive due to a frozen (probably root) filesystem via the FIFREEZE ioctl.
Sometimes SysRq seems to get ‘stuck’ after using it, what can I do?

That happens to me, also. I’ve found that tapping shift, alt, and control on both sides of the keyboard, and hitting an invalid sysrq sequence again will fix the problem. (i.e., something like alt-sysrq-z). Switching to another virtual console (ALT+Fn) and then back again should also help.
I hit SysRq, but nothing seems to happen, what’s wrong?

There are some keyboards that produce a different keycode for SysRq than the pre-defined value of 99 (see KEY_SYSRQ in include/uapi/linux/input-event-codes.h), or which don’t have a SysRq key at all. In these cases, run showkey -s to find an appropriate scancode sequence, and use setkeycodes <sequence> 99 to map this sequence to the usual SysRq code (e.g., setkeycodes e05b 99). It’s probably best to put this command in a boot script. Oh, and by the way, you exit showkey by not typing anything for ten seconds.
I want to add SysRQ key events to a module, how does it work?

In order to register a basic function with the table, you must first include the header include/linux/sysrq.h, this will define everything else you need. Next, you must create a sysrq_key_op struct, and populate it with A) the key handler function you will use, B) a help_msg string, that will print when SysRQ prints help, and C) an action_msg string, that will print right before your handler is called. Your handler must conform to the prototype in ‘sysrq.h’.

After the sysrq_key_op is created, you can call the kernel function register_sysrq_key(int key, struct sysrq_key_op *op_p); this will register the operation pointed to by op_p at table key ‘key’, if that slot in the table is blank. At module unload time, you must call the function unregister_sysrq_key(int key, struct sysrq_key_op *op_p), which will remove the key op pointed to by ‘op_p’ from the key ‘key’, if and only if it is currently registered in that slot. This is in case the slot has been overwritten since you registered it.

The Magic SysRQ system works by registering key operations against a key op lookup table, which is defined in ‘drivers/tty/sysrq.c’. This key table has a number of operations registered into it at compile time, but is mutable, and 2 functions are exported for interface to it:

register_sysrq_key and unregister_sysrq_key.

Of course, never ever leave an invalid pointer in the table. I.e., when your module that called register_sysrq_key() exits, it must call unregister_sysrq_key() to clean up the sysrq key table entry that it used. Null pointers in the table are always safe. :)

If for some reason you feel the need to call the handle_sysrq function from within a function called by handle_sysrq, you must be aware that you are in a lock (you are also in an interrupt handler, which means don’t sleep!), so you must call __handle_sysrq_nolock instead.
When I hit a SysRq key combination only the header appears on the console?

Sysrq output is subject to the same console loglevel control as all other console output. This means that if the kernel was booted ‘quiet’ as is common on distro kernels the output may not appear on the actual console, even though it will appear in the dmesg buffer, and be accessible via the dmesg command and to the consumers of /proc/kmsg. As a specific exception the header line from the sysrq command is passed to all console consumers as if the current loglevel was maximum. If only the header is emitted it is almost certain that the kernel loglevel is too low. Should you require the output on the console channel then you will need to temporarily up the console loglevel using alt-sysrq-8 or:

echo 8 > /proc/sysrq-trigger

Remember to return the loglevel to normal after triggering the sysrq command you are interested in.
I have more questions, who can I ask?

Just ask them on the linux-kernel mailing list:
    [email protected]

Credits

Written by Mydraal <[email protected]> Updated by Adam Sulmicki <[email protected]> Updated by Jeremy M. Dolan <[email protected]> 2001/01/28 10:15:59 Added to by Crutcher Dunnavant <[email protected]>

funny story, brave failed an update and I can't use it.
I have to use librewolf now and that fixed it. No more crashes or hangs. It seems like having brave open caused EVERYTHING.

your error message SAID that.  Seeing is believing..

trve lol, I didn't think brave could cause all of this but it did.

nvm, it started again, l4d2 (vulkan) keeps crashing after a bit and steam too right before it. Seems like mesa is really broken and brave was just really affected.

Great, just great. Now discord can't even launch and steam crashes for no reason. I have made no changes to the system since post 54  other than installing ncdu and gotop (no dependencies).

A bit of great news, is that we're seeing a pattern here. Unconfirmed, but a pattern regardless. Discord and Brave are Chromium based programs.

Steam is also based off of Chromium, but since you've tried my solution before. I gotta know, do you still have HA (hardware acceleration) disabled off of Steam?

I searched the net and says you can disable HA on Brave, but I'm not sure on Discord. I would recommend using Firefox-based browsers to login to Discord for now.

It didn't work, I'll try it again, also I tried running tf2 and it crashed kwin, l4d2 also crashes after a while. I'm at my wit's end here, I'm just done with this stupid problem. It keeps disappearing and reappearing with no clear pattern other than the mesa developers being mentally challenged

nevermind, it seems that rebooting sort of fixed it, now discord can launch and steam hasn't crashed (so far). I haven't played a youtube video yet though.

still on that same boot, I left it to idle as I was busy with IRL stuff. Librewolf hangs it every now and again but it doesn't completely freeze the system like brave. Steam and discord still haven't crashed. No segfaults in dmesg, the hangs might be from webGL being disabled in librewolf but that's just speculation. I'll test webGL later.

I played tf2, steam crashed midway through. No hangs or freezes.

I thought you already pinned the problem and now seem to be playing wack the mole instead of addressing it.  It seems there is a problem with hardware graphic acceleration - probably Mesa in various 3rd party browsers.

I thought so too, but it seems I didn't.

kernel panic minutes after boot (I updated mesa and vulkan-radeon) I was watching a youtube video and trying to start steam but it kept crashing. Discord also started crashing whenever I'd type something.
https://files.catbox.moe/fl1vab.jpeg
https://files.catbox.moe/tvp3x2.jpeg

If there is a software/ Mesa issue kernel should not panic. At most, kernel should reset the GPU if software has locked it up -- which could crash your entire graphical session, but should not crash the kernel.

If the panic is related to amdgpu driver, please report at https://gitlab.freedesktop.org/drm/amd/-/issues/ -- that is where AMDGPU issues are tracked.

that's what I thought, I don't know what the error message on the BSOD means though. I was using 6.15.2 zen which didn't panic before today's mesa update.

Been running the vanilla artix kernel (6.15.2) with the updated drivers for ~2 hours now, no issues whatsoever. Everything just werks.
Edit: steam just crashed but gracefully, it managed to restart with no issue.

[  581.960542] traps: steamwebhelper[10165] general protection fault ip:7f7c669ae026 sp:7ffce2183640 error:0 in libcef.so[a1ad026,7f7c5ebed000+a36d000]
This makes no sense. I'm on the same software versions from yesterday, same kernel, same everything (I installed kde connect yesterday but everything was fine) and now the segfaults and restarts are back. No GPU driver crashes and restarts, only discord and steam.
I should also mention that throughout yesterday, steam got more and more unstable. With it frequently opening windows to random things like steam support and stuff like that. Also mousing over to discord makes it restart. I'll try using LTS and I'll see what happens if I reboot.
Here's a recap of everything since yesterday.
1. I fixed the issue by updating the drivers
2. Steam was acting up but it was tolerable. It seemed to get worse as the day progressed though, at first it was nothing, then a random crash with a succesful restart and then constant pop ups whenever I'd mouse over it.
3. I installed KDE connect
4. I went to sleep and woke up
5. I tried installing a theme but it broke kwin, I ended up undoing everything. Uninstalled and downgraded packages, reinstalled my previous themes etc
I should be back at step 3 after undoing everything but I'm not. I can provide the pacman log if needed.
On LTS right now, testing using gmod, seems fine so far but frankly I don't have high hopes. And as soon I edited that in, steam crashed, restarted and popped up 3 windows, 'steam needs to update its audio driver` `about steam` and `system information` And steam just crashed. It seems that it does manage to restart but only to the task bar, it throws that libcef error if I try to restart the webhelper as well.
well at least I found this: https://gitlab.freedesktop.org/drm/amd/-/issues/4293
seems like LTS kernel was causing my issues. I used vanilla and it was fine until I opened steam chat, then it instantly crashed kwin.

There's also the Zen kernel if you're interested.

Can post full hardware specs?

sure, how do you want me to dump that info?
I also used zen and it kernel panicked almost immediately, I've updated KDE from 6.3.5 to 6.4 now it's the reverse, vanilla panics and zen is fine.

A fastfetch prompt would suffice. I'm curious why this is happening.

It turned out to be a ram issue. I reseated it and that fixed it.
https://files.catbox.moe/h7h11q.jpg

That's great, but also fingers crossed.  :D

UPDATED: Disregard as the reseating of RAM corrected.

TLDR -

... and if already spoken to, disregard.

Pipewire - are you using

/usr/bin/pipewire & /usr/bin/pipewire-pulse & /usr/bin/wireplumber &

I have nearly the same setup (albeit a Ryzen 7) and I have the above line in my .dwm/autostart.sh