AMD eGPU over Thunderbolt: crashing like there's no tomorrow

Aqualung · 2026-01-20 19:25:17

I have been agonizing hands-on over this issue for at least a week, day in and day out: how to make my new RX 9060 XT work as an eGPU over Thunderbolt. I have been using Copilot/Claude 4.5 quite extensively in my debugging efforts. Claude's conclusion is that it is hopeless, at least at this point in time, to attempt to run this AMD GPU over Thunderbolt. I have been getting catastrophic crashes, that prompt me to do hard reboots to get my system up and running. On the other hand, my ARC B580 works fine, no crashes, very well behaved under the same circumstances(!)--albeit being severely underpowered. Someone told me that I should look for GPUs that are capable to work without ReBAR, so here I am buying an AMD GPU, which, presumably, works better than the ARC in the absence of ReBAR. Some of the saga has been documented here.

Here's my eGPU setup:

LGGram (TB4) -> Caldigit TS5+ -> Razer Core X V2 -> ARC B580 or RX 9060 XT eGPU -> Acer SA242Y HBI monitor (60Hz, 1920x1080)

LGGram (TB4) -> Caldigit TS5+ -> Sabrent SB-TB4K -> 2xSamsung 4K monitors (60Hz, 3840x2160)

OS: ArchLinux

All connection cables are certified TB5.

My GRUB parameters look like this:

loglevel=3 quiet pci=realloc,hpiosize=512K,hpmemsize=1G,big_root_window pcie_gen_cap=0x40000 runpm=0 noretry=0 aspm=0

I have both ReBAR and "Above 4G Decoding" enabled in BIOS by default.

Here are the BIOS parameters that I have messed with--everything else is default:

ACPI Settings -> ACPI Auto Configuration = Enabled
Connectivity Configuration -> Preboot BLE = Enabled
System Agent (SA) Configuration -> Graphics Configuration -> Aperture Size = 1024
System Agent (SA) Configuration -> Graphics Configuration -> Intel Ultrabook Event Support -> IUER Dock Enable = Enabled
Platform Settings -> VTIO -> Enable VTIO Support = Enabled
Platform Settings -> TCSS Platform Setting -> Thunderbolt Configuration -> OS Native Resource Balance = Enabled
Platform Settings -> TCSS Platform Setting -> Thunderbolt Configuration -> Integrated Thunderbolt Configuration -> ITBT Root Port 1 Configuration -> Reserved PMemory = 4096
Platform Settings -> TCSS Platform Setting -> Thunderbolt Configuration -> Integrated Thunderbolt Configuration -> ITBT Root Port 1 Configuration -> PMemory Alignment = 31
Platform Settings -> TCSS Platform Setting -> Thunderbolt Configuration -> Integrated Thunderbolt Configuration -> ITBT Root Port 2 Configuration -> Reserved PMemory = 4096
Platform Settings -> TCSS Platform Setting -> Thunderbolt Configuration -> Integrated Thunderbolt Configuration -> ITBT Root Port 2 Configuration -> PMemory Alignment = 31

What am I doing wrong?

Last edited by Aqualung (2026-01-24 22:14:23)

Aqualung · 2026-01-20 20:07:56

As promised, here is lspci -k (will attach journalctl -b to a subsequent reply):

00:00.0 Host bridge: Intel Corporation Raptor Lake-P/U 4p+8e cores Host Bridge/DRAM Controller
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: igen6_edac
	Kernel modules: igen6_edac
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: i915
	Kernel modules: i915, xe
00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: proc_thermal_pci
	Kernel modules: processor_thermal_device_pci
00:06.0 PCI bridge: Intel Corporation Raptor Lake PCI Express 4.0 Graphics Port
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #2
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:07.3 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #1
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module
	Subsystem: LG Electronics, Inc. Device 0513
00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: intel_vsec
	Kernel modules: intel_vsec
00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01)
	Subsystem: Intel Corporation Device 0094
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi, wl
00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: sof-audio-pci-intel-tgl
	Kernel modules: snd_soc_avs, snd_sof_pci_intel_tgl, snd_hda_intel
00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
	Subsystem: LG Electronics, Inc. Device 0513
	Kernel driver in use: intel-spi
	Kernel modules: spi_intel_pci
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less) (rev 02)
	Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less)
	Kernel driver in use: nvme
	Kernel modules: nvme
2c:00.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
2d:00.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
2d:01.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
2d:02.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
2d:03.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
2d:04.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
2e:00.0 USB controller: ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host Controller
	Subsystem: CalDigit, Inc. Device 3144
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
2f:00.0 Ethernet controller: Aquantia Corp. AQtion AQC113 NBase-T/IEEE 802.3an Ethernet Controller [Antigua 10G] (rev 03)
	Subsystem: CalDigit, Inc. Device 0173
	Kernel driver in use: atlantic
	Kernel modules: atlantic
30:00.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
31:00.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
31:01.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
31:02.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
31:03.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
	Subsystem: Device 2222:1111
	Kernel driver in use: pcieport
	Kernel modules: shpchp
32:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev 25)
	Subsystem: Tul Corporation / PowerColor Device 1478
	Kernel driver in use: pcieport
	Kernel modules: shpchp
33:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch (rev 25)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
	Kernel driver in use: pcieport
	Kernel modules: shpchp
34:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0)
	Subsystem: Tul Corporation / PowerColor Device 2437
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu
34:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 HDMI/DP Audio Controller
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 HDMI/DP Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
3d:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
	Subsystem: Intel Corporation Device 0000
	Kernel driver in use: pcieport
	Kernel modules: shpchp
3e:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
	Subsystem: Intel Corporation Device 0000
	Kernel driver in use: pcieport
	Kernel modules: shpchp
3e:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
	Subsystem: Intel Corporation Device 0000
	Kernel driver in use: pcieport
	Kernel modules: shpchp
3e:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
	Subsystem: Intel Corporation Device 0000
	Kernel driver in use: pcieport
	Kernel modules: shpchp
3e:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
	Subsystem: Intel Corporation Device 0000
	Kernel driver in use: pcieport
	Kernel modules: shpchp
3e:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
	Subsystem: Intel Corporation Device 0000
	Kernel driver in use: pcieport
	Kernel modules: shpchp

Aqualung · 2026-01-20 20:31:12

And here's the journalctl -b: full.log.

Also, here's my mpv.conf, as the crash occurs during mpv playback:

# Copy to ~/.config/mpv to enable Vulkan hardware acceleration in mpv.
hwdec=vulkan # Enables hardware-accelerated video decoding via Vulkan.
vo=gpu-next # Use gpu-next for video output (required by Vulkan).
gpu-api=vulkan # Forces Vulkan for rendering.
gpu-context=waylandvk # For Wayland with Vulkan.
hwdec-codecs=all # Enables hardware decoding for all supported codecs.
# vulkan-device='Intel(R) Arc(tm) B580 Graphics (BMG G21)'
vulkan-device='AMD Radeon RX 9060 XT (RADV GFX1200)'
slang=eng # Sets the subtitle language to English.

Noted that the amdgpu driver crashes with hwdec=no as well.

Last edited by Aqualung (2026-01-20 20:48:48)

seth · 2026-01-22 15:20:22

runpm=0 noretry=0 aspm=0

This is not in the journal but also nonsense - you need to hint the module for the parameters - "amdgpu.runpm=0" etc.

works better than the ARC in the absence of ReBAR … I have both ReBAR and "Above 4G Decoding" enabled in BIOS by default.

???
Does the PCI setup look different when you toggle rebar support, notably wrt

Jan 20 14:54:33 DadsGram kernel: pcieport 0000:00:07.3: bridge window [io  size 0x431000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:00:07.3: bridge window [io  size 0x431000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:00:07.3: bridge window [io  size 0x380000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:00:07.3: bridge window [io  size 0x380000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2c:00.0: bridge window [io  size 0x380000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2c:00.0: bridge window [io  size 0x380000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2c:00.0: bridge window [io  size 0x380000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2c:00.0: bridge window [io  size 0x380000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:01.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:01.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:02.0: bridge window [io  size 0x128000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:02.0: bridge window [io  size 0x128000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:03.0: bridge window [io  size 0x12c000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:03.0: bridge window [io  size 0x12c000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:04.0: bridge window [io  size 0x128000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:04.0: bridge window [io  size 0x128000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:01.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:01.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:02.0: bridge window [io  size 0x128000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:02.0: bridge window [io  size 0x128000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:03.0: bridge window [io  size 0x12c000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:03.0: bridge window [io  size 0x12c000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:04.0: bridge window [io  size 0x128000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:2d:04.0: bridge window [io  size 0x128000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:30:00.0: bridge window [io  size 0x128000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:30:00.0: bridge window [io  size 0x128000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:30:00.0: bridge window [io  size 0x128000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:30:00.0: bridge window [io  size 0x128000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [mem size 0x400200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [mem size 0x400200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:01.0: bridge window [io  size 0x62000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:01.0: bridge window [io  size 0x62000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:02.0: bridge window [io  size 0x62000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:02.0: bridge window [io  size 0x62000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:03.0: bridge window [io  size 0x62000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:03.0: bridge window [io  size 0x62000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [mem size 0x400200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [mem size 0x400200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:01.0: bridge window [io  size 0x62000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:01.0: bridge window [io  size 0x62000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:02.0: bridge window [io  size 0x62000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:02.0: bridge window [io  size 0x62000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:03.0: bridge window [io  size 0x62000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:31:03.0: bridge window [io  size 0x62000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [mem size 0x400200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [mem size 0x400200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [mem size 0x400200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [mem size 0x400200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:32:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [mem size 0x400200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [mem size 0x400200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [mem size 0x400200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [mem size 0x400200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:33:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 0 [mem size 0x400000000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 0 [mem size 0x400000000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 2 [mem size 0x00200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 2 [mem size 0x00200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 0 [mem size 0x400000000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 0 [mem size 0x400000000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 2 [mem size 0x00200000 64bit pref]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: amdgpu 0000:34:00.0: BAR 2 [mem size 0x00200000 64bit pref]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3d:00.0: bridge window [io  size 0x12c000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3d:00.0: bridge window [io  size 0x12c000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3d:00.0: bridge window [io  size 0x12c000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3d:00.0: bridge window [io  size 0x12c000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:01.0: bridge window [io  size 0x63000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:01.0: bridge window [io  size 0x63000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:02.0: bridge window [io  size 0x63000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:02.0: bridge window [io  size 0x63000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:03.0: bridge window [io  size 0x63000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:03.0: bridge window [io  size 0x63000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:04.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:04.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:00.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:00.0: bridge window [io  size 0x1000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:01.0: bridge window [io  size 0x63000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:01.0: bridge window [io  size 0x63000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:02.0: bridge window [io  size 0x63000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:02.0: bridge window [io  size 0x63000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:03.0: bridge window [io  size 0x63000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:03.0: bridge window [io  size 0x63000]: failed to assign
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:04.0: bridge window [io  size 0x1000]: can't assign; no space
Jan 20 14:54:33 DadsGram kernel: pcieport 0000:3e:04.0: bridge window [io  size 0x1000]: failed to assign

Jan 20 14:54:34 DadsGram gnome-shell[3024]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Dumping IP State
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card0/device/devcoredump/data
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: ring vcn_unified_0 timeout, signaled seq=1284, emitted seq=1285
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu:  Process mpv pid 195158 thread av:h264:df1 pid 195185
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Starting vcn_unified_0 ring reset
Jan 20 14:57:48 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to load ucode VCN0_RAM(0x3B) 
Jan 20 14:57:48 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x0)
Jan 20 14:57:48 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: vcn_v5_0_0_start_dpg_mode: vcn sram load failed -22
Jan 20 14:57:48 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Ring vcn_unified_0 reset failed
Jan 20 14:57:48 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: GPU reset begin!. Source:  1
Jan 20 14:57:48 DadsGram kernel: amdgpu 0000:34:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 20 14:57:51 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
Jan 20 14:57:51 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to unmap legacy queue
Jan 20 14:57:53 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
Jan 20 14:57:53 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to unmap legacy queue
Jan 20 14:57:55 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
Jan 20 14:57:55 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to unmap legacy queue
Jan 20 14:57:57 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
Jan 20 14:57:57 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to unmap legacy queue
Jan 20 14:57:59 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
Jan 20 14:57:59 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to unmap legacy queue
Jan 20 14:58:01 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
Jan 20 14:58:01 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to unmap legacy queue
Jan 20 14:58:03 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x0)
Jan 20 14:58:03 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Failed to terminate hdcp ta
Jan 20 14:58:03 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: suspend of IP block <psp> failed -22
Jan 20 14:58:03 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: MODE1 reset
Jan 20 14:58:03 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: GPU mode1 reset
Jan 20 14:58:03 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: GPU smu mode1 reset
Jan 20 14:58:04 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: GPU reset succeeded, trying to resume
Jan 20 14:58:04 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: PCIE GART of 512M enabled (table at 0x0000008000000000).
Jan 20 14:58:04 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: VRAM is lost due to GPU reset!
Jan 20 14:58:04 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: PSP is resuming...
Jan 20 14:58:05 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: psp reg (0x16091) wait timed out, mask: 0, read: 0 exp: 0
Jan 20 14:58:05 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: PSP load sos failed!
Jan 20 14:58:05 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: PSP resume failed
Jan 20 14:58:05 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: resume of IP block <psp> failed -62
Jan 20 14:58:05 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: GPU reset end with ret = -62
Jan 20 14:58:05 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: GPU Recovery Failed: -62
Jan 20 14:58:15 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Dumping IP State
Jan 20 14:58:15 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
Jan 20 14:58:15 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Jan 20 14:58:15 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card0/device/devcoredump/data
Jan 20 14:58:15 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: ring vcn_unified_0 timeout, signaled seq=1285, emitted seq=1285
Jan 20 14:58:15 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Starting vcn_unified_0 ring reset
Jan 20 14:58:17 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: failed to load ucode VCN0_RAM(0x3B) 
Jan 20 14:58:17 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: psp gfx command UNLOAD_TA(0x2) failed and response status is (0x0)
Jan 20 14:58:17 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: vcn_v5_0_0_start_dpg_mode: vcn sram load failed -22
Jan 20 14:58:17 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Ring vcn_unified_0 reset failed
Jan 20 14:58:17 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: GPU reset begin!. Source:  1

Not sure whether

Jan 20 14:56:33 DadsGram org.gnome.Nautilus[195024]: Connecting to org.freedesktop.Tracker3.Miner.Files
Jan 20 14:56:33 DadsGram nautilus[195024]: WARNING: radv is not a conformant Vulkan implementation, testing use only.
Jan 20 14:56:33 DadsGram nautilus[195024]: MESA-INTEL: warning: ../mesa-25.3.3/src/intel/vulkan/anv_formats.c:993: FINISHME: support more multi-planar formats with DRM modifiers
Jan 20 14:56:33 DadsGram nautilus[195024]: MESA-INTEL: warning: ../mesa-25.3.3/src/intel/vulkan/anv_formats.c:959: FINISHME: support YUV colorspace with DRM format modifiers

means that you're trying to use radv w/ the intel IGP

Aqualung · 2026-01-22 15:52:27

seth wrote:

runpm=0 noretry=0 aspm=0
This is not in the journal but also nonsense - you need to hint the module for the parameters - "amdgpu.runpm=0" etc.

The four parameters (pcie_gen_cap=0x40000, runpm=0, noretry=0, aspm=0) are actually specified in an amd-pcie-fix.conf file in /etc/modprobe.d, which looks like this:

options amdgpu pcie_gen_cap=0x40000 runpm=0 noretry=0 aspm=0

works better than the ARC in the absence of ReBAR … I have both ReBAR and "Above 4G Decoding" enabled in BIOS by default.
???

The statement "works better then the ARC in the absence of ReBAR" is a just general statement. Surely enough, I tried running the AMD eGPU in both scenarios (i.e. ReBAR enabled and disabled), with the same results. Both scenarios crashed.

Does the PCI setup look different when you toggle rebar support, notably wrt ...

I have not yet captured a log in the no ReBAR scenario, but I will, and I will post it in a subsequent comment. Btw, when disabling ReBAR in BIOS, should I also disable "Above 4G Decoding"? (Or is that something that gets disabled automatically when disabling ReBAR?)

Not sure whether

Jan 20 14:56:33 DadsGram org.gnome.Nautilus[195024]: Connecting to org.freedesktop.Tracker3.Miner.Files
Jan 20 14:56:33 DadsGram nautilus[195024]: WARNING: radv is not a conformant Vulkan implementation, testing use only.
Jan 20 14:56:33 DadsGram nautilus[195024]: MESA-INTEL: warning: ../mesa-25.3.3/src/intel/vulkan/anv_formats.c:993: FINISHME: support more multi-planar formats with DRM modifiers
Jan 20 14:56:33 DadsGram nautilus[195024]: MESA-INTEL: warning: ../mesa-25.3.3/src/intel/vulkan/anv_formats.c:959: FINISHME: support YUV colorspace with DRM format modifiers

means that you're trying to use radv w/ the intel IGP

All I can tell you is that all the logs that I posted, and all the code above, pertain to the AMD eGPU use scenario. I have not posted any logs pertaining to the use of the ARC eGPU. Not sure what makes you think that I am trying to use redv with the Intel eGPU. How did you infer that?

Last edited by Aqualung (2026-01-22 17:55:52)

seth · 2026-01-22 20:11:31

Or is that something that gets disabled automatically when disabling ReBAR?

Idk what your BIOS does but those aren't strictly linked.

How did you infer that?

I'd assume that the system runs on the IGP (hence the explicit mpv config and limited crash triggers) and nautilus is posting messages from MESA-INTEL but also complains about radv (which might just because no vulkan driver is explicitly selected by exporting VK_DRIVER_FILES)
https://wiki.archlinux.org/title/Vulkan

Sidebar (well, main topic, actually)

as the crash occurs during mpv playback

"during" or "when"? Ie. can you play the video fine for a moment or does it crash right away?

Aqualung · 2026-01-22 20:40:23

seth wrote:

How did you infer that?
I'd assume that the system runs on the IGP (hence the explicit mpv config and limited crash triggers) and nautilus is posting messages from MESA-INTEL but also complains about radv (which might just because no vulkan driver is explicitly selected by exporting VK_DRIVER_FILES)
https://wiki.archlinux.org/title/Vulkan

The main system GPU is, indeed, the Iris Xe iGPU, though I choose to do mpv playback using the eGPU. So yes, that is why you see messages pertaining to both GPUs in the log.

as the crash occurs during mpv playback
"during" or "when"? Ie. can you play the video fine for a moment or does it crash right away?

Yes, video playback proceeds smoothly for a few good minutes, and everything looks peachy, with barely any stress of the eGPU ... that is, until the amdgpu driver crashes, and video freezes. Audio playback continues undisturbed until I kill off mpv. If I remember correctly, I have to disconnect the eGPU in order to be able to kill mpv. Even so, the amdgpu driver remains hung such that, in order to do a shutdown I have to actually use the laptop shutdown button, as soft shutdowns get stuck.

Last edited by Aqualung (2026-01-22 20:46:37)

seth · 2026-01-23 15:04:51

https://wiki.archlinux.org/title/Thunde … cing_power ?

Aqualung · 2026-01-23 16:25:27

seth wrote:

https://wiki.archlinux.org/title/Thunde … cing_power ?

Thank you, but I am not sure what exactly I am supposed to focus on on that page. Is this a suggestion to add the pci=hpbussize=0x33 parameter to grub by any chance? Or is there something else?

seth · 2026-01-23 16:29:37

The link goes to the paragraph about "Forcing power", the idea being that the TB links shuts down to save power, not understanding that the eGPU behind it is currently in use.
nb. that the UUID "86CCFD48-205E-4A77-9C48-2021CBEDE341" there is a placeholder and will rather be different on your system.

You could also try to add "thunderbolt.clx=0" to the https://wiki.archlinux.org/title/Kernel_parameters (see "modinfo thunderbolt")

Aqualung · 2026-01-23 19:14:56

Here's what Copilot/Claude suggests I send to ... whomever may be interested in this sort of crashes (AMD, Mesa etc.):

Perfect! Here are the key AMD GPU crash messages from this log (Jan 23, 13:55:26 onwards):

Critical Error Sequence to send to manufacturer:

Jan 23 13:55:26 - ring sdma1 timeout, signaled seq=1589, emitted seq=1591
Jan 23 13:55:26 - Starting sdma1 ring resetJan 23 13:55:26 - *ERROR* ring sdma1 test failed (-110)
Jan 23 13:55:26 - Ring sdma1 reset failed
Jan 23 13:55:27 - *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataJan 23 13:55:29-39 - MES(1) failed to respond to msg=REMOVE_QUEUE (repeated 6 times)
Jan 23 13:55:42 - psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x0)
Jan 23 13:55:42 - Failed to terminate hdcp taJan 23 13:55:42 - suspend of IP block <psp> failed -22
Jan 23 13:55:43 - Timeout waiting for VM flush ACK!
Jan 23 13:55:45 - psp gfx command UNKNOWN CMD(0x0) failed and response status is (0x0)
Jan 23 13:55:45 - Failed to load tocJan 23 13:55:45 - PSP tmr init failed!
Jan 23 13:55:45 - PSP resume failed
Jan 23 13:55:45 - resume of IP block <psp> failed -22
Jan 23 13:55:45 - GPU Recovery Failed: -22

Summary for manufacturer:

SDMA1 (DMA engine) timeouts and reset failures
MES (Micro Engine Scheduler) unresponsive
PSP (Platform Security Processor) recovery failures
GPU recovery fails completely over Thunderbolt 4 connection
Occurs regardless of ReBAR on/off, with/without video decode
Network: Linux 6.18.6-zen1, eGPU via Thunderbolt 4 → CalDigit TS5+ → Razer Core X V2

seth · 2026-01-23 19:42:59

Stop wasting your time with these bullshit generators, the only thing AMD *might* be interested in in the firmware dump:

Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Dumping IP State
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Jan 20 14:57:46 DadsGram kernel: amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card0/device/devcoredump/data

Did you attempt to prevent the thunderbolt powersaving?

Aqualung · 2026-01-23 20:04:59

seth wrote:

Did you attempt to prevent the thunderbolt powersaving?

I did add the thunderbolt.clx=0 parameter to grub, and it still didn't fix the crash. In order to try out the other suggestion, I would need the uuid of the Thunderbolt port: how do I figure that out?

Last edited by Aqualung (2026-01-23 20:09:00)

seth · 2026-01-23 20:36:42

ls /sys/bus/wmi/devices/*/force_power

Aqualung · 2026-01-23 22:30:16

seth wrote:

ls /sys/bus/wmi/devices/*/force_power

Thank you. Tried thunderbolt powersaving, and it didn't work. (Also note, as I said above, that no such crashes happen with my ARC B580 eGPU, which makes me think that the crash doesn't happen due to Thunderbolt's shutdown to save power.)

Anyway, I have posted here a short film of the crash, for whomever wants to see with their own eyes what it looks like. Just be patient and watch it all. You may want to download it locally.

Finally, huge thanks for all your help and advice!

Last edited by Aqualung (2026-01-23 22:30:58)

seth · 2026-01-24 15:39:17

Well, at least the cause is obvious - it's clearly stunned by Ganz' performance…

nb. that frequency and power draw freeze - those values are unreliable because the GPU no longer responds.
Is the delay somewhat deterministic or can you sometime play 15s and then 10 mins ?
Can you trigger this by running glxgears or some xscreensaver hack or vkcube or a unigine demo on the GPU?

Aqualung · 2026-01-24 17:35:56

seth wrote:

Is the delay somewhat deterministic or can you sometime play 15s and then 10 mins ?

No, not deterministic. Not as far as I could tell. As a matter of fact, what you see there is actually quite a long delay: usually the crash happens a lot earlier.

Can you trigger this by running glxgears or some xscreensaver hack or vkcube or a unigine demo on the GPU?

I'll look into it. As far as I can tell, no crash happens if the AMD eGPU is kept idle. Otherwise, displaying image on a monitor connected to the eGPU or doing video playback on the eGPU trigger crashes.

Aqualung · 2026-01-25 21:59:25

Just for the heck of it, I tried bypassing the TS5+, hence I connected the eGPU directly to the laptop's other TB4 port. I got the same crash. At this point, I am set on returning the current 9060XT GPU (a PowerColor), and I bought another one from ASUS this time. Will report back if that one crashes once I get it.

Aqualung · 2026-02-02 02:28:54

Just reporting back, I got the same type of crash with my new ASUS-branded RX 9060 XT eGPU; as such, it appears to be an issue with all 9060 amdgpu drivers.

MarPop · 2026-02-02 17:13:28

The problem lies in power states handling of the gpu. Could be AMD didn't disclose enough information - to linux ecosystem - on how to handle power saving dynamics (they say it's stable on windows). A nightmare that was resolved yesterday. I have a gb-BRR7H-4800 with Ryzen 7 4800u, and it used to block, crash, and all the rest described in your comments. Yesterday I disabled PSS Support BIOS option, and now everything runs smoothly and fast, though I cannot disable boost and/or use cpupower to regulate frequencies or policies (disabling PSS, ACPI is not exposed to the kernel). Now I have sway session and KDE session opened, and have tried all the sites where it used to crash.
Sorry, but I just registered here for the sake of letting you know how it has been solved here - to fix yours, at least temporarily, and to let know those in charge.

Aqualung · 2026-02-02 17:33:02

MarPop wrote:

The problem lies in power states handling of the gpu. Could be AMD didn't disclose enough information - to linux ecosystem - on how to handle power saving dynamics (they say it's stable on windows). A nightmare that was resolved yesterday. I have a gb-BRR7H-4800 with Ryzen 7 4800u, and it used to block, crash, and all the rest described in your comments. Yesterday I disabled PSS Support BIOS option, and now everything runs smoothly and fast, though I cannot disable boost and/or use cpupower to regulate frequencies or policies (disabling PSS, ACPI is not exposed to the kernel). Now I have sway session and KDE session opened, and have tried all the sites where it used to crash.
Sorry, but I just registered here for the sake of letting you know how it has been solved here - to fix yours, at least temporarily, and to let know those in charge.

Thank you. Will look for that in my BIOS. Just FYI, my system is Intel, and I am being told that this "PSS Support" is usually a setting in AMD BIOSes.

At any rate, at this point in time my hope is that kernel 6.19 will straighten out the ReBAR morass, which I am also told is the root of my crashes.

seth · 2026-02-02 23:08:08

https://bbs.archlinux.org/viewtopic.php … 5#p2285745
He's crossposting that as generic PSA and I doubt MarPop is even using an eGPU.

my ARC B580 works fine, no crashes, very well behaved under the same circumstances(!)--albeit being severely underpowered

I'd test the HW w/ windows (if you can/don't mind) just to make sure the TB actually provides enough power for the GPU or you could also try whether running the AMD GPU at the minimum power profile or performance level works…
https://wiki.archlinux.org/title/AMDGPU … nce_levels

Aqualung · 2026-02-03 04:43:52

seth wrote:

make sure the TB actually provides enough power for the GPU

As far as I know the B580 has more stringent power requirements than the 9060. AT any rate, my enclosure has an 850W PSU.

MarPop · 2026-02-04 01:51:02

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 5#p2285745
He's crossposting that as generic PSA and I doubt MarPop is even using an eGPU.

I posted there after having realized that I posted here by mistake, and I didn't remove it from here because I was thinking it can be useful anyway. And I mentioned this fact there. Though I wonder where from the need to point the obvious, seen that it could have been inferred from what I wrote.
I'll add — here and there — that the freezes manifests anyway after suspend. I am new here, so tell me if mine are useless.

potato035 · 2026-03-08 22:25:13

@Aqualung, did you find a fix for this? After a system update, my eGPU (RX 6700 XT on Intel 8th-gen TB3) started crashing during games. It dumps me back to Plasma without the eGPU, and I can't shut down or reboot without holding the power button. I'll add the log

Mar 09 01:40:14 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:14 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:14 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:14 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:15 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:15 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:15 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:15 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:15 archbtw kded6[1444]: Registering ":1.1346/StatusNotifierItem" to system tray
Mar 09 01:40:15 archbtw kded6[1444]: Service  ":1.1346" unregistered
Mar 09 01:40:15 archbtw kded6[1444]: Registering ":1.1347/StatusNotifierItem" to system tray
Mar 09 01:40:15 archbtw kded6[1444]: Service  ":1.1347" unregistered
Mar 09 01:40:15 archbtw kded6[1444]: Registering ":1.1349/StatusNotifierItem" to system tray
Mar 09 01:40:15 archbtw kded6[1444]: Service  ":1.1349" unregistered
Mar 09 01:40:15 archbtw kded6[1444]: Registering ":1.1350/StatusNotifierItem" to system tray
Mar 09 01:40:15 archbtw kded6[1444]: Service  ":1.1350" unregistered
Mar 09 01:40:16 archbtw steam[5264]: Fossilize INFO: Overriding serialization path: "/home/potato/.local/share/Steam/steamapps/shadercache/1203220/fozpipelinesv6/steamapprun_pipeline_cache".
Mar 09 01:40:16 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:16 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:16 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:16 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:16 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:16 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:16 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:06:01.0
Mar 09 01:40:17 archbtw kernel: pcieport 0000:06:01.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Mar 09 01:40:17 archbtw kernel: pcieport 0000:06:01.0:   device [8086:15ef] error status/mask=00001000/00002000
Mar 09 01:40:17 archbtw kernel: pcieport 0000:06:01.0:    [12] Timeout               
Mar 09 01:40:17 archbtw steam[5264]: 03/09 01:40:17 minidumps folder is set to /tmp/dumps
Mar 09 01:40:17 archbtw steam[5264]: 03/09 01:40:17 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20260121171226)/tid(13554)
Mar 09 01:40:17 archbtw steam[5264]: 03/09 01:40:17 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(13554)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:21 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:21 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:31 archbtw sunshine[2398]: [2026-03-09 01:40:31.953]: Warning: Couldn't discover any IPv4 UPNP devices
Mar 09 01:40:40 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:40 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:40 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:40 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:40 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:40 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:40 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:40 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:41 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:41 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:41 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:41 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:41 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:42 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:42 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:42 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:42 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:43 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:43 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:06:01.0
Mar 09 01:40:43 archbtw kernel: pcieport 0000:06:01.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:43 archbtw kernel: pcieport 0000:06:01.0:   device [8086:15ef] error status/mask=00000040/00002000
Mar 09 01:40:43 archbtw kernel: pcieport 0000:06:01.0:    [ 6] BadTLP                
Mar 09 01:40:43 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:43 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:43 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:45 archbtw kernel: aer_ratelimit: 5 callbacks suppressed
Mar 09 01:40:45 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:45 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:45 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:45 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:46 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:46 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:50 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:00:1c.4
Mar 09 01:40:50 archbtw kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Mar 09 01:40:50 archbtw kernel: pcieport 0000:00:1c.4:   device [8086:9dbc] error status/mask=00001000/00002000
Mar 09 01:40:50 archbtw kernel: pcieport 0000:00:1c.4:    [12] Timeout               
Mar 09 01:40:52 archbtw kernel: aer_ratelimit: 9 callbacks suppressed
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:52 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:52 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:57 archbtw kernel: aer_ratelimit: 7 callbacks suppressed
Mar 09 01:40:57 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:57 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:57 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:57 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:40:59 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:40:59 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:40:59 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:40:59 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:00 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:00 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:00 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:00 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:01 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:01 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:01 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:01 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:03 archbtw steam[5264]: [2026-03-09 01:41:03] Background update loop checking for update. . .
Mar 09 01:41:03 archbtw steam[5264]: [2026-03-09 01:41:03] Checking for available updates...
Mar 09 01:41:03 archbtw steam[5264]: [2026-03-09 01:41:03] Downloading manifest: https://client-update.fastly.steamstatic.com/steam_client_ubuntu12
Mar 09 01:41:03 archbtw steam[5264]: [2026-03-09 01:41:03] Manifest download: send request
Mar 09 01:41:03 archbtw steam[5264]: [2026-03-09 01:41:03] Manifest download: waiting for download to finish
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:04 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:04 archbtw steam[5264]: [2026-03-09 01:41:04] Manifest download: finished
Mar 09 01:41:04 archbtw steam[5264]: [2026-03-09 01:41:04] Download skipped by HTTP 304 Not Modified
Mar 09 01:41:04 archbtw steam[5264]: [2026-03-09 01:41:04] Nothing to do
Mar 09 01:41:10 archbtw kernel: aer_ratelimit: 33 callbacks suppressed
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:10 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:10 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:12 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:06:01.0
Mar 09 01:41:12 archbtw kernel: pcieport 0000:06:01.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:12 archbtw kernel: pcieport 0000:06:01.0:   device [8086:15ef] error status/mask=00000040/00002000
Mar 09 01:41:12 archbtw kernel: pcieport 0000:06:01.0:    [ 6] BadTLP                
Mar 09 01:41:17 archbtw kernel: aer_ratelimit: 344 callbacks suppressed
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:17 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:17 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: aer_ratelimit: 16 callbacks suppressed
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:22 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:22 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:27 archbtw kernel: aer_ratelimit: 194 callbacks suppressed
Mar 09 01:41:27 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:27 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:27 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:27 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:27 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:27 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:28 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:28 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:28 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:28 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:29 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:29 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:29 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:29 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:29 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:29 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:29 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:29 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:06:01.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:06:01.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:06:01.0:   device [8086:15ef] error status/mask=00000040/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:06:01.0:    [ 6] BadTLP                
Mar 09 01:41:32 archbtw kernel: aer_ratelimit: 283 callbacks suppressed
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:32 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:32 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:34 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:06:01.0
Mar 09 01:41:34 archbtw kernel: pcieport 0000:06:01.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:34 archbtw kernel: pcieport 0000:06:01.0:   device [8086:15ef] error status/mask=00000080/00002000
Mar 09 01:41:34 archbtw kernel: pcieport 0000:06:01.0:    [ 7] BadDLLP               
Mar 09 01:41:35 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:06:01.0
Mar 09 01:41:35 archbtw kernel: pcieport 0000:06:01.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:35 archbtw kernel: pcieport 0000:06:01.0:   device [8086:15ef] error status/mask=00000040/00002000
Mar 09 01:41:35 archbtw kernel: pcieport 0000:06:01.0:    [ 6] BadTLP                
Mar 09 01:41:37 archbtw kernel: aer_ratelimit: 1009 callbacks suppressed
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:37 archbtw kernel: pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:02:00.0
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:   device [8086:15c0] error status/mask=00000080/00002000
Mar 09 01:41:37 archbtw kernel: pcieport 0000:02:00.0:    [ 7] BadDLLP               
Mar 09 01:41:39 archbtw kernel: pcieport 0000:00:1c.4: DPC: containment event, status:0x1f05, ERR_FATAL received from 0000:06:01.0
Mar 09 01:41:39 archbtw kernel: pcieport 0000:03:00.0: Unable to change power state from D3hot to D0, device inaccessible
Mar 09 01:41:39 archbtw kernel: thunderbolt 0000:04:00.0: Unable to change power state from D3hot to D0, device inaccessible
Mar 09 01:41:39 archbtw kernel: ------------[ cut here ]------------
Mar 09 01:41:39 archbtw kernel: thunderbolt 0000:04:00.0: interrupt for TX ring 0 is already enabled
Mar 09 01:41:39 archbtw kernel: WARNING: CPU: 2 PID: 99 at drivers/thunderbolt/nhi.c:147 ring_interrupt_active+0x242/0x2d0 [thunderbolt]
Mar 09 01:41:39 archbtw kernel: Modules linked in: hid_playstation ff_memless led_class_multicolor rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device uinput xt_MASQUERADE xt_tcpudp xt_mark nft_reject_ipv4 act_csum cls_u32 sch_htb nf_nat_tftp nf_conntrack_tftp bridge stp llc tun ccm algif_aead des3_ede_x86_64 des_generic libdes md4 nft_masq nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security nf_tables ip6table_filter ip6_tables iptable_filter ip_tables x_tables cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_intelhdmi amdgpu snd_hda_codec_alc269 snd_hda_scodec_component snd_hda_codec_realtek_lib snd_hda_codec_generic ucsi_acpi typec_ucsi typec roles snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common intel_uncore_frequency
Mar 09 01:41:39 archbtw kernel:  intel_uncore_frequency_common snd_soc_hdac_hda intel_pmc_core_pltdrv snd_sof_intel_hda_mlink intel_pmc_core snd_sof_intel_hda pmt_telemetry soundwire_cadence pmt_discovery snd_sof_pci pmt_class snd_sof_xtensa_dsp intel_pmc_ssram_telemetry intel_vsec snd_sof intel_tcc_cooling snd_sof_utils x86_pkg_temp_thermal snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks intel_powerclamp soundwire_generic_allocation snd_soc_acpi coretemp soundwire_bus snd_soc_sdca kvm_intel processor_thermal_device_pci_legacy crc8 amdxcp vfat r8153_ecm processor_thermal_device cdc_ether drm_panel_backlight_quirks fat elan_i2c snd_soc_avs usbnet think_lmi iwlmvm intel_rapl_msr gpu_sched mei_hdcp snd_hda_codec_atihdmi mei_pxp processor_thermal_wt_hint snd_soc_hda_codec drm_exec i915 snd_hda_codec_hdmi kvm firmware_attributes_class platform_temperature_control drm_suballoc_helper snd_hda_intel snd_hda_ext_core mac80211 drm_buddy drm_ttm_helper processor_thermal_soc_slider intel_wmi_thunderbolt wmi_bmof irqbypass snd_hda_codec
Mar 09 01:41:39 archbtw kernel:  processor_thermal_rfim uvcvideo btusb polyval_clmulni videobuf2_vmalloc libarc4 btmtk ghash_clmulni_intel snd_hda_core uvc processor_thermal_rapl snd_soc_core aesni_intel intel_rapl_common snd_intel_dspcfg videobuf2_memops r8152 ttm btrtl iwlwifi snd_compress rapl btbcm i2c_algo_bit snd_ctl_led intel_cstate processor_thermal_wt_req mii e1000e i2c_i801 snd_intel_sdw_acpi drm_display_helper videobuf2_v4l2 spi_nor processor_thermal_power_floor btintel intel_uncore psmouse mei_me pcspkr libphy processor_thermal_mbox i2c_smbus ac97_bus snd_hwdep ptp mdio_bus mtd pps_core cec snd_pcm_dmaengine i2c_mux videobuf2_common thinkpad_acpi mei cfg80211 bluetooth platform_profile intel_soc_dts_iosf thunderbolt sparse_keymap intel_pch_thermal intel_gtt joydev int3403_thermal int340x_thermal_zone rfkill mousedev video pinctrl_cannonlake int3400_thermal acpi_thermal_rel wmi acpi_pad mac_hid snd_aloop snd_pcm v4l2loopback(OE) snd_timer videodev snd dm_mod mc pkcs8_key_parser uhid soundcore i2c_dev crypto_user ntsync
Mar 09 01:41:39 archbtw kernel:  nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress bpf_preload uas usb_storage mmc_block rpmb_core nvme sdhci_pci nvme_core sdhci_uhs2 sdhci nvme_keyring cqhci nvme_auth hkdf mmc_core serio_raw spi_intel_pci spi_intel
Mar 09 01:41:39 archbtw kernel: CPU: 2 UID: 0 PID: 99 Comm: irq/121-pcie-dp Tainted: G S   U     OE       6.18.16-1-lts #1 PREEMPT(voluntary)  674a1aec569c3e6c68f0032d072385577b88e9e1
Mar 09 01:41:39 archbtw kernel: Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Mar 09 01:41:39 archbtw kernel: Hardware name: LENOVO 20Q154X501/20Q154X501, BIOS N2JETA7W (1.85 ) 11/06/2024
Mar 09 01:41:39 archbtw kernel: RIP: 0010:ring_interrupt_active+0x242/0x2d0 [thunderbolt]
Mar 09 01:41:39 archbtw kernel: Code: 08 44 89 04 24 e8 ce f6 f8 e0 44 8b 04 24 48 8b 4c 24 08 4d 89 f1 48 8b 54 24 10 48 89 c6 48 c7 c7 b8 16 ab c0 e8 5e aa 40 e0 <0f> 0b 4d 8b 77 08 44 8b 5c 24 04 49 8b 76 18 45 84 e4 0f 85 e9 fe
Mar 09 01:41:39 archbtw kernel: RSP: 0000:ffffd2c400757b90 EFLAGS: 00010046
Mar 09 01:41:39 archbtw kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027
Mar 09 01:41:39 archbtw kernel: RDX: ffff8de94e49d008 RSI: 0000000000000001 RDI: ffff8de94e49d000
Mar 09 01:41:39 archbtw kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 00000000ffffefff
Mar 09 01:41:39 archbtw kernel: R10: ffffffffa2a61440 R11: ffffd2c400757a28 R12: 0000000000000001
Mar 09 01:41:39 archbtw kernel: R13: 0000000000038200 R14: ffffffffc0aaf9f7 R15: ffff8de605dd5b40
Mar 09 01:41:39 archbtw kernel: FS:  0000000000000000(0000) GS:ffff8de9aad6e000(0000) knlGS:0000000000000000
Mar 09 01:41:39 archbtw kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 09 01:41:39 archbtw kernel: CR2: 00007fe4afd1200c CR3: 0000000283d5c001 CR4: 00000000003726f0
Mar 09 01:41:39 archbtw kernel: Call Trace:
Mar 09 01:41:39 archbtw kernel:  <TASK>
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  tb_ring_start+0x149/0x300 [thunderbolt 4ec4cb6f12868dd7644c60112ced7bd07c37d901]
Mar 09 01:41:39 archbtw kernel:  ? pci_pme_active+0x1bd/0x1d0
Mar 09 01:41:39 archbtw kernel:  tb_ctl_start+0x26/0xa0 [thunderbolt 4ec4cb6f12868dd7644c60112ced7bd07c37d901]
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  tb_domain_runtime_resume+0x19/0x40 [thunderbolt 4ec4cb6f12868dd7644c60112ced7bd07c37d901]
Mar 09 01:41:39 archbtw kernel:  __rpm_callback+0x48/0x1f0
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? pcie_port_device_runtime_resume+0x33/0x50
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  rpm_callback+0x6d/0x80
Mar 09 01:41:39 archbtw kernel:  rpm_resume+0x4ab/0x6d0
Mar 09 01:41:39 archbtw kernel:  ? rpm_resume+0x1a0/0x6d0
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? __pfx_dpc_reset_link+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  __pm_runtime_resume+0x52/0x90
Mar 09 01:41:39 archbtw kernel:  pci_pm_runtime_get_sync+0x1a/0x30
Mar 09 01:41:39 archbtw kernel:  __pci_walk_bus+0x4c/0x70
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  __pci_walk_bus+0x34/0x70
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  __pci_walk_bus+0x34/0x70
Mar 09 01:41:39 archbtw kernel:  pci_walk_bus+0x37/0x50
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  pcie_do_recovery+0xa3/0x3f0
Mar 09 01:41:39 archbtw kernel:  dpc_handler+0x4a/0x140
Mar 09 01:41:39 archbtw kernel:  irq_thread_fn+0x25/0x60
Mar 09 01:41:39 archbtw kernel:  irq_thread+0x1c9/0x350
Mar 09 01:41:39 archbtw kernel:  ? __pfx_irq_thread_fn+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? __pfx_irq_thread+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  kthread+0xfc/0x240
Mar 09 01:41:39 archbtw kernel:  ? __pfx_kthread+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ret_from_fork+0x1c2/0x1f0
Mar 09 01:41:39 archbtw kernel:  ? __pfx_kthread+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ret_from_fork_asm+0x1a/0x30
Mar 09 01:41:39 archbtw kernel:  </TASK>
Mar 09 01:41:39 archbtw kernel: ---[ end trace 0000000000000000 ]---
Mar 09 01:41:39 archbtw kernel: ------------[ cut here ]------------
Mar 09 01:41:39 archbtw kernel: thunderbolt 0000:04:00.0: interrupt for RX ring 0 is already enabled
Mar 09 01:41:39 archbtw kernel: WARNING: CPU: 2 PID: 99 at drivers/thunderbolt/nhi.c:147 ring_interrupt_active+0x242/0x2d0 [thunderbolt]
Mar 09 01:41:39 archbtw kernel: Modules linked in: hid_playstation ff_memless led_class_multicolor rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device uinput xt_MASQUERADE xt_tcpudp xt_mark nft_reject_ipv4 act_csum cls_u32 sch_htb nf_nat_tftp nf_conntrack_tftp bridge stp llc tun ccm algif_aead des3_ede_x86_64 des_generic libdes md4 nft_masq nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security nf_tables ip6table_filter ip6_tables iptable_filter ip_tables x_tables cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_intelhdmi amdgpu snd_hda_codec_alc269 snd_hda_scodec_component snd_hda_codec_realtek_lib snd_hda_codec_generic ucsi_acpi typec_ucsi typec roles snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common intel_uncore_frequency
Mar 09 01:41:39 archbtw kernel:  intel_uncore_frequency_common snd_soc_hdac_hda intel_pmc_core_pltdrv snd_sof_intel_hda_mlink intel_pmc_core snd_sof_intel_hda pmt_telemetry soundwire_cadence pmt_discovery snd_sof_pci pmt_class snd_sof_xtensa_dsp intel_pmc_ssram_telemetry intel_vsec snd_sof intel_tcc_cooling snd_sof_utils x86_pkg_temp_thermal snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks intel_powerclamp soundwire_generic_allocation snd_soc_acpi coretemp soundwire_bus snd_soc_sdca kvm_intel processor_thermal_device_pci_legacy crc8 amdxcp vfat r8153_ecm processor_thermal_device cdc_ether drm_panel_backlight_quirks fat elan_i2c snd_soc_avs usbnet think_lmi iwlmvm intel_rapl_msr gpu_sched mei_hdcp snd_hda_codec_atihdmi mei_pxp processor_thermal_wt_hint snd_soc_hda_codec drm_exec i915 snd_hda_codec_hdmi kvm firmware_attributes_class platform_temperature_control drm_suballoc_helper snd_hda_intel snd_hda_ext_core mac80211 drm_buddy drm_ttm_helper processor_thermal_soc_slider intel_wmi_thunderbolt wmi_bmof irqbypass snd_hda_codec
Mar 09 01:41:39 archbtw kernel:  processor_thermal_rfim uvcvideo btusb polyval_clmulni videobuf2_vmalloc libarc4 btmtk ghash_clmulni_intel snd_hda_core uvc processor_thermal_rapl snd_soc_core aesni_intel intel_rapl_common snd_intel_dspcfg videobuf2_memops r8152 ttm btrtl iwlwifi snd_compress rapl btbcm i2c_algo_bit snd_ctl_led intel_cstate processor_thermal_wt_req mii e1000e i2c_i801 snd_intel_sdw_acpi drm_display_helper videobuf2_v4l2 spi_nor processor_thermal_power_floor btintel intel_uncore psmouse mei_me pcspkr libphy processor_thermal_mbox i2c_smbus ac97_bus snd_hwdep ptp mdio_bus mtd pps_core cec snd_pcm_dmaengine i2c_mux videobuf2_common thinkpad_acpi mei cfg80211 bluetooth platform_profile intel_soc_dts_iosf thunderbolt sparse_keymap intel_pch_thermal intel_gtt joydev int3403_thermal int340x_thermal_zone rfkill mousedev video pinctrl_cannonlake int3400_thermal acpi_thermal_rel wmi acpi_pad mac_hid snd_aloop snd_pcm v4l2loopback(OE) snd_timer videodev snd dm_mod mc pkcs8_key_parser uhid soundcore i2c_dev crypto_user ntsync
Mar 09 01:41:39 archbtw kernel:  nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress bpf_preload uas usb_storage mmc_block rpmb_core nvme sdhci_pci nvme_core sdhci_uhs2 sdhci nvme_keyring cqhci nvme_auth hkdf mmc_core serio_raw spi_intel_pci spi_intel
Mar 09 01:41:39 archbtw kernel: CPU: 2 UID: 0 PID: 99 Comm: irq/121-pcie-dp Tainted: G S   U  W  OE       6.18.16-1-lts #1 PREEMPT(voluntary)  674a1aec569c3e6c68f0032d072385577b88e9e1
Mar 09 01:41:39 archbtw kernel: Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Mar 09 01:41:39 archbtw kernel: Hardware name: LENOVO 20Q154X501/20Q154X501, BIOS N2JETA7W (1.85 ) 11/06/2024
Mar 09 01:41:39 archbtw kernel: RIP: 0010:ring_interrupt_active+0x242/0x2d0 [thunderbolt]
Mar 09 01:41:39 archbtw kernel: Code: 08 44 89 04 24 e8 ce f6 f8 e0 44 8b 04 24 48 8b 4c 24 08 4d 89 f1 48 8b 54 24 10 48 89 c6 48 c7 c7 b8 16 ab c0 e8 5e aa 40 e0 <0f> 0b 4d 8b 77 08 44 8b 5c 24 04 49 8b 76 18 45 84 e4 0f 85 e9 fe
Mar 09 01:41:39 archbtw kernel: RSP: 0000:ffffd2c400757b90 EFLAGS: 00010046
Mar 09 01:41:39 archbtw kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027
Mar 09 01:41:39 archbtw kernel: RDX: ffff8de94e49d008 RSI: 0000000000000001 RDI: ffff8de94e49d000
Mar 09 01:41:39 archbtw kernel: RBP: 0000000000001000 R08: 0000000000000000 R09: 00000000ffffefff
Mar 09 01:41:39 archbtw kernel: R10: ffffffffa2a61440 R11: ffffd2c400757a28 R12: 0000000000000001
Mar 09 01:41:39 archbtw kernel: R13: 0000000000038200 R14: ffffffffc0aaf9f7 R15: ffff8de605dd5300
Mar 09 01:41:39 archbtw kernel: FS:  0000000000000000(0000) GS:ffff8de9aad6e000(0000) knlGS:0000000000000000
Mar 09 01:41:39 archbtw kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 09 01:41:39 archbtw kernel: CR2: 00007fe4afd1200c CR3: 0000000283d5c001 CR4: 00000000003726f0
Mar 09 01:41:39 archbtw kernel: Call Trace:
Mar 09 01:41:39 archbtw kernel:  <TASK>
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  tb_ring_start+0x149/0x300 [thunderbolt 4ec4cb6f12868dd7644c60112ced7bd07c37d901]
Mar 09 01:41:39 archbtw kernel:  ? pci_pme_active+0x1bd/0x1d0
Mar 09 01:41:39 archbtw kernel:  tb_ctl_start+0x30/0xa0 [thunderbolt 4ec4cb6f12868dd7644c60112ced7bd07c37d901]
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  tb_domain_runtime_resume+0x19/0x40 [thunderbolt 4ec4cb6f12868dd7644c60112ced7bd07c37d901]
Mar 09 01:41:39 archbtw kernel:  __rpm_callback+0x48/0x1f0
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? pcie_port_device_runtime_resume+0x33/0x50
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_resume+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  rpm_callback+0x6d/0x80
Mar 09 01:41:39 archbtw kernel:  rpm_resume+0x4ab/0x6d0
Mar 09 01:41:39 archbtw kernel:  ? rpm_resume+0x1a0/0x6d0
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? __pfx_dpc_reset_link+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  __pm_runtime_resume+0x52/0x90
Mar 09 01:41:39 archbtw kernel:  pci_pm_runtime_get_sync+0x1a/0x30
Mar 09 01:41:39 archbtw kernel:  __pci_walk_bus+0x4c/0x70
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  __pci_walk_bus+0x34/0x70
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  __pci_walk_bus+0x34/0x70
Mar 09 01:41:39 archbtw kernel:  pci_walk_bus+0x37/0x50
Mar 09 01:41:39 archbtw kernel:  ? __pfx_pci_pm_runtime_get_sync+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  pcie_do_recovery+0xa3/0x3f0
Mar 09 01:41:39 archbtw kernel:  dpc_handler+0x4a/0x140
Mar 09 01:41:39 archbtw kernel:  irq_thread_fn+0x25/0x60
Mar 09 01:41:39 archbtw kernel:  irq_thread+0x1c9/0x350
Mar 09 01:41:39 archbtw kernel:  ? __pfx_irq_thread_fn+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ? __pfx_irq_thread+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  kthread+0xfc/0x240
Mar 09 01:41:39 archbtw kernel:  ? __pfx_kthread+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ret_from_fork+0x1c2/0x1f0
Mar 09 01:41:39 archbtw kernel:  ? __pfx_kthread+0x10/0x10
Mar 09 01:41:39 archbtw kernel:  ret_from_fork_asm+0x1a/0x30
Mar 09 01:41:39 archbtw kernel:  </TASK>
Mar 09 01:41:39 archbtw kernel: ---[ end trace 0000000000000000 ]---
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:40 param:0x00000000 message:AllowGfxOff?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to enable gfxoff!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:39 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: pcieport 0000:03:02.0: Unable to change power state from D3hot to D0, device inaccessible
Mar 09 01:41:40 archbtw kernel: snd_hda_intel 0000:09:00.1: Unable to change power state from D3hot to D0, device inaccessible
Mar 09 01:41:40 archbtw kernel: pcieport 0000:06:04.0: Unable to change power state from D3hot to D0, device inaccessible
Mar 09 01:41:40 archbtw kernel: pcieport 0000:06:04.0: pciehp: pcie_do_write_cmd: no response from device
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: snd_hda_intel 0000:09:00.1: CORB reset timeout#2, CORBRP = 65535
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: pcieport 0000:06:04.0: pciehp: pcie_do_write_cmd: no response from device
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:40 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:41 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:42 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: pcieport 0000:00:1c.4: pciehp: Slot(4): Link Down
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: Controller not ready at resume -19
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: PCI post-resume error -19!
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: HC died; cleaning up
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: remove, state 4
Mar 09 01:41:43 archbtw kernel: usb usb6: USB disconnect, device number 1
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: USB bus 6 deregistered
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: remove, state 4
Mar 09 01:41:43 archbtw kernel: usb usb5: USB disconnect, device number 1
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: Host halt failed, -19
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: Host not accessible, reset failed.
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:6e:00.0: USB bus 5 deregistered
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:3a:00.0: remove, state 1
Mar 09 01:41:43 archbtw kernel: usb usb4: USB disconnect, device number 1
Mar 09 01:41:43 archbtw kernel: r8152-cfgselector 4-2: USB disconnect, device number 3
Mar 09 01:41:43 archbtw kernel: r8152 4-2:1.0 enp58s0u2: Tx status -108
Mar 09 01:41:43 archbtw tailscaled[772]: monitor: RTM_DELROUTE: src=, dst=fe80::/64, gw=, outif=8, table=254
Mar 09 01:41:43 archbtw tailscaled[772]: monitor: RTM_DELROUTE: src=, dst=fe80::/128, gw=, outif=8, table=255
Mar 09 01:41:43 archbtw tailscaled[772]: monitor: RTM_DELROUTE: src=, dst=fe80::b63c:80ee:e327:5d7a/128, gw=, outif=8, table=255
Mar 09 01:41:43 archbtw tailscaled[772]: monitor: RTM_DELROUTE: src=, dst=ff00::/8, gw=, outif=8, table=255
Mar 09 01:41:43 archbtw tailscaled[772]: monitor: RTM_DELROUTE: src=192.168.1.41/0, dst=192.168.1.41/32, gw=, outif=8, table=255
Mar 09 01:41:43 archbtw tailscaled[772]: tsdial: closing system connection 192.168.1.41:52602->192.200.0.102:443 due to link change
Mar 09 01:41:43 archbtw NetworkManager[706]: <info>  [1773000703.7506] device (enp58s0u2): state change: activated -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
Mar 09 01:41:43 archbtw NetworkManager[706]: <info>  [1773000703.7507] dhcp4 (enp58s0u2): canceled DHCP transaction
Mar 09 01:41:43 archbtw NetworkManager[706]: <info>  [1773000703.7507] dhcp4 (enp58s0u2): activation: beginning transaction (timeout in 45 seconds)
Mar 09 01:41:43 archbtw NetworkManager[706]: <info>  [1773000703.7507] dhcp4 (enp58s0u2): state changed no lease
Mar 09 01:41:43 archbtw NetworkManager[706]: <info>  [1773000703.7515] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 09 01:41:43 archbtw NetworkManager[706]: <info>  [1773000703.7521] dns-mgr: Removing DNS information from /usr/bin/resolvconf
Mar 09 01:41:43 archbtw tailscaled[772]: Received error: PollNetMap: read tcp 192.168.1.41:52602->192.200.0.102:443: use of closed network connection
Mar 09 01:41:43 archbtw systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 09 01:41:43 archbtw systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:43 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:3a:00.0: USB bus 4 deregistered
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:3a:00.0: remove, state 1
Mar 09 01:41:43 archbtw kernel: usb usb3: USB disconnect, device number 1
Mar 09 01:41:43 archbtw kernel: usb 3-1: USB disconnect, device number 2
Mar 09 01:41:43 archbtw kded6[1444]: Failed to notify "Created too many similar notifications in quick succession"
Mar 09 01:41:43 archbtw kernel: xhci_hcd 0000:3a:00.0: USB bus 3 deregistered
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw tailscaled[772]: control: controlhttp: forcing port 443 dial due to recent noise dial
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: snd_hda_intel 0000:09:00.1: CORB reset timeout#2, CORBRP = 65535
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw tailscaled[772]: [RATELIMIT] format("dns udp query: %v") (17 dropped)
Mar 09 01:41:44 archbtw tailscaled[772]: dns udp query: resolving using "https://base.dns.mullvad.net/dns-query": Post "https://base.dns.mullvad.net/dns-query": dial tcp [2a07:e340::4]:443: connect: network is unreachable
Mar 09 01:41:44 archbtw tailscaled[772]: dns udp query: resolving using "https://base.dns.mullvad.net/dns-query": Post "https://base.dns.mullvad.net/dns-query": dial tcp [2a07:e340::4]:443: connect: network is unreachable
Mar 09 01:41:44 archbtw tailscaled[772]: dns udp query: resolving using "https://base.dns.mullvad.net/dns-query": Post "https://base.dns.mullvad.net/dns-query": dial tcp [2a07:e340::4]:443: connect: network is unreachable
Mar 09 01:41:44 archbtw tailscaled[772]: dns udp query: resolving using "https://base.dns.mullvad.net/dns-query": Post "https://base.dns.mullvad.net/dns-query": dial tcp [2a07:e340::4]:443: connect: network is unreachable
Mar 09 01:41:44 archbtw tailscaled[772]: dns udp query: resolving using "https://base.dns.mullvad.net/dns-query": Post "https://base.dns.mullvad.net/dns-query": dial tcp [2a07:e340::4]:443: connect: network is unreachable
Mar 09 01:41:44 archbtw tailscaled[772]: [RATELIMIT] format("dns udp query: %v")
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: snd_hda_intel 0000:09:00.1: CORB reset timeout#2, CORBRP = 65535
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:44 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to export SMU metrics table!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: VM memory stats for proc (0) task (0) is non-zero when fini
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: amdgpu: finishing device.
Mar 09 01:41:45 archbtw org_kde_powerdevil[1524]: [  1628] Udev event detected
Mar 09 01:41:45 archbtw systemd-coredump[19704]: Process 784 (Xorg) of user 0 terminated abnormally with signal 6/ABRT, processing...
Mar 09 01:41:45 archbtw systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
Mar 09 01:41:45 archbtw systemd[1]: Created slice Slice /system/systemd-coredump.
Mar 09 01:41:45 archbtw systemd[1]: Started Process Core Dump (PID 19704/UID 0).
Mar 09 01:41:45 archbtw systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Mar 09 01:41:45 archbtw lact[867]: 2026-03-08T20:11:45.351441Z  INFO lact_daemon: got kernel drm subsystem event, reloading GPUs
Mar 09 01:41:45 archbtw lact[867]: 2026-03-08T20:11:45.362730Z  INFO lact_daemon::server::handler: initialized i915 controller for GPU 8086:3EA0-17AA:2286-0000:00:02.0 at '/sys/class/drm/card1/device'
Mar 09 01:41:45 archbtw lact[867]: 2026-03-08T20:11:45.362745Z  INFO lact_daemon::server::handler: GPU list reloaded with 1 devices, reapplying configuration
Mar 09 01:41:45 archbtw lact[867]: 2026-03-08T20:11:45.362847Z  WARN lact_daemon::server::handler: could not find GPU with id 1002:73DF-1DA2:E445-0000:09:00.0 defined in configuration
Mar 09 01:41:45 archbtw lact[867]: 2026-03-08T20:11:45.362883Z  INFO lact_daemon::server::handler: configuration applied
Mar 09 01:41:45 archbtw steam[5264]: radv/amdgpu: Failed to query the last GPUVM fault (-19).
Mar 09 01:41:45 archbtw steam[5264]: radv/amdgpu: Failed to allocate a buffer:
Mar 09 01:41:45 archbtw steam[5264]: radv/amdgpu:    size      : 8294400 bytes
Mar 09 01:41:45 archbtw steam[5264]: radv/amdgpu:    alignment : 262144 bytes
Mar 09 01:41:45 archbtw steam[5264]: radv/amdgpu:    domains   : 2
Mar 09 01:41:45 archbtw org_kde_powerdevil[1524]: [  1628] Udev event detected
Mar 09 01:41:45 archbtw tailscaled[772]: control: controlhttp: failed dialing using DialPlan, falling back to DNS; errs=all connection attempts failed (HTTP: dial tcp [2606:b740:49::110]:80: connect: network is unreachable, HTTPS: dial tcp [2606:b740:49::110]:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp 192.200.0.110:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp [2606:b740:49::104]:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp 192.200.0.104:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp [2606:b740:49::112]:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp 192.200.0.112:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp [2606:b740:49::111]:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp 192.200.0.111:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: [RATELIMIT] format("control: trying bootstrapDNS(%q, %q) for %q ...") (7 dropped)
Mar 09 01:41:45 archbtw tailscaled[772]: control: trying bootstrapDNS("derp4h.tailscale.com", "185.40.234.77") for "controlplane.tailscale.com" ...
Mar 09 01:41:45 archbtw tailscaled[772]: [RATELIMIT] format("control: bootstrapDNS(%q, %q) for %q error: %v") (7 dropped)
Mar 09 01:41:45 archbtw tailscaled[772]: control: bootstrapDNS("derp4h.tailscale.com", "185.40.234.77") for "controlplane.tailscale.com" error: Get "https://derp4h.tailscale.com/bootstrap-dns?q=controlplane.tailscale.com": dial tcp 185.40.234.77:443: connect: network is unreachable
Mar 09 01:41:45 archbtw tailscaled[772]: control: trying bootstrapDNS("derp21d.tailscale.com", "2607:f740:50::ca4") for "controlplane.tailscale.com" ...
Mar 09 01:41:45 archbtw tailscaled[772]: control: bootstrapDNS("derp21d.tailscale.com", "2607:f740:50::ca4") for "controlplane.tailscale.com" error: Get "https://derp21d.tailscale.com/bootstrap-dns?q=controlplane.tailscale.com": dial tcp [2607:f740:50::ca4]:443: connect: network is unreachable
Mar 09 01:41:45 archbtw tailscaled[772]: control: trying bootstrapDNS("derp18b.tailscale.com", "176.58.90.147") for "controlplane.tailscale.com" ...
Mar 09 01:41:45 archbtw tailscaled[772]: control: bootstrapDNS("derp18b.tailscale.com", "176.58.90.147") for "controlplane.tailscale.com" error: Get "https://derp18b.tailscale.com/bootstrap-dns?q=controlplane.tailscale.com": dial tcp 176.58.90.147:443: connect: network is unreachable
Mar 09 01:41:45 archbtw tailscaled[772]: control: trying bootstrapDNS("derp11e.tailscale.com", "2600:3c0d::2000:d2ff:fe43:1790") for "controlplane.tailscale.com" ...
Mar 09 01:41:45 archbtw tailscaled[772]: control: bootstrapDNS("derp11e.tailscale.com", "2600:3c0d::2000:d2ff:fe43:1790") for "controlplane.tailscale.com" error: Get "https://derp11e.tailscale.com/bootstrap-dns?q=controlplane.tailscale.com": dial tcp [2600:3c0d::2000:d2ff:fe43:1790]:443: connect: network is unreachable
Mar 09 01:41:45 archbtw tailscaled[772]: control: trying bootstrapDNS("derp12f.tailscale.com", "199.38.182.118") for "controlplane.tailscale.com" ...
Mar 09 01:41:45 archbtw tailscaled[772]: [RATELIMIT] format("control: trying bootstrapDNS(%q, %q) for %q ...")
Mar 09 01:41:45 archbtw tailscaled[772]: control: bootstrapDNS("derp12f.tailscale.com", "199.38.182.118") for "controlplane.tailscale.com" error: Get "https://derp12f.tailscale.com/bootstrap-dns?q=controlplane.tailscale.com": dial tcp 199.38.182.118:443: connect: network is unreachable
Mar 09 01:41:45 archbtw tailscaled[772]: [RATELIMIT] format("control: bootstrapDNS(%q, %q) for %q error: %v")
Mar 09 01:41:45 archbtw tailscaled[772]: Received error: PollNetMap: Post "https://controlplane.tailscale.com/machine/map": all connection attempts failed (HTTP: TLS forced: no port 80 dialed, HTTPS: dial tcp [2606:b740:49::105]:443: connect: network is unreachable)
Mar 09 01:41:45 archbtw tailscaled[772]: control: controlhttp: forcing port 443 dial due to recent noise dial
Mar 09 01:41:45 archbtw systemd-coredump[19705]: Process 784 (Xorg) of user 0 dumped core.
                                                 
                                                 Stack trace of thread 784:
                                                 #0  0x00007fac900caa2c n/a (libc.so.6 + 0x98a2c)
                                                 #1  0x00007fac900701a0 raise (libc.so.6 + 0x3e1a0)
                                                 #2  0x00007fac900575fe abort (libc.so.6 + 0x255fe)
                                                 #3  0x00005626ccd791be OsAbort (/usr/lib/Xorg + 0x1601be)
                                                 #4  0x00005626ccd86510 FatalError (/usr/lib/Xorg + 0x16d510)
                                                 #5  0x00005626ccd7b6b3 n/a (/usr/lib/Xorg + 0x1626b3)
                                                 #6  0x00007fac900702d0 n/a (libc.so.6 + 0x3e2d0)
                                                 
                                                 Stack trace of thread 787:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 786:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 788:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1042:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1049:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1046:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 789:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1040:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 794:
                                                 #0  0x00007fac900c58d0 n/a (libc.so.6 + 0x938d0)
                                                 #1  0x00007fac900cc139 pthread_mutex_lock (libc.so.6 + 0x9a139)
                                                 #2  0x00005626ccd7a65c n/a (/usr/lib/Xorg + 0x16165c)
                                                 #3  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #4  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1048:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1041:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1044:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1045:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1043:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 
                                                 Stack trace of thread 1047:
                                                 #0  0x00007fac900d0f32 n/a (libc.so.6 + 0x9ef32)
                                                 #1  0x00007fac900c539c n/a (libc.so.6 + 0x9339c)
                                                 #2  0x00007fac900c568c n/a (libc.so.6 + 0x9368c)
                                                 #3  0x00007fac900c7e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
                                                 #4  0x00007fac8c9ec55e n/a (libgallium-26.0.1-arch1.1.so + 0x5ec55e)
                                                 #5  0x00007fac8c9a18fd n/a (libgallium-26.0.1-arch1.1.so + 0x5a18fd)
                                                 #6  0x00007fac8c9ec49d n/a (libgallium-26.0.1-arch1.1.so + 0x5ec49d)
                                                 #7  0x00007fac900c897a n/a (libc.so.6 + 0x9697a)
                                                 #8  0x00007fac9014c2bc n/a (libc.so.6 + 0x11a2bc)
                                                 ELF object binary architecture: AMD x86-64
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110)
Mar 09 01:41:45 archbtw sddm[782]: Display server stopped.
Mar 09 01:41:45 archbtw sddm[782]: Running display stop script  QList("/usr/share/sddm/scripts/Xstop")
Mar 09 01:41:45 archbtw systemd[1]: systemd-coredump@0-4109-19704_19705-0.service: Deactivated successfully.
Mar 09 01:41:45 archbtw systemd[1]: systemd-coredump@0-4109-19704_19705-0.service: Consumed 375ms CPU time over 481ms wall clock time, 168.7M memory peak.
Mar 09 01:41:45 archbtw sddm-helper[1179]: Signal received: SIGTERM
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw systemd[1185]: Stopped target plasma-workspace-wayland.target.
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw systemd[1185]: Stopped target KDE Plasma Workspace.
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw systemd[1185]: Stopped target Startup of XDG autostart applications.
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Firewall Applet...
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Geoclue Demo agent...
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: failed to clear page tables on GEM object close (-19)
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: leaking bo va (-19)
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Discover...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Calendar Reminders...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping KDE Connect...
Mar 09 01:41:45 archbtw dbus-broker[1437]: Dispatched 300 messages @ 3(±4)μs / message.
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Accessibility services bus...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Virtual filesystem service...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Proxies GTK DBus menus to a Plasma readable format...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping KAccess...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping KDE Night Time Service...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Track hardware statistics...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping KDE PolicyKit Authentication Agent...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Powerdevil...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Xdg Desktop Portal For KDE...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Handle legacy xembed system tray icons...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Portal service (GTK/GNOME implementation)...
Mar 09 01:41:45 archbtw systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
Mar 09 01:41:45 archbtw kded6[1444]: Service  ":1.75" unregistered
Mar 09 01:41:45 archbtw drkonqi-coredump-processor[19706]: "/usr/lib/Xorg" 784 "/var/lib/systemd/coredump/core.Xorg.0.1450518f871f46a5a990f2a30a48b616.784.1773000705000000.zst"
Mar 09 01:41:45 archbtw drkonqi-coredump-processor[19706]: The socket path doesn't exist @ "/run/user/0/drkonqi-coredump-launcher"
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Portal service...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping flatpak document portal service...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping sandboxed app permission store...
Mar 09 01:41:45 archbtw systemd[1185]: Stopping Baloo File Indexer Daemon...
Mar 09 01:41:45 archbtw systemd[1]: drkonqi-coredump-processor@0-4109-19704_19705-0.service: Deactivated successfully.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Portal service.
Mar 09 01:41:45 archbtw systemd[1185]: xdg-desktop-portal.service: Consumed 1.726s CPU time over 3min 38.130s wall clock time, 8.7M memory peak.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped sandboxed app permission store.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped KDE Night Time Service.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Accessibility services bus.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Firewall Applet.
Mar 09 01:41:45 archbtw systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Portal service (GTK/GNOME implementation).
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Geoclue Demo agent.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Discover.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Virtual filesystem service.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Xdg Desktop Portal For KDE.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped KDE Connect.
Mar 09 01:41:45 archbtw systemd[1185]: app-org.kde.kdeconnect.daemon@autostart.service: Consumed 1.388s CPU time over 3min 35.726s wall clock time, 42.6M memory peak.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Baloo File Indexer Daemon.
Mar 09 01:41:45 archbtw systemd[1185]: kde-baloo.service: Consumed 1.968s CPU time over 3min 38.178s wall clock time, 241.6M memory peak.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Proxies GTK DBus menus to a Plasma readable format.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped KAccess.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Handle legacy xembed system tray icons.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Track hardware statistics.
Mar 09 01:41:45 archbtw systemd[1185]: plasma-ksystemstats.service: Consumed 1.219s CPU time over 3min 34.281s wall clock time, 7.3M memory peak.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped flatpak document portal service.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped KDE PolicyKit Authentication Agent.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped Powerdevil.
Mar 09 01:41:45 archbtw systemd[1185]: Stopped target KDE Plasma Workspace Core.
Mar 09 01:41:45 archbtw systemd[1185]: Stopping KDE Daemon 6...
Mar 09 01:41:45 archbtw sddm-helper[1179]: [PAM] Closing session
Mar 09 01:41:45 archbtw systemd[1185]: Starting Track hardware statistics...
Mar 09 01:41:45 archbtw sddm-helper[1179]: pam_unix(sddm:session): session closed for user potato
Mar 09 01:41:45 archbtw sddm-helper[1179]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Mar 09 01:41:45 archbtw sddm-helper[1179]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 09 01:41:45 archbtw sddm-helper[1179]: [PAM] Ended.
Mar 09 01:41:45 archbtw systemd[1185]: Stopping KDE Plasma Workspace...
Mar 09 01:41:45 archbtw sddm[782]: Auth: sddm-helper exited with 255
Mar 09 01:41:45 archbtw sddm[782]: Socket server stopping...
Mar 09 01:41:45 archbtw sddm[782]: Socket server stopped.
Mar 09 01:41:45 archbtw sddm[782]: Removing display SDDM::Display(0x563cedb18e90) ...
Mar 09 01:41:45 archbtw sddm[782]: Adding new display...
Mar 09 01:41:45 archbtw sddm[782]: Loaded empty theme configuration
Mar 09 01:41:45 archbtw sddm[782]: Xauthority path: "/run/sddm/xauth_jeKaFV"
Mar 09 01:41:45 archbtw sddm[782]: Using VT 2
Mar 09 01:41:45 archbtw sddm[782]: Display server starting...
Mar 09 01:41:45 archbtw sddm[782]: Writing cookie to "/run/sddm/xauth_jeKaFV"
Mar 09 01:41:45 archbtw sddm[782]: Running: /usr/bin/X -dpi 0 -background none -seat seat0 vt2 -auth /run/sddm/xauth_jeKaFV -noreset -displayfd 18
Mar 09 01:41:45 archbtw systemd-logind[570]: Session 2 logged out. Waiting for processes to exit.
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/ldac
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSink/aptx_hd
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_hd
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSink/aptx
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSink/aac
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aac
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSink/opus_g
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/opus_g
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/faststream
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSink/opus_05
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/opus_05
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Mar 09 01:41:45 archbtw bluetoothd[563]: Endpoint unregistered: sender=:1.38 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Mar 09 01:41:45 archbtw plasmashell[1475]: corrupted double-linked list
Mar 09 01:41:45 archbtw plasmashell[1475]: KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2
Mar 09 01:41:45 archbtw systemd-coredump[19791]: Process 1475 (plasmashell) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Mar 09 01:41:45 archbtw kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: device lost from bus!
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:7 param:0x00000000 message:DisableAllSmuFeatures?
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: Failed to disable smu features.
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: ring_buffer_start = 0000000065517173; ring_buffer_end = 00000000af4a9476; write_frame = 000000004a65546c
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: write_frame is pointing to address out of bounds
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: ring_buffer_start = 0000000065517173; ring_buffer_end = 00000000af4a9476; write_frame = 000000004a65546c
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: write_frame is pointing to address out of bounds
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: ring_buffer_start = 0000000065517173; ring_buffer_end = 00000000af4a9476; write_frame = 000000004a65546c
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: write_frame is pointing to address out of bounds
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: ring_buffer_start = 0000000065517173; ring_buffer_end = 00000000af4a9476; write_frame = 000000004a65546c
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: write_frame is pointing to address out of bounds
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: ring_buffer_start = 0000000065517173; ring_buffer_end = 00000000af4a9476; write_frame = 000000004a65546c
Mar 09 01:41:45 archbtw kernel: amdgpu 0000:09:00.0: amdgpu: write_frame is pointing to address out of bounds
Mar 09 01:41:45 archbtw systemd[1]: Started Process Core Dump (PID 19791/UID 0).
Mar 09 01:41:45 archbtw systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Mar 09 01:41:45 archbtw systemd[1]: Starting Hostname Service...

Last edited by potato035 (2026-03-08 23:10:55)

Arch Linux

#1 2026-01-20 19:25:17

AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#2 2026-01-20 20:07:56

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#3 2026-01-20 20:31:12

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#4 2026-01-22 15:20:22

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#5 2026-01-22 15:52:27

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#6 2026-01-22 20:11:31

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#7 2026-01-22 20:40:23

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#8 2026-01-23 15:04:51

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#9 2026-01-23 16:25:27

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#10 2026-01-23 16:29:37

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#11 2026-01-23 19:14:56

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#12 2026-01-23 19:42:59

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#13 2026-01-23 20:04:59

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#14 2026-01-23 20:36:42

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#15 2026-01-23 22:30:16

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#16 2026-01-24 15:39:17

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#17 2026-01-24 17:35:56

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#18 2026-01-25 21:59:25

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#19 2026-02-02 02:28:54

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#20 2026-02-02 17:13:28

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#21 2026-02-02 17:33:02

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#22 2026-02-02 23:08:08

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#23 2026-02-03 04:43:52

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#24 2026-02-04 01:51:02

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

#25 2026-03-08 22:25:13

Re: AMD eGPU over Thunderbolt: crashing like there's no tomorrow

Board footer