FW13 Return from s2idle causes reboot (S5_RESET_STATUS = 0x00800800) <- Triple Fault #50
Open
2 of 3 tasks
Labels
Comments
1 task
|
Hi. Context: |
|
Thanks for the ideas! I'll try yanking the SSD and wifi card when I have the time. It could take days of sleep/wake to find the issue. One pattern I notice is that it happens when I resume after sleeping for a long time (like 8 hours overnight) and then I can usually get it to happen very shortly after the first time, too. I don't have a dGPU, this is a FW13 and I mostly use it on the go. I'll update the issue. It would be nice if we could bisect the kernel to figure out if this was happening. From what I have seen online, it doesn't seem to be happening on 6.11, and was introduced sometime in 6.12. I guess I could try compiling the latest 6.11 kernel, and maybe the earliest 6.12 LTS kernel (because I know for a fact it happened there) |
|
Dropping by to add that I've been experiencing a similar issue (described here: https://community.frame.work/t/sudden-reboot-on-wake-with-no-logs/65434 ) I've experienced this on several kernels, being from Debian stable 6.1, backports 6.9 and 6.12, Liquorix 6.12, and mainline 6.14 rc4 (though I haven't checked what patches the Debian team is applying on their kernels, maybe they are backporting some bad patches?) I've heard that others with somewhat-similar issues on Arch could fix by downgrading Mesa to 24.x, but Debian stable ships 22, and updating to 24 did not help (crashes still occur) I have noticed that I can almost always prevent reboots by switching to a tty right as I open my laptop. I usually keep it there for a few seconds before switching back to tty1 with Plasma/Wayland. |
Sometimes I get reboots the instant I open my lid :( |
@jcdutton Can you say more about this? How would I see these messages if I'm not getting past my lockscreen before a reboot? Would they appear in a TTY? Would they appear in my dmesg? I'm now running |
|
@WillNilges |
|
This is related? I have a Ubuntu install, i will test it immediately, right after I wake up or something. |
|
@CDRXavier sounds very related, putting aside the OS's of choice/used. Nice seeing more and more people mention this and in various hardware setup/flavors, too! |
kiram9
added
Laptop 13 - AMD Ryzen 7040
|
Now, I don't think the Triple fault is coming from the Linux kernel. Alternatively, could this be caused by bit-flips, maybe going undetected due to lack of ECC in some data paths? I am just trying to think of some other things to investigate to track this down. |
Funny enough, i'm thinking the same. This is either something SMM, something the on-die ecc doesn't/can't catch, or, i can't even tell why, the mediatek wireless card freaking out with power management. The completely random pattern suggests the memory theory, i suppose. i.e. an electrical issue. |
|
I can safely (hopefully) say that, since the 14th, I am no longer experiencing this issue. I have no idea why. I am still using my self-built 6.14 rc4 kernel that I mentioned in the forum post. This is the contents of my /var/log/dpkg.log of all my package changes from that last triple-fault to today: I had no changes on the 14th itself, so this starts on the 15th. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Device Information
System Model or SKU
Please select one of the following
BIOS VERSION
Please provide the bios version.
03.05
Windows:
Open a command terminal as administrator:
wmic bios get SMBIOSBIOSVERSIONLinux:
Open a terminal and run the following command
sudo dmidecode --string bios-versionDIY Edition information
If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.
Memory: CRUCIAL CT32G56C46S5
Storage: SAMSUNG MZVL21T0HDLU-00BLL
Port/Peripheral information
If you are experiencing an issue with a peripheral or an expansion card/port please fill out the following information:
I have no dGPU, and the only things I regularly plug in are a monitor, keyboard, mouse, and mic via a docking station. Other than that I use it mostly on the go, and I have only ever seen the issue while the machine is not plugged into anything. (I have been able to reproduce the issue with/without the AC adapter)
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
Describe the bug
A clear and concise description of what the bug is.
Often (at least 1/3 times) when I come out of s2idle, my laptop screen will suddenly go black, then the machine will start up as if coming from a cold boot. Sometimes it happens slowly enough that I can unlock and get a browser open, sometimes it happens before I'm even done opening the lid.
I applied a kernel patch (see below) and the reset code is
Steps To Reproduce
Steps to reproduce the behavior:
You should see the crash by Step 4
Expected behavior
A clear and concise description of what you expected to happen.
I can use the laptop and sleep and wake as many times as I want without it crashing.
Screenshots
If applicable, add screenshots to help explain your problem.
Operating System (please complete the following information):
I have applied this patch to check my reset codes.
Additional context
Add any other context about the problem here.
This issue started around Feb 14, 2025. At the time I was running Linux LTS and it had upgraded to 6.12 when the issues started. I was on 6.6 since around December and it was fine.
I was directed to open this issue here: #41
This is my thread: https://community.frame.work/t/spontaneous-and-ungraceful-restarts-upon-closing-the-lid/64806
I saw this thread about what seems to be the exact same issue: https://community.frame.work/t/framework-13-amd-return-from-sleep-causes-reboot/64743/16
Possibly these folks as well: https://community.frame.work/t/responded-inconsistent-resume-from-suspend-linux-amd/46587
It would be nice to reach out to everybody in these threads and see if we could get some more information. I am also going to open a support ticket with Framework directly because they keep ignoring me on the forums.
The text was updated successfully, but these errors were encountered: