syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"

[Gerald Gilbert-Thorple]

When I close the lid on my laptop, syslog goes crazy with the message

systemd-logind: hibernation is restricted; see man kernel_lockdown.7

repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04.

[Gerald Gilbert-Thorple (gxgilthor)]

by unmasking sleep.target suspend.target hibernate.target hybrid-sleep.target, and allowing for suspend on lid closure in login.conf, I was able to make the problem go away, but why should I be forced to this?

[Dan Streetman (ddstreet)]

> by unmasking

those targets don't come masked by default, how did they get masked?

[Gerald Gilbert-Thorple (gxgilthor)]

That's right, I masked them by hand following some advice on the internet for how to make systemd stop suspending, since it was not responding to settings in login.conf even after restating logind
service.

Regardless of my motivation, it seems buggy that changing these settings should lead to such undesirable behavior.

[dev (darkraspberry)]

I am affected with this. My kernel yells "Lockdown: systemd[1]: hibernation is restricted; see man kernel_lockdown.7" during boot.

And make my system impossible to boot. Some day it take time upto 10 MIN.

[Launchpad Janitor (janitor)]

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

[JP Guisset (ubuntuforums-jpgu)]

I am using an old laptop as server. The internal screen has been removed. When no external display is connected, the system quickly goes to sleep mode. To avoid this I had masked sleep.target and suspend.target, which resulted in the described repeated "systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and 80% load by systemd-logind.

I could avoid suspend without triggering this issue by modifying /etc/systemd/logind.conf:
 HandleSuspendKey=ignore
 HandleHibernateKey=ignore
 HandleLidSwitch=ignore
 HandleHibernateKey=ignore

[Max (bubuta)]

I see those messages as well although in my case all the sleep.target suspend.target hibernate.target hybrid-sleep.target targets are unmasked. Note: I'm not trying to suspend or hybernate, the laptop is running on external power. Is there a way to figure out what's causing those messages?

[Dan Streetman (ddstreet)]

this message comes from the kernel, not systemd.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1896137

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Leonard/Janis (ljrk)]

This issue arises whenever system-logind access the `/sys/power/disk` file. Reproduce using `cat /sys/power/disk` and you'll find

    kernel: Lockdown: cat: hibernation is restricted; see man kernel_lockdown.7

in the kernel log. This is per-se harmless but does flood the log with garbage.