On 6/23/22 14:22, Ranjan Maitra wrote:
On Thu Jun23'22 10:57:55AM, Samuel Sieb wrote:
> From: Samuel Sieb <samuel(a)sieb.net>
> Date: Thu, 23 Jun 2022 10:57:55 -0700
> To: users(a)lists.fedoraproject.org
> Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
> Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from
> hibernate (post Thursday updates)
>
> 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.
Thanks!
My /home is encrypted, but not my / /boot /tmp, swap, etc which are separate partitions.
It has never been previously a problem: when we resume, I am not asked for my /home
encryption password.
> If you boot the previous kernel, does hibernation work? Make sure you pick
> it for both the hibernating and the resuming.
Not any longer. Here is the output with 5.17.4:
Ok, those are the same errors.
Just to be very clear, you booted with kernel 5.17.4, did a hibernate,
then when you turned it back on, you picked 5.17.4 again?
One thing that i have not been clear of is where it matters if the
headers are only from kernel-headers-5.18.4. The earlier kernel-headers is the only
kernel-related file in my system that gets updated. The other files (kernel-core,
kernel-modules, kernel) all get updated, keeping the current version and the last but one
version. I doubt that this makes a difference though that it has been so for years.
The headers are only if you need to compile something and you always
have the latest, it doesn't keep multiple versions.
Can you check the dnf history to see what packages were involved in that
update that possibly made it stop working?