Something is killing my PC at nite

still trying to figure out why suspend/resume is not working like it is supposed to on this PC

  • systemd stuff (suspend and hibernate) works as expected when called from the command line

  • plasma automatically goes to sleep (S3) and wakes up during the daytime just without any obvious issues

but nearly every nite (esp when there are discover updates) the PC will not only lock up tight forcing me to cycle the power, but it also somehow corrupts my BIOS forcing me to reset or reflash the CMOS before it will boot.

i’ve filed bug reports on this, but because plasma 6.1 is not officially supported there is no help there.

in the meantime i’ve just now turned off automatic updates, statistics, and user feedback in the hopes that it might be one of those processes in the middle of the nite that is killing my machine.

here is the sudo journalctl -b -1 from last nite as i woke it just long enough to see if it was still working and let it go back to sleep on it’s own… the next morning it was unresponsive … if there is any clue in here please help me find it.

specs

Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-14-generic (64-bit)
Graphics Platform: X11
Processors: 28 × Intel® Core™ i7-14700K
Memory: 62.6 GiB of RAM
Graphics Processor: AMD Radeon RX 6800
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D27
System Version: 1.0

UPDATE: since booted to windows and waded thru a ton of updates as well as a file system repair on one of my data partitions that was throwing errors in dolphin.

also paused updates in windows for 35 days (max allowed) just in case windows was trying to take over my sleeping linux in the middle of the nite.

still happened again this morning… had to re-flash the BIOS back to an earlier version (H) and re-enter all my BIOS settings.

could there be some bad communication between plasma and the ACPI of the firmware taking place?

as i’ve stated before, i can run the systemd command line for suspend and hibernate and everything seems to work, but if i let plasma just go to sleep for too long (over nite) it won’t wake up.

not only will it not wake up but the whole computer is unresponsive, i can only get the ram to light up by pressing the power button.

Try shutting the machine off overnight, so all the updates happen when you start up again in the morning, so maybe you can see which one causes the problems.

does it happen while booted into windows overnight?

i’ve taken to not using the plasma sleep function at all (do nothing), and writing my own script to run systemctl suspend-then-hibernate

this seems to be working fine, so there is something wrong with the way plasma is evoking the suspend function, or when it’s in that state it’s vulnerable to some other process trying (and failing) to wake it and put it back into suspend.

this does not happen with windows as “sleep” there just puts the whole thing into hibernation without any suspend step at all.

the acpi of my firmware only seems to support (S4) hibernation, so the fact that it can suspend to RAM (S3) at all in linux is kind of amazing.