I didn't mention it because I don't think it's a Framework issue (GP obviously doesn't have it) but rather my somehow messed up configuration of it, but the one problem I have with mine at the moment is that ten seconds or so after resuming (but not before) everything starts segfaulting, literally any command. And consequently logs don't get written to disk, so there's no record of it after I reboot it (with the physical button, necessarily) - so I'm having a hell of a time trying to debug it...
Oh wow. Indeed I haven't experienced this. How's the battery drain while suspended? I can't help but wonder if you get better suspend in exchange for...everything segfaulting.
I haven't noticed that it's been bad, but then I've had more to worry about... I have the same CPU (and, I thought the same config...) on my work laptop and no problem with battery drain there; I use 'hybrid-sleep' (suspend to swap & RAM, resume from the latter if possible but tolerate power loss).
It sounds like you might be using 'shallow' or 's2idle' (suspend to idle) sleep mode? You might need to write 'deep' to /sys/power/mem_sleep. (But don't listen to me, mine segfaults!)
