We have been doing some work over here trying to track down the “Freeze then Reboot” problem.
We have discovered something interesting:
Note: when is says “Answer: …” it means someone from AMD provided the answer.
Value seen during a Freeze-then-reboot (FTR):
S5_RESET_STATUS = 0x08000800
Answer: Sync flood.
If it helps, the above S5_RESET_STATUS = 0x08000800
was seen on a:
Framework Laptop 13 powered by AMD Ryzen™ 7040 Series Processors:
Ryzen 7 7840U and Ryzen 5 7640U
And also a FW16 AMD 7840HS.
Explanation from AMD:
Bit 27 means this is a reboot due to “sync flood”. Here’s a description:
A drastic method of reporting errors in which a device transmits Sync
packets continuously until reset occurs. Each device on the chain that
detects the Sync flood repeats the pattern on all links. A reset is
required to recover from a Sync flood. Sync flood is analogous to SERR#
(System Error) on a PCI bus.
Debugging this will need to be done with a custom BIOS that disables
reboot on Syncflood so that the full state of the system could be
analyzed to characterize it.
In short; you unfortunately won’t be able to debug this any further
yourself; it needs to be done by Framework BIOS team.
The best thing you as an end user could do is find the pattern of
activity that’s tripping this (if there is one) so that Framework is
able to reproduce it.