On Mon Dec09'24 04:32:00PM, Patrick O'Callaghan wrote: > From: Patrick O'Callaghan <pocallaghan@xxxxxxxxx> > Date: Mon, 09 Dec 2024 16:32:00 +0000 > To: users@xxxxxxxxxxxxxxxxxxxxxxx > Reply-To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > Subject: Re: new F41 install: is swap partition no longer needed for > hibernate? > > On Mon, 2024-12-09 at 07:29 -0600, Ranjan Maitra via users wrote: > > On Mon Dec09'24 12:38:54PM, Patrick O'Callaghan wrote: > > > From: Patrick O'Callaghan <pocallaghan@xxxxxxxxx> > > > Date: Mon, 09 Dec 2024 12:38:54 +0000 > > > To: users@xxxxxxxxxxxxxxxxxxxxxxx > > > Reply-To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > > > Subject: Re: new F41 install: is swap partition no longer needed for > > > hibernate? > > > > > > On Mon, 2024-12-09 at 06:31 -0600, Ranjan Maitra via users wrote: > > > > I don't understand what this could be, and wonder what the issue could be? > > > > > > Check the journal, e.g. 'journalctl -g hibernate'. Maybe also: > > > > Thank you! Here is the thing: I get nothing different from both entries, that i can see, except for the time: it is back in 3 s. For example: > > > > > > Dec 09 07:12:24 localhost systemd-logind[1285]: The system will hibernate now! > > Dec 09 07:12:24 localhost systemd[1]: Starting systemd-hibernate.service - System Hibernate... > > Dec 09 07:12:24 localhost systemd-sleep[2547]: in suspend-then-hibernate operations or setups with encrypted home directories. > > Dec 09 07:12:24 localhost systemd-sleep[2547]: Performing sleep operation 'hibernate'... > > Dec 09 07:12:28 localhost systemd-sleep[2547]: System returned from sleep operation 'hibernate'. > > Dec 09 07:12:28 localhost systemd[1]: systemd-hibernate.service: Deactivated successfully. > > Dec 09 07:12:28 localhost systemd[1]: Finished systemd-hibernate.service - System Hibernate. > > Dec 09 07:12:28 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > Dec 09 07:12:28 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > Dec 09 07:12:28 localhost kernel: audit: type=1130 audit(1733749948.243:168): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > Dec 09 07:12:28 localhost kernel: audit: type=1131 audit(1733749948.243:169): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > Dec 09 07:12:28 localhost systemd[1]: Reached target hibernate.target - System Hibernation. > > Dec 09 07:12:28 localhost systemd-logind[1285]: Operation 'hibernate' finished. > > Dec 09 07:12:28 localhost systemd[1]: Stopped target hibernate.target - System Hibernation. > > > > > $ systemctl list-units --failed > > > > UNIT LOAD ACTIVE SUB DESCRIPTION > > > > 0 loaded units listed. > > > > > > Any other things I can look into? > > Nothing that occurs to me. It looks like the system is hibernating and > immediately waking up again, so I'd wonder if there's a hardware > element. > > If you do a hard restart i.e. remove power power completely (e.g. > remove the battery if it's a laptop, or pull the power cord if it's a > desktop), does the hibernate/resume work as expected? Does it work the > first time, but not at subsequent times? I don't think it is very easy to remove the battery but I can take a careful look. > Not sure what else I can suggest other than looking at the BIOS > settings. If you still have a Windows partition, maybe try that and see > if has the same behaviour. I do not have anything other than Fedora installed. It seems to me to be strange that it reliably comes back the first time, but not in future times. Something is being triggered from the second time on. It could have been H/W but why this reliability in the first run? Perhaps I do not know, but would that have not rule it out? Perhaps someone else would have some more ideas on what to look for. Many thanks again, and best wishes, Ranjan -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
