[systemd-devel] systemd hibernator generator does not function on default Fedora install

James Hogarth james.hogarth at gmail.com
Mon Apr 18 22:19:54 UTC 2016


Hi all,

There's been some discussion today about the impact of
https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the problem
actually lies.

The issue lies specifically with hibernate and affects all Fedora systems
regardless of hardware (it's reproducible in a VM).

The hibernate image gets written to swap correctly
but hibernate-resume-generator.c looks specifically for 'resume' in
/proc/cmdline to determine a) if any check shoudl even happen and b) which
block device to check.

When Fedora is installed anaconda does not write a resume= line
to GRUB_CMDLINE_LINUX in /etc/default/grub or to the default kernel stanza
for grubby to later duplicate.

Dracut cmdline module does produce a resume= line but it appears this
occurs too late for the generator to pick up.

The end result is that without manual intervention to add an appropriate
resume= line it's impossible to resume from hibernation on Fedora, and the
critical battery behaviour (configured via /etc/Upower/Upower.conf and
visible in upower -d) is to HybridSleep.

Is it feasible for systemd to have the generator pick a swap image
regardless of resume being present or not? If so the dracut cmdline coming
later than the hibernate generator wouldn't be a problem.

Cheers,

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160418/5cd65a03/attachment.html>


More information about the systemd-devel mailing list