Hi there,
I’ve been having this issue on Fedora 39, BIOS 3.02 - my Framework Laptop 16 wakes itself up from suspend, typically in <= 10 seconds after suspending. At one point my system even froze entirely after it did this, although I haven’t been able to reproduce the freezing, only the self-waking.
Let me know if there’s a better place to report this; I wasn’t entirely sure whether to reply here, or open a ticket, or follow the instructions from this Laptop 13 thread, so please let me know if there’s anything more I can do to help!
I ran amd_s2idle.py a couple times, with the same effect each time:
- Prints “Suspend cycle 1: Started at…”
- Screen goes dark
- Screen comes back in 2ish-5ish seconds (still signed in, even though I have Automatic Screen Lock turned on)
- Less than a second later, screen goes dark again very briefly, this time for no more than a second or two
- When it comes back, script crashes with
OSError: [Errno 16] Device or resource busy
I noticed the stack trace isn’t included in the report so I’ll attach below both the report and my stdout that includes the stack trace. (Actually, I’m having a hard time figuring out how to get the forum to accept the s2idle report file, so for now I’ll post a screenshot of its run, let me know how I can send the report if it would help)
Thanks so much to the Framework team for all your awesome hard work on this great laptop! If there’s anything else I can try please let me know.
Thanks,
Jonathan
Update
I have narrowed down this issue! It only happens while I have an Ethernet Expansion Card plugged in (in none of my tests did I have an ethernet cable plugged into the card; I’m not at my desk at the moment so I have no ethernet cable to plug in at this time). Removing the Expansion Card fixes my suspend issues.
I don’t plan to leave the Ethernet card in all the time anyway, so this is mostly fine for me, but it does mean I won’t be able to put my laptop to sleep while it’s “docked” at my desk without unplugging the expansion card, so I’m still happy to help provide more details or try new things to try and resolve the issue 
