On Wed, May 30, 2018 at 08:44:36AM +0100, Dave Mitchell wrote: > On Tue, May 29, 2018 at 08:12:39PM +0200, Wolfgang Pfeiffer wrote: > > > > On Mon, May 28, 2018 at 10:38:58PM +0100, Dave Mitchell wrote: > > > On Tue, Apr 17, 2018 at 10:26:22PM +0200, Wolfgang Pfeiffer wrote: > > > OP here - my UPower settings are the same as yours, and when I found time > > > to risk my battery getting down to 2% (I only tried to 4% originally), it > > > did indeed hibernate. Although it then immediately resumed :-( > > > > Resumed meaning it really "woke up", without your intervention like > > pressing a key or so? If yes I'd check the journalctl logs, because > > that seems a little strange to me. > > Yep. I get a 'critical alert' notification on the screen at 2%, then > the screen goes dark, followed by several seconds of disk activity light > flashing, then the screen turns on again, and I'm back where I was. > All without user intervention. > > > I had a similar situation a few days ago: I ran down battery until > > very low down. When the battery level was in what the system probably > > saw as critical (45%, something like that), it started > > sleep-hibernating (whatever the mix of these modes means), with > > journalctl writing (excerpt): > > > > Starting Hybrid Suspend+Hibernate... > > > > and seconds later: > > PM: Hibernation image created > > Here's a stripped-down log: > > [ ... ] > May 28 22:23:31 robin kernel: ACPI: Low-level resume complete > May 28 22:23:31 robin kernel: ACPI: EC: EC started > May 28 22:23:31 robin kernel: PM: Restoring platform NVS memory > May 28 22:23:31 robin kernel: Enabling non-boot CPUs ... > May 28 22:23:31 robin kernel: x86: Booting SMP configuration: > May 28 22:23:31 robin kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 > May 28 22:23:31 robin kernel: cache: parent cpu1 should not be sleeping > May 28 22:23:31 robin kernel: CPU1 is up >From these logs I cannot see why this did not work .. > NB - this laptop does a normal suspend/resume quite happily when closing > /opening lid. Same here: the only time this machine refuses to sleep (S3 sleep, different from the emergency hibernation from above, it seems) is when an external monitor is connected to the computer, via HDMI cable. You sure that there was nothing similar on your machine that might have prevented the emergency hibernate, by resuming immediately again? HTH Wolfgang _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/PFAZWOCHSLICZ4PQDNHZEL3OLVE4FCAZ/