If only suspend to RAM actually worked :-(
Regular comment readers will know that I have a bitter hatred of Microsoft and all its products - this extends to the latest generation of CPUs where MS appears to have used its monopolistic powers to bully lobby manufacturers to completely ditch hardware support for the 'S3' sleep state we knew as 'suspend to RAM' in favour of Microsoft's catchily named 'S0ix' a.k.a. 'Modern Standby'... This has the objective of making standby near-instant because, shocker, S0ix isn't really standby but instead pushes full responsibility onto the OS to pretend to sleep by suspending services and/or switching them in to power-saving modes.
This means that the relatively stable and quick alternative to hibernating to disk is no longer available on modern hardware. All my previous Lenovo laptops have happily suspended to RAM multiple times per day for months on end (sometimes after a few initial teething issues), however now my Laptop (a P14s Gen4 with an AMD Ryzen 7 PRO 7840U) comes out of my bag ranging from feeling warm to the touch, to scalding hot and completely dead. I am lucky to see an uptime of more than 30 days before something causes the machine to overheat and drain the battery when I'm not using it.
Rumour has it that this method of standby has caused a lot of pain and frustration for Windows users too, with many reporting similar issues of laptops cooking themselves whilst in standby. Certainly my latest corporate-issued Win 11 laptop seems to be begging for a charger every morning when I wake it up.
After a lot of pain (and a fair bit of swearing) I managed to isolate Bluetooth as the main cause of my pain on Ubuntu, although disabling it also means I then can't use it, but lately I found out that if I suspended after using my built-in cellular modem then this will wake the machine up and cook it in my bag. Basically, anything could wake the laptop up at any time because it's really still awake.
So the suggested alternative is hibernating to disk - great; except that I've since upgraded my RAM and have nowhere near enough swap space, plus hibernation is known to be problematic (not to mention fairly slow, and possibly still not ideal to be dumped onto NVMe/SSD storage) - At some point I'll get around to migrating to a bigger drive so I've at least got the option to try it.
Yet again this seems to me like Microsoft abusing its dominant position to force everyone to do things its way - In the same way they tried to force a tablet/touch-centric UI onto all users, they now want to force a tablet/phone style 'standby' onto everybody, even though laptops/desktops are arguably running far more complex tasks without the constraint of everything being an app in a sandbox. Why did they have to push for the removal of legacy S3 standby!?
Seriously, I don't mind nor care if they want to dabble with their own 'modern standby' implementation - good luck to them! But they should not be allowed to remove or break core hardware (and firmware) the ones relied upon by other users.
Where will this end? We've already got dedicated Microsoft buttons on our keyboards (thankfully just Windows keys on mine and no 'co-pilot' button), enforced 'upgrades' to TPM v2.0 because of Windows 11 requirements, Secure Boot (which last time I read about it was controlled entirely by Microsoft - e.g. non-MS OSes need to obtain a certificate from MS if they want to use it).
Back on topic - I can see the ability to cancel hibernation as being useful on those occasions when I put the machine to sleep and then remember something else I meant to do - this happens often. I'm just hoping that when I finally sort it out (which may also involve making a jump to Devuan Linux to rid myself of systemd) that hibernating to disk will work 100% of the time and won't take too long to sleep/resume.
