Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910252
Title:
> /sys/power/image_size represents the required amount of space for the
image
no it doesn't:
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-power
"The kernel's suspend-to-disk code will do its best to ensure the image size
will not exceed this number. However, if it turns out to be
So I've done a little more testing. On boot, with /sys/power/resume
unset (i.e. 0:0), I see this in the logind debug logs:
Jan 08 09:47:11 surprise systemd-logind[1887]: Sleep mode "disk" is supported
by the kernel.
Jan 08 09:47:11 surprise systemd-logind[1887]: /dev/dm-2: is a candidate
And, for clarity, when systemd does hibernate, I haven't had issues
restoring: it's just getting systemd to find the correct swap space to
use that's been the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Thu, Jan 07, 2021 at 03:23:36PM -, Dimitri John Ledkov wrote:
> Also, you do disable secureboot as well right? Because with secureboot
> on, even though hybernation image is created, it will be ignored and
> not used upon resume.
Yep, Secure Boot is disabled on this system.
--
You
these things are very weird indeed.
Also, you do disable secureboot as well right? Because with secureboot on, even
though hybernation image is created, it will be ignored and not used upon
resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> So, looking at the systemd code at
https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared
/sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the
correct device actually was the workaround/fix?
The confusing part about this is that I don't
I enabled systemd-logind debug logging, and I saw:
Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call
sender=:1.264 destination=:1.220 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CanHibernate cookie=6
reply_cookie=0 signature=n/a
> $ cat /sys/power/resume
> 0:0
This was a red herring. What I have found consistently fixes this is:
$ sudo swapoff /dev/sda2
$ sudo swapon -p 1 /dev/sda2
Hibernate then succeeds. However, this is not how I want my system
configured: I have a small swap partition on my SSD, which I would
Oh, and `free -h`:
totalusedfree shared buff/cache available
Mem: 15Gi 6.0Gi 667Mi 567Mi 9.0Gi 8.8Gi
Swap: 98Gi13Mi98Gi
--
You received this bug notification because you are a member of Ubuntu
/sys/power/image_size represents the required amount of space for the
image; that said, the machine has 16G RAM total, so even if that were
maxed out, it would fit into 97.7G comfortably.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
and how much RAM does the system have? and how much is used? and of
swap?
free -h
free swap should be more then used memory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910252
Title:
One thing I have noticed, is that on boot:
$ cat /sys/power/resume
0:0
I can't test right now, but I _think_ that before the holiday break
setting that to 8:2[0] and restarting systemd-logind meant that
hibernate did then work.
[0] $ ls -l /sys/dev/block/8:2
lrwxrwxrwx 1 root root 0 Jan 5
13 matches
Mail list logo
