Hibernation does not work after upgrading from kernel 5.4 to 5.10 or from 5.4 to 5.15

[Killi]

Thanks again @Jim.B for your answers.

I have the following this post written by @FancierTech which seems somehow similar:

Hibernate doesn't work, shuts down instead

Reviving this topic as I don’t want to create the same one. Previously… 8 month ago I created a swap partition and noticed after that I could sleep or hibernate my PC. I hadn’t needed that feature before, but now when I needed it the problem came… The problem. I have two options on my PC (KDE): sleep and hibernate. When I press sleep the PC goes to sleep as expected and it’s ok, but when I press hibernate the PC simply shuts down, but much faster than usually (its recovering the journal at …

According to him the solution would be found on this post written by @Wollie :

Added swap partition, hibernation results in complete shutdown instead?

It looks like your resume function is not properly set. You need a swap partition entry in your /etc/fstab, then resume=UUID=place here the swap partition UUID somewhere after the first " in the line starting GRUB_CMDLINE_LINUX_DEFAULT=" of your /etc/default/grub and the resume hook set at the end of HOOKS=(base .... resume) within the brackets in your /etc/mkinitcpio.conf. At the end run sudo mkinitcpio -P sudo update-grub and reboot.

My /etc/fstab is the following:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=CB2B-F14D                            /boot/efi      vfat    defaults,noatime 0 2
UUID=9bb57f6c-3448-4344-b74a-4bf0077ff48a /              ext4    defaults,noatime 0 1
UUID=0ad0883f-6f99-4b41-b4c7-2bc76822afb5 /home          ext4    defaults,noatime 0 2
/swapfile none swap defaults 0 0
UUID=24718325-ae45-4a9e-a52d-6a6b91d976b2 /home/ricardo/Supplément/ ext4 defaults,noatime 0 2

The swapfile is mentioned so it could be good.

My /etc/default/grub is the following:

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet udev.log_priority=3"
GRUB_CMDLINE_LINUX="quiet resume=UUID=9bb57f6c-3448-4344-b74a-4bf0077ff48a resume_offset=2916352"

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter 
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" 
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
#GRUB_DISABLE_OS_PROBER=false

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper 
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
GRUB_BACKGROUND="/usr/share/grub/background.png"
#GRUB_THEME="/path/to/gfxtheme"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true

This line is present so it should be also good: GRUB_CMDLINE_LINUX="quiet resume=UUID=9bb57f6c-3448-4344-b74a-4bf0077ff48a resume_offset=2916352"

I have not checked that the UUID number is the right one, but since it works currently with my 5.4 kernel it should be the right one, shouldn’t it?

My /etc/mkinitcpio.conf is the following:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"

In my /etc/mkinitcpio.conf I can see that the resume hook is not set at the end of the end of the parenthesis. According to this @Wollie post, the problem could be here but I cannot still understand why it works with the 5.4 kernel and not with the 5.10 nor with the 5.15 ones.

Wanting to have more information on this resume function before adding it at the end of the hooks list in my /etc/mkinitcpio.conf, I can just see the following information running

$ mkinitcpio -H resume

==> Help for hook 'resume':
This hook initializes support for resuming from Disk.  Supports swsusp and
suspend2.

==> This hook has runtime scripts:
  -> pre-mount hook

Finally, it gives me not so much more information… Is there a risk to try to add resume at the end of the hooks list?

Thanks a lot for your attention!