The reason I’m suspecting a charger is that maybe it’s putting the EC into some funny state and causing it to trigger SCI constantly with this GPE set.
To rule it out can you fully power off the machine, boot it up on battery and try without it plugged in? Hopefully the EC will be power cycled and this can be ruled out.
Sure.
I think what you are seeing here is an unrelated issue - if the laptop is in suspend, and you close the lid it wakes up. There is a workaround by adding a udev rule. More info in: [TRACKING] Framework AMD Ryzen 7040 Series lid wakeup behavior feedback - #54 by Gawdl3y
Apologies for the delay, new user here so restricted in how much I can post.
I unplugged the laptop then powered it off. Both installed Fedora KDE environment and live Fedora GNOME persisted with the same issue, so likely rules the power adapter out.
Not sure why, but my KDE env shows EN STS enabled, unmasked on a fresh boot while the live GNOME env shows STS disabled, unmasked for gpe1A. In both cases, enormous number of gpe1A interrupts (seems to get higher quicker on the KDE env).
I am running into the same issues as @sheern. In my case it is gpe0B. I am running Kubuntu on the framework 13. I have 2 USB-C’s in the left slot, and 1 HDMI and 1 USB-A in the right.
My laptop was in my backpack for 24 hours and the battery was almost completely depleted while in sleep. I can´t figure out what it is at this time. Running BIOS 3.03. Any help would be appreciated.
echo "mask" | sudo tee /sys/firmware/acpi/interrupts/gpeXX
Masking the offending interrupt has helped with the sleep drain issue. Unfortunately, support wasn’t able to replicate the issue so the cause is unclear.