Framework Desktop unprompted restart with core dump on Ubuntu 25.10

Framework Desktop
1

Happy to provide more info but I installed the above, hoping to mostly run LLMs (LM Studio, Lemonade or llama.cpp, not sure yet), ComfyUI and Steam games. Wifi is off, Ethernet (2.5 Gbs) is on. USB-C monitor connected (DisplayLink drivers)

Not sure how to diagnose what’s happening but based on the kernel dump

The sytem kernel-panicked due to a bug in the Realtek Ethernet driver (r8169), while handling TCP traffic. Any advice on how to fix that?

========================================

Framework Complete Diagnostic Bundle
Generated: Sat Dec 27 16:49:15 EST 2025

=== PLATFORM DETECTION ===
Product: Desktop (AMD Ryzen AI Max 300 Series)
Version: A6
Manufacturer: Framework
Serial: FRAMDACPA6543600FA
BIOS Version: 03.04
BIOS Date: 11/19/2025

=== CPU INFORMATION ===
model name : AMD RYZEN AI MAX+ 395 w/ Radeon 8060S
CPU Cores: 32

=== GPU DETECTION ===
c2:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Strix Halo [Radeon Graphics / Radeon 8050S Graphics / Radeon 8060S Graphics] (rev c1)

=== MEMORY INFO ===
total used free shared buff/cache available
Mem: 122Gi 2.4Gi 119Gi 11Mi 1.9Gi 120Gi
Swap: 8.0Gi 0B 8.0Gi

=== STORAGE DEVICES ===
NAME SIZE TYPE MOUNTPOINT FSTYPE
loop0 73.9M loop /snap/core22/2133 squashfs
loop1 4K loop /snap/bare/5 squashfs
loop2 66.8M loop /snap/core24/1243 squashfs
loop3 11.8M loop /snap/desktop-security-center/59 squashfs
loop4 74M loop /snap/core22/2193 squashfs
loop5 22.6M loop /snap/desktop-security-center/99 squashfs
loop6 247.6M loop /snap/firefox/6966 squashfs
loop7 516.2M loop /snap/gnome-42-2204/226 squashfs
loop8 250.8M loop /snap/firefox/7559 squashfs
loop9 242.6M loop /snap/gaming-graphics-core24/13 squashfs
loop10 18.5M loop /snap/firmware-updater/210 squashfs
loop11 11.1M loop /snap/firmware-updater/167 squashfs
loop12 50.8M loop /snap/snapd/25202 squashfs
loop13 17.5M loop /snap/snap-store/1300 squashfs
loop14 91.7M loop /snap/gtk-common-themes/1535 squashfs
loop15 50.9M loop /snap/snapd/25577 squashfs
loop16 14.4M loop /snap/prompting-client/104 squashfs
loop17 576K loop /snap/snapd-desktop-integration/315 squashfs
loop18 278.4M loop /snap/steam/231 squashfs
nvme0n1 3.6T disk
├─nvme0n1p1 1G part /boot/efi vfat
└─nvme0n1p2 3.6T part / ext4

=== WIRELESS DEVICES ===
Bus 003 Device 003: ID 0e8d:0717 MediaTek Inc. Wireless_Device

=== KERNEL INFO ===
Linux framework 6.17.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 14 21:44:46 UTC 2025 x86_64 GNU/Linux

=== LOADED KERNEL MODULES (TOP 20) ===
Module Size Used by
aesni_intel 94208 3
af_alg 32768 6 algif_hash,algif_skcipher
algif_hash 16384 1
algif_skcipher 12288 1
amd_atl 73728 1
amd_pmc 49152 0
amd_pmf 110592 0
amd_sfh 73728 1 amd_pmf
amdgpu 20373504 15
amdtee 32768 0
amdxcp 12288 1 amdgpu
amdxdna 151552 0
autofs4 57344 2
binfmt_misc 24576 1
bluetooth 1040384 34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
bnep 32768 2
bridge 430080 0
btbcm 24576 1 btusb
btintel 69632 1 btusb

=== FIRMWARE STATUS ===
Status: :white_check_mark: No firmware load failures detected

=== DRIVER BINDINGS ===
pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted
c0:00.0 Network controller [0280]: MEDIATEK Corp. MT7925 (RZ717) Wi-Fi 7 160MHz [14c3:0717]
Subsystem: MEDIATEK Corp. MT7925 (RZ717) Wi-Fi 7 160MHz [14c3:0717]
Kernel driver in use: mt7925e
Kernel modules: mt7925e

=== FRAMEWORK TOOL: NOT FOUND ===
framework_tool not found in current directory or PATH
Download from: Releases · FrameworkComputer/framework-system · GitHub

=== FALLBACK: BASIC BATTERY INFO ===
No battery information available

=== ADDITIONAL SENSORS (lm-sensors) ===
amdgpu-pci-c200
Adapter: PCI adapter
vddgfx: 0.00 V
vddnb: 0.00 V
edge: +38.0°C
PPT: 9.06 W (avg = 9.06 W)
sclk: 600 MHz

cros_ec-isa-000c
Adapter: ISA adapter
fan1: 0 RPM
fan2: 0 RPM
fan3: 0 RPM
mainboard_power@4d: +35.9°C
mainboard_memory@4d: +35.9°C
mainboard_ambient@4d: +35.9°C
cpu@4c: +38.9°C
cpu_virtual@4c: +34.9°C

ucsi_source_psy_USBC000:002-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.10 A)

nvme-pci-c100
Adapter: PCI adapter
Composite: +36.9°C (low = -273.1°C, high = +81.8°C)
(crit = +84.8°C)
Sensor 1: +36.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +38.9°C (low = -273.1°C, high = +65261.8°C)

mt7925_phy0-pci-c000
Adapter: PCI adapter
temp1: +35.0°C

r8169_0_bf00:00-mdio-0
Adapter: MDIO adapter
temp1: +51.5°C (high = +120.0°C)

ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 3.00 A (max = +0.00 A)

acpitz-acpi-0
Adapter: ACPI interface
temp1: +35.8°C
temp2: +35.8°C
temp3: +35.8°C
temp4: +38.8°C

2

Can you post the full kernel stack trace?
As a temporary work around, try using a USB Ethernet adapter, until the r8169 bug is fixed.
For example the FW provided slot card for ethernet uses the r8152, that seems to work Ok.
It is a simple USB-C usb-to-ethernet card inside it.

3

I tried

sudo apt update
sudo apt install r8125-dkms
sudo modprobe -r r8169
sudo modprobe r8125

But I still got 8169 after a reboot and running: lsmod | grep r81

Here is the stack trace: gist:87680fe003e2d69659a5a6e5d5501db0 · GitHub

Based on the following, I blame the r8169 kernel module?

Call Trace:
kmem_cache_free
skb_release_data
kfree_skbmem
__kfree_skb
tcp_clean_rtx_queue
tcp_ack
tcp_rcv_established
…
rtl8169_poll
__napi_poll
net_rx_action

I’ll try a USB-C doc with Ethernet (1GB) in the mean time.

4

The stack trace is a bit odd. The gist link does not have the same messages as you post above.
Try to reproduce the problem without any usb devices plugged in, apart from mouse, keyboard and use a HDMI or DP display, and not a USB display.
Try to also use the desktop without the “evdi” driver.
That might at least narrow down the problem.

5

No, this was a later core dump.

Understood though, I’ll try running it without USB-C devices at all and on Wifi only. It’s surprising at this point that there are so many kernel issues with USB-C devices and network cards on recent Linux distros.

Instead of LLM serving and some light gaming, it’s been mostly core dumping since I bought it.

6

I’ve resintalled from scratch, using just Wifi. No USB-C devices, no display link drivers or device. I’ve tried Fedora 43 and Ubuntu 25.10, it’s just not stable, it crashes within 30 minutes to a few hours.