Which kernel are you using? 6.18.5-200.fc43.x86_64
Which BIOS version are you using? 03.16
Which Framework Laptop 13 model are you using? AMD Ryzen™ 7040 Series
About twice a week, my laptop reboots suddenly while I’m using it. After reboot, the kernel log shows:
Previous system reset reason [0x08000800]: an uncorrected error caused a data fabric sync flood event
I’ve seen it most often while watching video (e.g. YouTube or Zoom in Firefox) and while connected to external monitors through my Plugable TB4 dock, HOWEVER it has also happened while using the laptop standalone, merely typing in a terminal.
This problem might be related to the FTR (freeze-then-reset) problem that @James3 has been tracking, but of course we’re all stabbing in the dark.
(This summary has been updated since originally posting, as new information has become available.)
I use both in Firefox, and I could try another browser, and I guess that would help us know whether it’s avoidable that way. Not really a long-term solution IMHO but a useful test. Thanks for the suggestion.
I have had issues with Zoom and Teams using Firefox. It is not the same issue as you. There is a Flatpak version of Chrome, so try that and see if its any different.
At a high level, this isn’t something we’re seeing reported broadly with our Thunderbolt docks.
We don’t officially support Linux with our docks, but we’d be happy to learn more.
If you’d like, please let us know the exact Plugable dock model you’re using and results from testing whether the issue ever occurs in another browser or when fully disconnected from the dock to help isolate further.
You can also contact our support team directly at support@plugable.com, if interested.
It’s been a great dock. I’ve even occasionally run two 4K monitors simultaneously at 60Hz, while still using the laptop panel as a third screen. I hot-plug the dock all the time, and GNOME remembers the monitor layout. It’s just fantastic.
I don’t know if the reboots have anything to do with the dock. I mentioned it because I’m not seeing reports like this, so I’m looking at what makes my system unique.
Since the reboots only happen once or twice a week, it’s hard to collect meaningful data, but it’s been going on long enough (a couple months) that I’d like to get to the bottom of it.
Thanks, I will. It would be useful to have a workaround, so I appreciate it. The reason for my lukewarm response is that I’d really like to go the other direction: Make it happen reliably and repeatably, and capture the necessary logging so that we can pursue the proper fix.
Ok. It sounds like you have something different then.
Another bit of data to gather could be with ectool.
Try “sudo ectool console” as soon after the reboot as you can, and post the logs here.
Ugh, it rebooted while I stepped away from my desk (no video involved) and I discovered I didn’t have ectool installed. Since I’m running bluefin, installing it involved another reboot.
Here’s the log, but it’s not fresh. I’ll capture more immediately after the reboot next time.
Hi,
That ectool console should be enough.
I was wondering if the EC was resetting itself for some reason, because this would switch off/reboot the laptop.
12170774 is how many seconds the EC has been up for, so the EC did not reset. It would be closer to zero if the EC had reset.
So, I don’t think your problem is EC related.
Another thing to look for, after the reboot, is lines in the syslog/journal log that say:
“x86/amd: Previous system reset reason…”
I think it might only be Kernel 6.18.x that have this message.
It can give some indication on why the laptop rebooted last time.
It only works with AMD CPUs, but you have a AMD CPU, so it should appear.
Previous system reset reason [0x00080800]: software wrote 0x6 to reset control register 0xCF9
I think that one is OK. It appears on my system when I ask the laptop to reboot with the “reboot” command or from the menus.
It at least shows that your kernel is outputting those useful messages already.
The problem one is: Previous system reset reason [0x08000800]: an uncorrected error caused a data fabric sync flood event
The “sync flood” one is the Freeze, then Reboot (FTR) one.
How long it freezes for, before the forced reboot, is configurable, so you might not see the 20 seconds freeze.
As you have seen the “sync flood” one.
We find this really difficult to reproduce, so any information about what you were doing at the time is useful. I generally find it happens when watching videos.
Other things that would be useful are, CPU/GPU utilization just before it happened. I have found that 4K video uses a lot of CPU/GPU, but 2K and below uses much much less.
RAM temps just before it happened are also useful, or if you look at the temps immediately after the FTR, RAM might still be warm.
The most recent reboot is an odd one, because the system was mostly idle. I had just stepped away from my computer to refill my coffee. There was no video playing.