SOLVED systemd-sleep[47832]: Failed to set EFI variable Hibe

linux_os2 · Last edited by linux_os2 on Wed Apr 24, 2024 6:11 pm; edited 4 times in total

Hi,

Since one of the last updates "hibernation" does not work anymore

followings is posted in journalctl:

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

Do you have efivars loaded/enabled in your kernel?

Best Regards,
Georgi

linux_os2 · Posted: Thu Apr 18, 2024 7:56 am Post subject:

linux_os2 · Posted: Thu Apr 18, 2024 8:49 am Post subject:

installed sys-apps/systemd-255.4: no succes
installed sys-apps/systemd-9999: no succes
installed sys-apps/systemd-255.4: no succes
rolled back to installed sys-apps/systemd-254.8-rc1: also no succes

booted backup of couple of days: hibernate ok
so my guess is that systemd is not responsible. or the patch does not work for me.

linux_os2 · Posted: Fri Apr 19, 2024 8:20 am Post subject:

restored a backup of 14/04/2024
upgraded system: no problem any more
so what happened ?????
any way put as SOLVED

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

What are the updates? If you still haven't updated world after the restore, could you post the output of

linux_os2 · Posted: Fri Apr 19, 2024 9:23 am Post subject:

linux_os2 · Posted: Fri Apr 19, 2024 1:44 pm Post subject:

Packages upgraded/reinstalled:

for me none of these packages could be responsible for th error

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

sys-apps/merge-usr ?

emerge --info please.

Best Regards,
Georgi

linux_os2 · Posted: Fri Apr 19, 2024 4:24 pm Post subject:

linux_os2 · Posted: Sun Apr 21, 2024 9:09 am Post subject:

linux_os2 · Posted: Sun Apr 21, 2024 10:29 am Post subject:

following updates were done

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

None of those can be related. Either there were other updates or the issue is intermittent. I don't see anything useful in dmesg either, which means it might not be kernel's fault.

You mentioned you updated the system after the restore, but it might be necessary to restart or login again for the issue to appear. Can you remember if you did that after the update?

How do you hibernate your system? More info on the system? Does `echo disk > /sys/power/state` work?

Best Regards,
Georgi

linux_os2 · Posted: Sun Apr 21, 2024 7:08 pm Post subject:

rebooted several times after the uprade.
an UPS is connected to the system and a script /etc/apcupsd/doshutdown is calling

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

Unfortunately I can't suggest anything more here. Here's my dmesg after systemctl hibernate: https://bpa.st/RJ2Q. I don't have this script you posted, but I doubt it matters.

Note that there's no mention of hibernate in your failed hibernate dmesg and no mention of resume image in your failed resume dmesg. Maybe restore from backup again and inspect dmesg output of working hibernate/resume scenario.

Best Regards,
Georgi

linux_os2 · Posted: Mon Apr 22, 2024 6:14 am Post subject:

linux_os2 · Posted: Mon Apr 22, 2024 4:30 pm Post subject:

removed the ubuntu partitions.
did restore of the efi partition
did factory restore of the firmware
ran memtest for 8 hours
did grub-mkconfig
no succes.

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

Found it: https://github.com/systemd/systemd/issues/32331

Username bears certain similarity with yours, if it was you, reopen it.

One more thing I could suggest is to inspect your emerge.log and see if you can emerge the version which was updated prior to the restore from backup, i.e. one before the one in the backup.

p.s. the earlier issue you linked mentions something about clearing a stale value from the variable, maybe you had it there all along and when it got cleared, you lost the ability to hibernate because it cannot be set.

p.s.2 I'm with 255.3

Best Regards,
Georgi

linux_os2 · Posted: Tue Apr 23, 2024 8:51 am Post subject:

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

I updated to 255.4 and didn't encounter the issue. I suspect it might be hardware support issue as your CPU model indicates it's an older computer.

However there's another clue in the pull request that introduced that feature: "for resume without kernel cmdline". I remember I looked into your dmesg and didn't see a resume kernel parameter. I have it set built into the kernel and for now I can't come up with easy enough solution to test it without having it set.

EDIT: I tested it, it doesn't break for me. Test it for yourself with resume kernel command line parameter and see what happens.

Just for reference: this is the commit, you can follow it to the pull request and the issue from there: https://github.com/systemd/systemd/commit/90efe8a6d4c0035c6a01d42805be87d99fb12f9a

It is the same commit in systemd and systemd-stable.

Best Regards,
Georgi

linux_os2 · Posted: Wed Apr 24, 2024 6:11 pm Post subject:

the resume kernel cmdline parameter used to be present, but strangely disappeared.
added resume=UUID=b4b1cbec-4e1f-4da7-88d7-5ebc50492090

now the "systemctl hibernate" works.
the resume is also ok.

thanks a lot.

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437

linux_os2 · Posted: Thu Apr 25, 2024 6:58 pm Post subject:

I am sure: did hibernate with and without the resume parameter,
thanks again.

e8root · Tux's lil' helper Joined: 09 Feb 2024 Posts: 94

Here is my hibernate script I made to not have to type systemctl each time I want to hibernate

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2437