Bug#902416: Bug#890950: RE: Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

[Ben Hutchings]

On Mon, 2019-03-11 at 00:20 +0100, Michael Biebl wrote:
> Hi Ben
> 
> Am 10.03.19 um 23:17 schrieb Ben Hutchings:
> > I think it would make sense for systemd to only set the hibernation
> > device if it's not already set (i.e. if /sys/power/resume contains
> > "0:0\n").
> 
> I get $ cat /sys/power/resume
> 8:4
> 
> which part is responsible for setting that?

initramfs-tools, or any alternative that implements resume from
hibernation.  This is because writing to /sys/power/resume is the way
to resume from hibernation, as well as the way to set the device for
the next hibernation.  (systemd writes the number of an active swap
device, so it won't cause an immediate resume.)

Ben.

-- 
Ben Hutchings
The program is absolutely right; therefore, the computer must be wrong.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190310/bc5b5221/attachment.sig>