Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #949364
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#890950: Bug#902416: Bug#890950: RE: Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade |
| Date | 2019-03-11 01:00 +0100 |
| Message-ID | <xAgwi-AH-5@gated-at.bofh.it> (permalink) |
| References | (11 earlier) <w4UaR-8go-3@gated-at.bofh.it> <xAf7b-8gK-3@gated-at.bofh.it> <xAgwi-AH-7@gated-at.bofh.it> <vloAa-6FO-11@gated-at.bofh.it> <xAgwi-AH-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
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.
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#890950: RE: Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade Ben Hutchings <ben@decadent.org.uk> - 2019-03-10 23:30 +0100 Bug#890950: Bug#902416: Bug#890950: RE: Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade Ben Hutchings <ben@decadent.org.uk> - 2019-03-11 01:00 +0100
csiph-web