Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

Michal Suchanek hramrach at gmail.com
Sun Oct 22 13:48:03 BST 2017


On 22 October 2017 at 14:14, Michael Biebl <biebl at debian.org> wrote:
> Am 22.10.2017 um 13:43 schrieb Michal Suchanek:

> Please try downgrading the kernel to the previous version and report back.

Downgrading the kernel is not really an option. It was broken so I did
not keep a backup and the build is gone from the archives.

> That said, you can enable persistent journal by creating the directory
> following the instructions in /usr/share/doc/systemd/README.Debian.gz

I will keep that filed in case I do have some logs to collect.

>> However, I noticed that I have hibernate logs and comparing earlier
>> hibernate logs with recent ones I can see that earlier logs have an
>> error saying the s2d device is not available while recent hibernate
>> logs say the system was suspended to disk.
>> Disabling any suspend methods in hibernate resolves the problem.
> What exactly did you disable and how?

All suspend methods in /etc/hibernate.conf

> Are you using the hibernate tool from the "hibernate" package?

I would not say exactly using. I have it installed and hooked to the
acpid scripts but long time ago when I upgraded to Debian version that
requires systemd it stopped working because systemd took over handling
the power key.

Now it is obviously hooked to something somewhere again because it
runs in parallel to the systemd power button handling.

This is quite unfortunate. I am not aware of doing anything that would
re-enable it. My expectation is that only one package handles power



More information about the Pkg-systemd-maintainers mailing list