Hey guys. I’ve been having an ongoing problem with my desktop where, when it goes into suspend, it’ll shut down instead of waking back up. Not a hard shutdown, either, but what appears to be a proper shutdown where everything gets nicely SIGTERM’d and everything.
Now, I’m saying all that just in case it’s related to what happened today. I stepped away from my machine after having it play Youtube videos through the night and came back to it about an hour later to find that it had been shut down. There was no indication of an improper shutdown, either, since the usual “hey, you hard powered off and now your disk needs to be fsck’d” messages weren’t there. The logs stop right before when I assume the shutdown happened, but there’s nothing in them that really sticks out as a possible reason for why it would have happened.
Getting to the point, is there somewhere other than journalctl and dmesg that I should be looking to try and figure out what happened? I’m on Fedora 43, and I’m happy to provide whatever logs are necessary. I’m really hoping it’s not a hardware fault, but I’ve had other problems that seem to indicate the PCIe port on my motherboard starting to go bad such as inexplicable static on one monitor and my GPU disconnecting whenever my cat jumps down from my lap too hard.
Which logs did you look at already?
If you’re using journalctl, I think you should have shutdown messages in the log. You might need to filter by the previous boot for them though (https://linuxhandbook.com/journalctl-boot-logs/).
For dmesg, you might have old, rotated logs from previous boots in your /var/logs folder.
I’d expect any logs around power management to end up in one or both of those places.
You could also try manually triggering a suspend or hibernate to see what happens. I remember having a machine that would suspend fine, but if it was suspended too long, it would hibernate. And for some reason it didn’t know how to come back up after a hibernate.