I enabled systemd-logind debug logging, and I saw: Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CanHibernate cookie=6 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported by the kernel. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate device. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with lower priority Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files matching resume config were found in /proc/swaps. Jan 06 17:45:18 surprise systemd-logind[73027]: Sent message type=method_return sender=n/a destination=:1.264 path=n/a interface=n/a member=n/a cookie=185 reply_cookie=6 signature=s error-name=n/a error-message=n/a Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CanHybridSleep cookie=7 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported by the kernel. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate device. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with lower priority Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files matching resume config were found in /proc/swaps.
However, after a reboot this morning, hibernation does seem to be working, and I instead see: Jan 07 09:29:37 surprise systemd-logind[1798]: Got message type=method_call sender=:1.125 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=Hibernate cookie=3 reply_cookie=0 signature=b error-name=n/a error-message=n/a Jan 07 09:29:37 surprise systemd-logind[1798]: Sleep mode "disk" is supported by the kernel. Jan 07 09:29:37 surprise systemd-logind[1798]: /dev/sda2: device matches configured resume settings. Jan 07 09:29:37 surprise systemd-logind[1798]: Hibernation will attempt to use swap entry with path: /dev/sda2, device: 8:2, offset: 0, priority: -3 Jan 07 09:29:37 surprise systemd-logind[1798]: Enough swap for hibernation, Active(anon)=3080788 kB, size=102401108 kB, used=0 kB, threshold=98% So it looks like the issue is that my resume device was not being detected correctly previously, meaning that priority was being used (which resulted in the wrong device being selected). So, looking at the systemd code at https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared /sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the correct device actually was the workaround/fix? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1910252 Title: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation" Status in systemd package in Ubuntu: New Bug description: I have plenty of swap space configured in my system: $ cat /sys/power/image_size 6642229248 # ~ 6.2GiB $ swapon NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 /dev/sda2 partition 97.7G 0B -3 But when I attempt to hibernate: $ sudo systemctl hibernate Failed to hibernate system via logind: Not enough swap space for hibernation I have the swap partition configured as my resume device in my kernel commandline: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 lrwxrwxrwx 1 root root 10 Jan 5 09:08 /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2 (I'm not really sure how to further debug my issue, any assistance would be appreciated!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 5 09:33:04 2021 InstallationDate: Installed on 2019-05-07 (608 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. ------ Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
