On Mon, 6 Apr 2020 at 17:37, Markus Schaaf via arch-general
wrote:
> What I have found: It is unlikely that hibernation is the cause to the
> problem I have encountered. It is just the trigger. Somehow dm-integrity
> or dm-crypt manages to fuck up it's on-disk meta-data. (Meanwhile the
> same happ
On Sun, 12 Jan 2020 at 12:03, Justin Capella via arch-general <
arch-general@archlinux.org> wrote:
> Ah interesting. Do those memory regions match what is reported in
> proc/iomem prior to hibernating-- odd question but I recall someone on the
> irc encountering a difference.
Mmm that *is* inter
On Sun, 12 Jan 2020, 10:08 Justin Capella via arch-general, <
arch-general@archlinux.org> wrote:
>
> https://wiki.archlinux.org/index.php/Dm-crypt/Swap_encryption#With_suspend-to-disk_support
Nope; if that was the problem then the kernel would not see the resume data
at all, because the swap blo
I'm having trouble getting hibernation to work on my new Dell Inspiron
7590. It seems that the image is stored correctly (onto LUKS+LVM thin-lv),
but resume fails, with the following left in the kernel logs:
---
PM: Image signature found, resuming
PM: resume from hibernation
Freezing user space pr
4 matches
Mail list logo