FW Desktop - Bazzite - Sudden reboots after coldstart when watching youtube videos

Community Support
,
1

BAZZITE:STABLE (latest) Framework Desktop AMD AI 300 (on firmware 3.03 because of known boot issues on fedora based distros since 3.04) + Razer TB4 Dock → Data Fabric Sync Flood (0x08000800)

  1. Summary
    System reboots instantly when using a Razer Thunderbolt 4 Dock Chroma on Framework Desktop AMD.
    Reset reason shows AMD Data Fabric Sync Flood (0x08000800), which is a fatal SoC‑level I/O fabric error.
    Logs confirm USB4/PCIe tunnel instability: link drops, retimer resets, Realtek NIC resets, and PCIe fallback to Gen1 x1.
  1. Reset Reason

Command:
sudo dmesg | grep -i reset

Output:
x86/amd: Previous system reset reason [0x08000800]: an uncorrected error caused a data fabric sync flood event

Meaning (according to AI):
A Data Fabric Sync Flood is an emergency hardware reset caused by a catastrophic USB4/PCIe/PD fabric failure.

  1. USB4 / Thunderbolt Stack

Command:
sudo dmesg | grep -Ei “usb4|retimer|tbt|thunderbolt|ucsi”

Key outputs:
ACPI: USB4 _OSC: OS supports USB3+ DisplayPort+ PCIe+ XDomain+
usb usb4: We don’t know the algorithms for LPM for this host, disabling LPM.
ucsi_acpi USBC000:00: unknown error 256
thunderbolt 1-2: Razer Thunderbolt 4 Dock
thunderbolt 1-0:2.1: new retimer found
thunderbolt 1-2:1.1: new retimer found

Meaning (according to AI):
UCSI error + retimer re-enumeration = unstable USB4 tunnel.

  1. PCIe Link Instability

Command:
sudo dmesg | grep -Ei “pcie|aer|correct|uncorrect”

Key outputs:
pciehp: Slot(0-1): Link Down
pciehp: Slot(0-1): Card not present
2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link
ASPM: current common clock configuration is inconsistent, reconfiguring

Meaning (according to AI):
PCIe tunnel collapses → dock re-enumerates at Gen1 x1.

  1. Realtek NIC Reset (Dock)

Command:
sudo dmesg | grep -Ei “r8169|rtl|reset”

Key:
r8152-cfgselector … reset SuperSpeed USB device

Meaning (according to AI):
NIC reset is a known trigger for USB4/PCIe instability.

  1. PCIe Link State (lspci -vv)

AMD Root Port (00:01.2)

Command:
sudo lspci -vv -s 00:01.2

Key:
LnkCap: Speed 2.5GT/s, Width x1
LnkSta: Speed 2.5GT/s, Width x1
Capabilities: [380 v1] Downstream Port Containment

Meaning (according to AI):
Should be 8.0GT/s x4. Running at Gen1 x1 = severe fallback.
DPC present → isolation of misbehaving dock triggers fabric panic.

Intel TB4 Switch (60:00.0)

Command:
sudo lspci -vv -s 60:00.0

Key:
LnkCap: Speed 2.5-8GT/s, Width x4
LnkSta: Speed 2.5GT/s, Width x4
DevSta: CorrErr+

Meaning (according to AI):
Switch supports Gen3/Gen4 but stuck at Gen1 → upstream instability.

  1. Behavioral Pattern

Reboot occur during:

  • YouTube (MS edge flatpak) via docked monitor (DP-over-USB4 + PCIe + retimers + NIC), so far only once after cold boot (both hub and FW Desktop power off disconnected from any power source → both simultaneously connected to power → power on)
  1. Questions
  • Is this pattern consistent with known AMD USB4 errata?
  • Would USB4 debug logs or AER dumps help?