Bug#749832: systemd: ignores /run/do-not-hibernate, hibernates after kernel update

[Michael Biebl]

On Thu, 29 May 2014 19:11:25 -0700 Nikolaus Rath <Nikolaus at rath.org> wrote:
> Package: systemd
> Version: 204-8
> Severity: grave
> Justification: causes non-serious data loss
> 
> 'systemctl hibernate' (and probably other methods to hibernate when
> systemd is installed, I tested only the command) hibernates the system
> even if a new kernel package has been installed and /vmlinuz no longer
> points to the currently running kernel.
> 
> If this happens, and the system is booted again, the bootloader will
> load the new kernel, and then try to resume using the image stored by
> the old kernel. As far as I can tell, the system then marks the
> hibernation image as broken, reboots automatically and, on the second
> attempt, boots the system using the new kernel without resuming. At this
> point, any data that was available in the hibernated session but not
> written to disk is lost.
> 
> Prior to installing systemd, hibernating was not possible after a kernel
> update. I believe the mechanism to prevent it was a
> /run/do-not-hibernate file that is not used by systemd.

Is there a distro-agnostic way to determine whether it's safe to
hibernate or not?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180721/8c63aca8/attachment-0002.sig>