On 6/23/22 05:13, Ranjan Maitra wrote:
> That would correspond to the logs
> that you're showing there. The other thing to check is the last bit of the
> logs from the previous boot.
>
> I also suggest looking at some lines in that area that might not have been
> caught by the grep. Maybe there is a reason listed for why the resume
> failed.
Here is the complete journalctl output (after a new boot, since I think that journalctl
restarts?). Perhaps I should be looking at other messages?
Here's the problem:
Jun 23 06:47:25 localhost.localdomain kernel: PM: Loading and
decompressing image data (1505529 pages)...
Jun 23 06:47:25 localhost.localdomain kernel: Hibernate inconsistent
memory map detected!
Jun 23 06:47:25 localhost.localdomain kernel: PM: hibernation: Image
mismatch: architecture specific data
Jun 23 06:47:25 localhost.localdomain kernel: PM: hibernation: Read
6022116 kbytes in 0.01 seconds (602211.60 MB/s)
Jun 23 06:47:25 localhost.localdomain kernel: PM: Error -1 resuming
Jun 23 06:47:25 localhost.localdomain kernel: PM: hibernation: Failed to
load image, recovering.
Jun 23 06:47:25 localhost.localdomain kernel: PM: hibernation: Basic
memory bitmaps freed
Jun 23 06:47:25 localhost.localdomain kernel: Restarting tasks ... done.
Jun 23 06:47:25 localhost.localdomain kernel: PM: hibernation: resume
failed (-1)
I see a few references to that problem, but no clear solutions. It
seems to be either a BIOS issue or possibly related to using an
encrypted filesystem.
If you boot the previous kernel, does hibernation work? Make sure you
pick it for both the hibernating and the resuming.