I installed Fedora 41 KDE (not a live disk, installed) on a USB stick that I am booting from. It has power profiles daemon set to balanced. I have not encountered a reboot event in a few days of sleep/wake.
A few days later, I noticed there was amd-ucode updates on arch, so I installed those, and have not experienced another reboot since (fingers crossed). My PPD is also set to balanced here.
I am now running 6.13.7-arch1-1
From pacman logs
[2025-03-19T18:45:23-0400] [ALPM] upgraded amd-ucode (20250311.b69d4b74-2 → 20250311.b69d4b74-3)
[2025-03-19T18:45:23-0400] [ALPM] upgraded linux-firmware-whence (20250311.b69d4b74-2 → 20250311.b69d4b74-3)
[2025-03-19T18:45:24-0400] [ALPM] upgraded linux-firmware (20250311.b69d4b74-2 → 20250311.b69d4b74-3)
I have been dailying my Framework again for a few weeks now, and no reboots have happened (fingers crossed).
Wow, this bug is persistent. Can you open a ticket with Framework about this? If I can repro I’ll do the same. Please encourage everyone else to do the same.
Might need to look at what changed between my current kernel and this new one. I am not having this yet on 6.14.9
CC @Matt_Hartley it appears the Ryzen AI 300 series boards also suffer from the Sync Flood issue. Please tell me that Framework engineers are aware of this and actively looking into it? This means every AMD board Framework has released suffers from this problem.
Yep, sometime around 6.13.7, one of those upgrades seemed to solve my Triple Fault issue. I have not had this problem since. I am currently running linux 6.14.10-arch1-1, core/linux-firmware 20250508.788aadc8-2, and core/amd-ucode 20250508.788aadc8-2.
However, I got tagged in this post the other day. I asked if they could check the S5_RESET_STATUS so we can be sure if it’s FTR or Triple Fault but they haven’t replied. I am guessing it is Sync Flood because of the version of Linux (6.14.9) they are running. I haven’t seen anybody overtly reporting the Triple Fault 0x00800800 yet, but the Ryzen AI 300 series boards are confirmed to be experiencing the Sync Flood 0x08000800.
I appreciate the attention on this. This Sync Flood issue is particularly nasty because it seems to affect any and all boards on any and all distros/kernels. This thread, as well as the others replied in, and the GitHub issues all have these reports. It seems like it’s hardware/firmware related. I fear that if it is not root caused by Framework engineering, whatever AMD board is released next will also have this issue. I’d suggest this thread be read and watched as the main Sync Flood thread.
Just like Matt mentioned, this issue is going to be my first focus of the day. Currently putting a fresh install of Arch on a Framework Laptop 13 Ryzen AI 300 series. Thanks a ton for sharing the GitHub issue and related threads, I’m gonna be pouring over those while I work on this.
I do share the sentiment most are sharing that it will still take a considerable amount of time to really narrow down the issue and give our engineers and AMD the information they need to act on this. We really appreciate everybody’s patience in the meantime. I hope we’re able to provide an update soon.
I’ve finally found a way to force this crash to happen essentially on demand with my hardware. I’m hoping we’re able to use that as a basis to find a fix for this issue, and with luck I’ll be able to deliver for information on this soon.
