# Lost hibernation and suspend functions with new kernel **URL:** \ **Category:** Rocky Linux Help & Support\ **Tags:** rocky-linux-9\ **Created:** [November 25, 2023, 6:02pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991 "2023-11-25T18:02:06Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 25, 2023, 6:02pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/1 "2023-11-25T18:02:06Z")
After upgrading from Rocky Linux 9.2 to 9.3 I’ve completely lost the suspend and the hibernation functions. That’s a real shame because before, with the older kernel, I’d reached an uptime of 36 days with my laptop… In the logs I see, for example: `integrity: Problem loading X.509 certificate -126` and: `Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7` but I wonder whether they even concern my problem or not… When I manage to boot with the older kernel (and that’s not so easy, since I don’t see a menu at boot time!), the problem disappear. Thanks a lot for your ideas, Francesco ---
**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\ **Post date:** [November 25, 2023, 7:35pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/2 "2023-11-25T19:35:29Z")
Disabling hibernation is a “feature” of kernel\_lockdown. As far as I can tell the only way to disable this is to either set up an encrypted swap file or disable secure boot altogether. The first method might work, the second will probably work. ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 25, 2023, 8:02pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/3 "2023-11-25T20:02:37Z")
Thank @FrankCox . I did try to disable secure boot in UEFI but nothing changed, and I wouldn’t know where to start to encrypt my swap! It is strange though that I seem to be the only one hit by this: am I the only fool using Rocky on a laptop? Has this `kernel_lockdown` option appeared only in the newer `5.14.0-362.8.1.el9_3.x86_64` kernel? ---
**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\ **Post date:** [November 25, 2023, 8:35pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/4 "2023-11-25T20:35:02Z")
Maybe this article would be of interest. > **[How To Disable Kernel Lockdown on Ubuntu 18.04 for USB Device Access |...](https://devicetests.com/disable-kernel-lockdown-ubuntu-18-04-usb-access)** > > Master Ubuntu 18.04: Unlock USB device access by disabling kernel lockdown. Optimize your Ubuntu experience with our step-by-step guide. I just checked the contents of /sys/kernel/security/lockdown on this Rocky 8.9 system and it tells me this: $ cat /sys/kernel/security/lockdown [none] integrity Which is interesting. I’ve never looked at this before at all. > [@firminmaillard](#): > > Has this `kernel_lockdown` option appeared only in the newer `5.14.0-362.8.1.el9_3.x86_64` kernel? I think it’s the first time it’s been enabled by default. As shown above it seems to exist in some form in Rocky 8.9 but it doesn’t appear to be doing anything. ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 25, 2023, 9:03pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/5 "2023-11-25T21:03:43Z")
> [@FrankCox](#): > > cat /sys/kernel/security/lockdown this is what I get: ```auto [francesco@localhost ~]$ cat /sys/kernel/security/lockdown none [integrity] confidentiality ``` I should try to set it to `none`, but ```auto [root@localhost ~]# sysctl kernel.security.lockdown=none sysctl: cannot stat /proc/sys/kernel/security/lockdown: No such file or directory ``` ---
**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\ **Post date:** [November 25, 2023, 9:51pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/6 "2023-11-25T21:51:44Z")
What is your grub comandline? ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 25, 2023, 9:57pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/7 "2023-11-25T21:57:55Z")
I’m sorry, but what do you mean? How can I check that for you? ---
**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\ **Post date:** [November 25, 2023, 10:18pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/8 "2023-11-25T22:18:04Z")
The easiest way is cat /proc/cmdline ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 25, 2023, 10:22pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/9 "2023-11-25T22:22:13Z")
> [@FrankCox](#): > > cat /proc/cmdline Right, this what I get: ```auto [root@localhost ~]# cat /proc/cmdline BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-362.8.1.el9_3.x86_64 root=/dev/mapper/rl_localhost--live-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rl_localhost--live-swap rd.lvm.lv=rl_localhost-live/root rd.lvm.lv=rl_localhost-live/swap rhgb quiet ``` ---
**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\ **Post date:** [November 26, 2023, 4:19am UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/10 "2023-11-26T04:19:30Z")
Well that’s interesting. Apparently this lockdown thing doesn’t work the way I thought it did. Which goes to show how far I get when I make assumptions. I’ve never encountered this before so this is a whole new learning experience. Have you tried ```auto sysctl kernel.lockdown=0 ``` If so, what does ```auto cat /sys/kernel/security/lockdown ``` show you after that? Furthermore, I just found this: > **["Lockdown: X: Y is restricted, see man kernel\_lockdown.7" messages in the...](https://access.redhat.com/solutions/6969947)** > > Below kernel messages logged in /var/log/messages & dmesg Lockdown: rhsmcertd-worke: /dev/mem,kmem,port is restricted; see man kernel\_lockdown.7 Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel\_lockdown.7 Lockdown: sosreport:... Which contains this bit of information: “Contact hardware vendor to disable `Secure Boot` in the server `BIOS`. There is no other way to disable the feature.” If that means what it says then it appears the only way to disable the kernel lockdown is to disable the secure boot altogether. Which seems insane. ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 26, 2023, 1:19pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/11 "2023-11-26T13:19:01Z")
> [@FrankCox](#): > > Have you tried > > ```auto > sysctl kernel.lockdown=0 > > ``` I have tried, but I only get: ```auto [root@localhost ~]# sysctl kernel.lockdown=0 sysctl: cannot stat /proc/sys/kernel/lockdown: No such file or directory ``` ---
**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\ **Post date:** [November 26, 2023, 4:32pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/12 "2023-11-26T16:32:21Z")
If so, what does ```auto cat /sys/kernel/security/lockdown ``` show you after that? [/quote] ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 26, 2023, 6:42pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/13 "2023-11-26T18:42:36Z")
> [@FrankCox](#): > > If so, what does > > ```auto > cat /sys/kernel/security/lockdown > > ``` This is what I get: ```auto [francesco@localhost ~]$ cat /sys/kernel/security/lockdown none [integrity] confidentiality ``` even if I’m now using ```auto [francesco@localhost ~]$ uname -a Linux localhost.localdomain 5.14.0-284.30.1.el9_2.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Sep 16 09:55:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` from Rocky Linux 9.2 and I can perform a suspend without any issue! Shall I try to install another, supported (since this one it isn’t), kernel? ---
**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\ **Post date:** [November 26, 2023, 7:02pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/14 "2023-11-26T19:02:15Z")
It seems somehow relevant to me that /sys/kernel/security/lockdown exists but /proc/sys/kernel/lockdown doesn’t, even though that’s apparently what the sysctl command is trying to use/change. If /proc/sys/kernel/lockdown doesn’t exist, why is sysctl looking for it? /proc/sys/kernel/lockdown doesn’t exist on my Rocky 8.9 system either so it’s not something that just disappeared. Unfortunately I can’t tell you what any of this means. My best guess is that it’s either a bug in sysctl or whatever sysctl is using to determine what file to call, or someone upstream decided to yank that functionality away and didn’t update sysctl to remove it completely. None of which actually solves your problem. In accordance with the last link I posted above, I suggest that you disable secure boot completely and then you will be able to use the latest kernel. I think. This seems like telling someone who wants to install an air conditioner that he’ll have to smash all of the glass out of the windows in his house first. Someone must think this is a good idea but I really can’t see it. ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 26, 2023, 7:34pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/15 "2023-11-26T19:34:15Z")
I did try to disable secure boot, and even UEFI - going back to legacy boot - but that didn’t resolve the problem. I think that I’ll try to install a maintained kernel from the **Community Enterprise Linux Repository** , and see how it goes. In any case, that you very much for your help, @FrankCox ! ---
**Author:** ![firminmaillard](https://avatars.discourse-cdn.com/v4/letter/f/e495f1/32.png) [@firminmaillard](https://forums.rockylinux.org/u/firminmaillard)\ **Post date:** [November 26, 2023, 8:33pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/16 "2023-11-26T20:33:23Z")
Right, I’ve installed the kernel-lt (6.13) from ELRepo and I can suspend the laptop all right. I guess that’s because here, `lockdown` is set on `none`: ```auto [root@localhost ~]# cat /sys/kernel/security/lockdown [none] integrity confidentiality ``` Maybe one day I’ll be able to come back to the official kernel… who knows? ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [January 25, 2024, 8:33pm UTC](https://forums.rockylinux.org/t/lost-hibernation-and-suspend-functions-with-new-kernel/11991/17 "2024-01-25T20:33:32Z")
Closed on January 25, 2024, 8:33pm UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.