fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Many thanks and best wishes, Ranjan
On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra mlmaitra@gmx.com wrote:
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Is this a dual boot with Windows? Did you recently get firmware updates from Dell? Have you looked at messages using journalctl?
On Wed Jun22'22 11:40:10AM, George N. White III wrote:
From: "George N. White III" gnwiii@gmail.com Date: Wed, 22 Jun 2022 11:40:10 -0300 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra mlmaitra@gmx.com wrote:
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Is this a dual boot with Windows? Did you recently get firmware updates from Dell? Have you looked at messages using journalctl?
My apologies for overlooking such obvious necessary information. To answer your questions:
Is this a dual boot with Windows?
No, only runs Fedora since I bought it. I believe I wiped out all partitions when it came and put up Fedora (in 2018).
Did you recently get firmware updates from Dell?
No, sorry. I did not even check.
Have you looked at messages using journalctl?
So, I don't really know what to look for, but I tried:
journalctl | grep hibernate
and got:
Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume. Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4). Jun 22 06:06:50 localhost.localdomain systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: Deactivated successfully. Jun 22 06:06:50 localhost.localdomain systemd[1]: Finished systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605. Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Note however, that this is after the machine was asked to reboot since the system never came back from hibernate so I am not completely sure it has the information from not coming back.
Let me know what else I should look for.
Many thanks again and best wishes, Ranjan
On Wed, Jun 22, 2022 at 12:00 PM Ranjan Maitra mlmaitra@gmx.com wrote:
On Wed Jun22'22 11:40:10AM, George N. White III wrote:
From: "George N. White III" gnwiii@gmail.com Date: Wed, 22 Jun 2022 11:40:10 -0300 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users <
users@lists.fedoraproject.org>
Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra mlmaitra@gmx.com wrote:
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly
(and
upgraded when appropriate) using dnf on a cron job for the past few
years.
Sadly, after last Thursday's updates, the machine goes down fine (with
the
usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had
any
suggestions as to how I may diagnose and fix this problem.
Is this a dual boot with Windows? Did you recently get firmware updates from Dell? Have you looked at messages using journalctl?
My apologies for overlooking such obvious necessary information. To answer your questions:
Is this a dual boot with Windows?
No, only runs Fedora since I bought it. I believe I wiped out all partitions when it came and put up Fedora (in 2018).
Did you recently get firmware updates from Dell?
No, sorry. I did not even check.
Have you looked at messages using journalctl?
So, I don't really know what to look for, but I tried:
journalctl | grep hibernate
and got:
Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume. Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service
- Resume from hibernation using device
/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4).
Next chance, make
Searching for "systemd-hibernate-resume Could not resume from 'dev/disk/by-uuid" in the past year may give you some ideas. Interesting hit was https://www.suse.com/support/kb/doc/?id=000020264, which says:
Specifying to attempt resuming from a hibernation image should not normally result in a failure to boot. SUSE Support has observed cases in which it does. These include:
Security hardened systems Systems in which the swap device, root filesystem or /boot partition was not specified by UUID Otherwise improperly configured GRUB, such as duplicate resume= parameters Cases where the swap device was unreachable.
Jun 22 06:06:50 localhost.localdomain systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: Deactivated successfully.
Why is ASCII "minus/dash" (-) is shown as hex "\x2d"? I see similar entries on my Fedora 35 system.
Thanks!
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly
(and
upgraded when appropriate) using dnf on a cron job for the past few
years.
Sadly, after last Thursday's updates, the machine goes down fine (with
the
usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had
any
suggestions as to how I may diagnose and fix this problem.
Is this a dual boot with Windows? Did you recently get firmware updates from Dell? Have you looked at messages using journalctl?
My apologies for overlooking such obvious necessary information. To answer your questions:
Is this a dual boot with Windows?
No, only runs Fedora since I bought it. I believe I wiped out all partitions when it came and put up Fedora (in 2018).
Did you recently get firmware updates from Dell?
No, sorry. I did not even check.
Have you looked at messages using journalctl?
So, I don't really know what to look for, but I tried:
journalctl | grep hibernate
and got:
Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume. Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service
- Resume from hibernation using device
/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4).
Next chance, make
Searching for "systemd-hibernate-resume Could not resume from 'dev/disk/by-uuid" in the past year may give you some ideas. Interesting hit was https://www.suse.com/support/kb/doc/?id=000020264, which says:
Specifying to attempt resuming from a hibernation image should not normally result in a failure to boot.
I don't know what this means, but I do boot in, but not to the hibernated state, but a new one.
SUSE Support has observed cases in which it does. These include:
Security hardened systems Systems in which the swap device, root filesystem or /boot partitionwas not specified by UUID Otherwise improperly configured GRUB, such as duplicate resume= parameters Cases where the swap device was unreachable.
I have changed nothing for months, if not years. In any case, I am pretty certain the first three points are not true for me, and I have no idea as to how to see if the swap device is reachable or not.
Btw, I have noticed something, that the grub menu now has an entry for the kernel with debug as well as the kernel itself (which is what it boots into, and does not resume). Before last week (at least), there were not two entries: one for the kernel with debug and the other for the kernel only. I am not sure if this is relevant.
My /etc/default/grub is as follows:
GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="resume=UUID=a83ac239-cc10-43a6-be54-de4ce7050605 rhgb quiet" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true
It was last updated on May 5, 2019.
Jun 22 06:06:50 localhost.localdomain systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: Deactivated successfully.
Why is ASCII "minus/dash" (-) is shown as hex "\x2d"? I see similar entries on my Fedora 35 system.
Don't know, sorry.
Thanks again for your help and your suggestions, Ranjan
On 22 Jun 2022, at 21:38, George N. White III gnwiii@gmail.com wrote:
Why is ASCII "minus/dash" (-) is shown as hex "\x2d"? I see similar entries on my Fedora 35 system.
Systemd uses it as a directory separator in things like scope paths. (I don’t recall the full details when it’s needed) So if you need a literal - then you need to use the escape. I think it because using a / created a set of nasty issues, but may have that wrong.
Barry
On 6/22/22 07:59, Ranjan Maitra wrote:
On Wed Jun22'22 11:40:10AM, George N. White III wrote:
From: "George N. White III" gnwiii@gmail.com Date: Wed, 22 Jun 2022 11:40:10 -0300 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra mlmaitra@gmx.com wrote:
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Have you looked at messages using journalctl?
So, I don't really know what to look for, but I tried:
journalctl | grep hibernate
and got:
Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume. Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4). Jun 22 06:06:50 localhost.localdomain systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: Deactivated successfully. Jun 22 06:06:50 localhost.localdomain systemd[1]: Finished systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605. Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Note however, that this is after the machine was asked to reboot since the system never came back from hibernate so I am not completely sure it has the information from not coming back.
What do you mean "doesn't come back up"? Usually the problem is that you get a normal boot instead of a resume. 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.
Dear Sam,
Thank you for looking into this.
So, I don't really know what to look for, but I tried:
journalctl | grep hibernate
and got:
Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume. Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4). Jun 22 06:06:50 localhost.localdomain systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: Deactivated successfully. Jun 22 06:06:50 localhost.localdomain systemd[1]: Finished systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605. Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Note however, that this is after the machine was asked to reboot since the system never came back from hibernate so I am not completely sure it has the information from not coming back.
What do you mean "doesn't come back up"? Usually the problem is that you get a normal boot instead of a resume.
Yes, that is right, I get a normal boot instead of a resume, since last Thursday's updates.
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?
https://paste.centos.org/view/3519f018
Here is the output of:
sudo cat /var/log/messages | grep hibernate
https://paste.centos.org/view/b1f418a0
sudo cat /var/log/messages | grep resume
https://paste.centos.org/view/e7807a58
Thank you again for your help, and suggestions.
Best wishes, Ranjan
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.
On Thu Jun23'22 10:57:55AM, Samuel Sieb wrote:
From: Samuel Sieb samuel@sieb.net Date: Thu, 23 Jun 2022 10:57:55 -0700 To: users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@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:
journalctl
https://paste.centos.org/view/de6641db
sudo cat /var/log/messages | grep resume
https://paste.centos.org/view/3d24579b
sudo cat /var/log/messages | grep hibernate
https://paste.centos.org/view/cccda1fb
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.
Many thanks again for your help!
Best wishes, Ranjan
On 6/23/22 14:22, Ranjan Maitra wrote:
On Thu Jun23'22 10:57:55AM, Samuel Sieb wrote:
From: Samuel Sieb samuel@sieb.net Date: Thu, 23 Jun 2022 10:57:55 -0700 To: users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@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?
On Thu Jun23'22 02:44:00PM, Samuel Sieb wrote:
From: Samuel Sieb samuel@sieb.net Date: Thu, 23 Jun 2022 14:44:00 -0700 To: users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On 6/23/22 14:22, Ranjan Maitra wrote:
On Thu Jun23'22 10:57:55AM, Samuel Sieb wrote:
From: Samuel Sieb samuel@sieb.net Date: Thu, 23 Jun 2022 10:57:55 -0700 To: users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@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?
Yes, indeed! I was careful about this, because of what you wrote.
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?
Thanks! Here are the updates from last Wed and Thu:
-------------------------------------------------------------------------------- Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15 09:00:01 PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 09:00:01 PM CDT 2022 - Complete! Wed Jun 15 09:00:04 PM CDT 2022 - *** CHECKING FOR SYSTEM UPDATES *** Wed Jun 15 09:00:04 PM CDT 2022 - Copr repo for Signal-Desktop owned by luminoso 9.1 kB/s | 3.3 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - Adobe Systems Incorporated 8.4 kB/s | 2.9 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - Fedora 36 - x86_64 55 kB/s | 18 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - Fedora 36 openh264 (From Cisco) - x86_64 3.3 kB/s | 989 B 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - Fedora Modular 36 - x86_64 38 kB/s | 18 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - Fedora 36 - x86_64 - Updates 45 kB/s | 15 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - Fedora Modular 36 - x86_64 - Updates 48 kB/s | 15 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Free 5.3 kB/s | 2.7 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Free - Updates 10 kB/s | 2.7 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Nonfree 5.4 kB/s | 2.8 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Nonfree - Updates 11 kB/s | 2.7 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - teams 6.7 kB/s | 3.0 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:04 PM CDT 2022 - ================================================================================ Wed Jun 15 09:00:04 PM CDT 2022 - Package Arch Version Repository Size Wed Jun 15 09:00:04 PM CDT 2022 - ================================================================================ Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading: Wed Jun 15 09:00:04 PM CDT 2022 - ibus x86_64 1.5.26-9.fc36 updates 11 M Wed Jun 15 09:00:04 PM CDT 2022 - ibus-gtk2 x86_64 1.5.26-9.fc36 updates 27 k Wed Jun 15 09:00:04 PM CDT 2022 - ibus-gtk3 x86_64 1.5.26-9.fc36 updates 27 k Wed Jun 15 09:00:04 PM CDT 2022 - ibus-libs x86_64 1.5.26-9.fc36 updates 260 k Wed Jun 15 09:00:04 PM CDT 2022 - ibus-setup noarch 1.5.26-9.fc36 updates 60 k Wed Jun 15 09:00:04 PM CDT 2022 - libtool x86_64 2.4.7-1.fc36 updates 593 k Wed Jun 15 09:00:04 PM CDT 2022 - libtool-ltdl x86_64 2.4.7-1.fc36 updates 37 k Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c x86_64 3.2.7-1.fc36 updates 196 k Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c-config noarch 3.2.7-1.fc36 updates 9.5 k Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c-devel x86_64 3.2.7-1.fc36 updates 54 k Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c-doc noarch 3.2.7-1.fc36 updates 98 k Wed Jun 15 09:00:04 PM CDT 2022 - ostree-libs x86_64 2022.4-2.fc36 updates 433 k Wed Jun 15 09:00:04 PM CDT 2022 - perl-Date-Manip noarch 6.88-1.fc36 updates 1.0 M Wed Jun 15 09:00:04 PM CDT 2022 - tree x86_64 2.0.2-1.fc36 updates 57 k Wed Jun 15 09:00:04 PM CDT 2022 - Wed Jun 15 09:00:04 PM CDT 2022 - Transaction Summary Wed Jun 15 09:00:04 PM CDT 2022 - ================================================================================ Wed Jun 15 09:00:04 PM CDT 2022 - Upgrade 14 Packages Wed Jun 15 09:00:04 PM CDT 2022 - Wed Jun 15 09:00:04 PM CDT 2022 - Total download size: 14 M Wed Jun 15 09:00:04 PM CDT 2022 - Downloading Packages: Wed Jun 15 09:00:04 PM CDT 2022 - (1/14): ibus-gtk2-1.5.26-8.fc36_1.5.26-9.fc36.x 58 kB/s | 13 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (2/14): ibus-gtk3-1.5.26-8.fc36_1.5.26-9.fc36.x 53 kB/s | 12 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (3/14): ibus-libs-1.5.26-8.fc36_1.5.26-9.fc36.x 59 kB/s | 16 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (4/14): ibus-setup-1.5.26-8.fc36_1.5.26-9.fc36. 215 kB/s | 15 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - [DRPM 1/5] ibus-gtk2-1.5.26-8.fc36_1.5.26-9.fc36.x86_64.drpm: done Wed Jun 15 09:00:04 PM CDT 2022 - (5/14): ostree-libs-2022.3-3.fc36_2022.4-2.fc36 438 kB/s | 112 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - [DRPM 2/5] ibus-gtk3-1.5.26-8.fc36_1.5.26-9.fc36.x86_64.drpm: done Wed Jun 15 09:00:04 PM CDT 2022 - [DRPM 3/5] ibus-setup-1.5.26-8.fc36_1.5.26-9.fc36.noarch.drpm: done Wed Jun 15 09:00:04 PM CDT 2022 - (6/14): libtool-ltdl-2.4.7-1.fc36.x86_64.rpm 527 kB/s | 37 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (7/14): mariadb-connector-c-3.2.7-1.fc36.x86_64 819 kB/s | 196 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (8/14): mariadb-connector-c-config-3.2.7-1.fc36 138 kB/s | 9.5 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (9/14): mariadb-connector-c-devel-3.2.7-1.fc36. 608 kB/s | 54 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (10/14): mariadb-connector-c-doc-3.2.7-1.fc36.n 884 kB/s | 98 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (11/14): libtool-2.4.7-1.fc36.x86_64.rpm 663 kB/s | 593 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (12/14): tree-2.0.2-1.fc36.x86_64.rpm 768 kB/s | 57 kB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (13/14): perl-Date-Manip-6.88-1.fc36.noarch.rpm 1.7 MB/s | 1.0 MB 00:00 Wed Jun 15 09:00:04 PM CDT 2022 - (14/14): ibus-1.5.26-9.fc36.x86_64.rpm 635 kB/s | 11 MB 00:18 Wed Jun 15 09:00:04 PM CDT 2022 - [DRPM 4/5] ibus-libs-1.5.26-8.fc36_1.5.26-9.fc36.x86_64.drpm: done Wed Jun 15 09:00:04 PM CDT 2022 - [DRPM 5/5] ostree-libs-2022.3-3.fc36_2022.4-2.fc36.x86_64.drpm: done Wed Jun 15 09:00:04 PM CDT 2022 - -------------------------------------------------------------------------------- Wed Jun 15 09:00:04 PM CDT 2022 - Total 725 kB/s | 14 MB 00:19 Wed Jun 15 09:00:04 PM CDT 2022 - Delta RPMs reduced 14.3 MB of updates to 13.7 MB (4.4% saved) Wed Jun 15 09:00:04 PM CDT 2022 - Running transaction check Wed Jun 15 09:00:04 PM CDT 2022 - Transaction check succeeded. Wed Jun 15 09:00:04 PM CDT 2022 - Running transaction test Wed Jun 15 09:00:04 PM CDT 2022 - Transaction test succeeded. Wed Jun 15 09:00:04 PM CDT 2022 - Running transaction Wed Jun 15 09:00:04 PM CDT 2022 - Preparing : 1/1 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : ibus-libs-1.5.26-9.fc36.x86_64 1/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : ibus-gtk2-1.5.26-9.fc36.x86_64 2/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : ibus-gtk3-1.5.26-9.fc36.x86_64 3/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : ibus-setup-1.5.26-9.fc36.noarch 4/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : ibus-1.5.26-9.fc36.x86_64 5/28 Wed Jun 15 09:00:04 PM CDT 2022 - Running scriptlet: ibus-1.5.26-9.fc36.x86_64 5/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : mariadb-connector-c-config-3.2.7-1.fc36.noarch 6/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : mariadb-connector-c-3.2.7-1.fc36.x86_64 7/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : mariadb-connector-c-doc-3.2.7-1.fc36.noarch 8/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : mariadb-connector-c-devel-3.2.7-1.fc36.x86_64 9/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : tree-2.0.2-1.fc36.x86_64 10/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : perl-Date-Manip-6.88-1.fc36.noarch 11/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : ostree-libs-2022.4-2.fc36.x86_64 12/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : libtool-ltdl-2.4.7-1.fc36.x86_64 13/28 Wed Jun 15 09:00:04 PM CDT 2022 - Upgrading : libtool-2.4.7-1.fc36.x86_64 14/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : ibus-1.5.26-8.fc36.x86_64 15/28 Wed Jun 15 09:00:04 PM CDT 2022 - Running scriptlet: ibus-1.5.26-8.fc36.x86_64 15/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : ibus-setup-1.5.26-8.fc36.noarch 16/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : perl-Date-Manip-6.86-2.fc36.noarch 17/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : libtool-2.4.6-50.fc36.x86_64 18/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : mariadb-connector-c-devel-3.2.6-1.fc36.x86_64 19/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : ibus-gtk2-1.5.26-8.fc36.x86_64 20/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : ibus-gtk3-1.5.26-8.fc36.x86_64 21/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : mariadb-connector-c-doc-3.2.6-1.fc36.noarch 22/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : mariadb-connector-c-3.2.6-1.fc36.x86_64 23/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : mariadb-connector-c-config-3.2.6-1.fc36.noarch 24/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : ibus-libs-1.5.26-8.fc36.x86_64 25/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : tree-2.0.1-2.fc36.x86_64 26/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : ostree-libs-2022.3-3.fc36.x86_64 27/28 Wed Jun 15 09:00:04 PM CDT 2022 - Cleanup : libtool-ltdl-2.4.6-50.fc36.x86_64 28/28 Wed Jun 15 09:00:04 PM CDT 2022 - Running scriptlet: ibus-1.5.26-9.fc36.x86_64 28/28 Wed Jun 15 09:00:04 PM CDT 2022 - Running scriptlet: libtool-ltdl-2.4.6-50.fc36.x86_64 28/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-1.5.26-9.fc36.x86_64 1/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-1.5.26-8.fc36.x86_64 2/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-gtk2-1.5.26-9.fc36.x86_64 3/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-gtk2-1.5.26-8.fc36.x86_64 4/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-gtk3-1.5.26-9.fc36.x86_64 5/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-gtk3-1.5.26-8.fc36.x86_64 6/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-libs-1.5.26-9.fc36.x86_64 7/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-libs-1.5.26-8.fc36.x86_64 8/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-setup-1.5.26-9.fc36.noarch 9/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ibus-setup-1.5.26-8.fc36.noarch 10/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : libtool-2.4.7-1.fc36.x86_64 11/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : libtool-2.4.6-50.fc36.x86_64 12/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : libtool-ltdl-2.4.7-1.fc36.x86_64 13/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : libtool-ltdl-2.4.6-50.fc36.x86_64 14/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-3.2.7-1.fc36.x86_64 15/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-3.2.6-1.fc36.x86_64 16/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-config-3.2.7-1.fc36.noarch 17/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-config-3.2.6-1.fc36.noarch 18/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-devel-3.2.7-1.fc36.x86_64 19/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-devel-3.2.6-1.fc36.x86_64 20/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-doc-3.2.7-1.fc36.noarch 21/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : mariadb-connector-c-doc-3.2.6-1.fc36.noarch 22/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ostree-libs-2022.4-2.fc36.x86_64 23/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : ostree-libs-2022.3-3.fc36.x86_64 24/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : perl-Date-Manip-6.88-1.fc36.noarch 25/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : perl-Date-Manip-6.86-2.fc36.noarch 26/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : tree-2.0.2-1.fc36.x86_64 27/28 Wed Jun 15 09:00:04 PM CDT 2022 - Verifying : tree-2.0.1-2.fc36.x86_64 28/28 Wed Jun 15 09:00:04 PM CDT 2022 - Wed Jun 15 09:00:04 PM CDT 2022 - Upgraded: Wed Jun 15 09:00:04 PM CDT 2022 - ibus-1.5.26-9.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - ibus-gtk2-1.5.26-9.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - ibus-gtk3-1.5.26-9.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - ibus-libs-1.5.26-9.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - ibus-setup-1.5.26-9.fc36.noarch Wed Jun 15 09:00:04 PM CDT 2022 - libtool-2.4.7-1.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - libtool-ltdl-2.4.7-1.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c-3.2.7-1.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c-config-3.2.7-1.fc36.noarch Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c-devel-3.2.7-1.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - mariadb-connector-c-doc-3.2.7-1.fc36.noarch Wed Jun 15 09:00:04 PM CDT 2022 - ostree-libs-2022.4-2.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - perl-Date-Manip-6.88-1.fc36.noarch Wed Jun 15 09:00:04 PM CDT 2022 - tree-2.0.2-1.fc36.x86_64 Wed Jun 15 09:00:04 PM CDT 2022 - Wed Jun 15 09:00:04 PM CDT 2022 - Complete! Wed Jun 15 09:00:37 PM CDT 2022 - DNF UPDATE COMPLETED Wed Jun 15 09:00:37 PM CDT 2022 - DNF TASKS COMPLETED -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Thu Jun 16 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Thu Jun 16 09:00:01 PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Thu Jun 16 09:00:01 PM CDT 2022 - Last metadata expiration check: 0:05:10 ago on Thu 16 Jun 2022 08:54:53 PM CDT. Thu Jun 16 09:00:01 PM CDT 2022 - Dependencies resolved. Thu Jun 16 09:00:01 PM CDT 2022 - Nothing to do. Thu Jun 16 09:00:01 PM CDT 2022 - Complete! Thu Jun 16 09:00:04 PM CDT 2022 - *** CHECKING FOR SYSTEM UPDATES *** Thu Jun 16 09:00:04 PM CDT 2022 - Copr repo for Signal-Desktop owned by luminoso 5.0 kB/s | 3.3 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - Adobe Systems Incorporated 8.3 kB/s | 2.9 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - Fedora 36 - x86_64 40 kB/s | 18 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - Fedora 36 openh264 (From Cisco) - x86_64 3.4 kB/s | 989 B 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - Fedora Modular 36 - x86_64 55 kB/s | 18 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - Fedora 36 - x86_64 - Updates 51 kB/s | 16 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - Fedora Modular 36 - x86_64 - Updates 42 kB/s | 15 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Free 4.5 kB/s | 2.7 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Free - Updates 12 kB/s | 3.1 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Nonfree 5.5 kB/s | 2.8 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - RPM Fusion for Fedora 36 - Nonfree - Updates 13 kB/s | 3.3 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - teams 9.2 kB/s | 3.0 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - Dependencies resolved. Thu Jun 16 09:00:04 PM CDT 2022 - ================================================================================ Thu Jun 16 09:00:04 PM CDT 2022 - Package Arch Version Repository Size Thu Jun 16 09:00:04 PM CDT 2022 - ================================================================================ Thu Jun 16 09:00:04 PM CDT 2022 - Installing: Thu Jun 16 09:00:04 PM CDT 2022 - kernel x86_64 5.17.14-300.fc36 updates 165 k Thu Jun 16 09:00:04 PM CDT 2022 - kernel-core x86_64 5.17.14-300.fc36 updates 46 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-core x86_64 5.17.14-300.fc36 updates 48 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules x86_64 5.17.14-300.fc36 updates 54 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules-extra x86_64 5.17.14-300.fc36 updates 3.5 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-modules x86_64 5.17.14-300.fc36 updates 53 M Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading: Thu Jun 16 09:00:04 PM CDT 2022 - automake noarch 1.16.5-7.fc36 updates 675 k Thu Jun 16 09:00:04 PM CDT 2022 - containerd x86_64 1.6.6-1.fc36 updates 38 M Thu Jun 16 09:00:04 PM CDT 2022 - firefox x86_64 101.0.1-4.fc36 updates 102 M Thu Jun 16 09:00:04 PM CDT 2022 - iwl100-firmware noarch 39.31.5.1-135.fc36 updates 138 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl1000-firmware noarch 1:39.31.5.1-135.fc36 updates 249 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl105-firmware noarch 18.168.6.1-135.fc36 updates 217 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl135-firmware noarch 18.168.6.1-135.fc36 updates 226 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl2000-firmware noarch 18.168.6.1-135.fc36 updates 220 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl2030-firmware noarch 18.168.6.1-135.fc36 updates 228 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl3160-firmware noarch 1:25.30.13.0-135.fc36 updates 990 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl3945-firmware noarch 15.32.2.9-135.fc36 updates 79 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl4965-firmware noarch 228.61.2.24-135.fc36 updates 92 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl5000-firmware noarch 8.83.5.1_1-135.fc36 updates 363 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl5150-firmware noarch 8.24.2.2-135.fc36 updates 135 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl6000-firmware noarch 9.221.4.1-135.fc36 updates 154 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl6000g2a-firmware noarch 18.168.6.1-135.fc36 updates 334 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl6000g2b-firmware noarch 18.168.6.1-135.fc36 updates 341 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl6050-firmware noarch 41.28.5.1-135.fc36 updates 293 k Thu Jun 16 09:00:04 PM CDT 2022 - iwl7260-firmware noarch 1:25.30.13.0-135.fc36 updates 9.5 M Thu Jun 16 09:00:04 PM CDT 2022 - iwlax2xx-firmware noarch 20220610-135.fc36 updates 45 M Thu Jun 16 09:00:04 PM CDT 2022 - libertas-usb8388-firmware noarch 2:20220610-135.fc36 updates 103 k Thu Jun 16 09:00:04 PM CDT 2022 - librsvg2 x86_64 2.54.4-1.fc36 updates 3.6 M Thu Jun 16 09:00:04 PM CDT 2022 - librsvg2-devel x86_64 2.54.4-1.fc36 updates 97 k Thu Jun 16 09:00:04 PM CDT 2022 - linux-firmware noarch 20220610-135.fc36 updates 146 M Thu Jun 16 09:00:04 PM CDT 2022 - linux-firmware-whence noarch 20220610-135.fc36 updates 50 k Thu Jun 16 09:00:04 PM CDT 2022 - mozjs91 x86_64 91.10.0-1.fc36 updates 4.4 M Thu Jun 16 09:00:04 PM CDT 2022 - pcsc-lite x86_64 1.9.8-1.fc36 updates 94 k Thu Jun 16 09:00:04 PM CDT 2022 - pcsc-lite-libs x86_64 1.9.8-1.fc36 updates 28 k Thu Jun 16 09:00:04 PM CDT 2022 - vim-X11 x86_64 2:8.2.5085-1.fc36 updates 2.1 M Thu Jun 16 09:00:04 PM CDT 2022 - vim-common x86_64 2:8.2.5085-1.fc36 updates 7.0 M Thu Jun 16 09:00:04 PM CDT 2022 - vim-data noarch 2:8.2.5085-1.fc36 updates 27 k Thu Jun 16 09:00:04 PM CDT 2022 - vim-filesystem noarch 2:8.2.5085-1.fc36 updates 21 k Thu Jun 16 09:00:04 PM CDT 2022 - vim-minimal x86_64 2:8.2.5085-1.fc36 updates 749 k Thu Jun 16 09:00:04 PM CDT 2022 - Removing: Thu Jun 16 09:00:04 PM CDT 2022 - kernel x86_64 5.17.9-300.fc36 @updates 0 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-core x86_64 5.17.9-300.fc36 @updates 89 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-core x86_64 5.17.9-300.fc36 @updates 92 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules x86_64 5.17.9-300.fc36 @updates 53 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules-extra x86_64 5.17.9-300.fc36 @updates 3.3 M Thu Jun 16 09:00:04 PM CDT 2022 - kernel-modules x86_64 5.17.9-300.fc36 @updates 52 M Thu Jun 16 09:00:04 PM CDT 2022 - Thu Jun 16 09:00:04 PM CDT 2022 - Transaction Summary Thu Jun 16 09:00:04 PM CDT 2022 - ================================================================================ Thu Jun 16 09:00:04 PM CDT 2022 - Install 6 Packages Thu Jun 16 09:00:04 PM CDT 2022 - Upgrade 33 Packages Thu Jun 16 09:00:04 PM CDT 2022 - Remove 6 Packages Thu Jun 16 09:00:04 PM CDT 2022 - Thu Jun 16 09:00:04 PM CDT 2022 - Total download size: 568 M Thu Jun 16 09:00:04 PM CDT 2022 - Downloading Packages: Thu Jun 16 09:00:04 PM CDT 2022 - (1/39): iwl105-firmware-18.168.6.1-132.fc36_18. 81 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (2/39): iwl100-firmware-39.31.5.1-132.fc36_39.3 75 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (3/39): iwl1000-firmware-39.31.5.1-132.fc36_39. 70 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (4/39): iwl135-firmware-18.168.6.1-132.fc36_18. 327 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (5/39): iwl2000-firmware-18.168.6.1-132.fc36_18 325 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (6/39): iwl2030-firmware-18.168.6.1-132.fc36_18 270 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (7/39): iwl3160-firmware-25.30.13.0-132.fc36_25 330 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (8/39): iwl3945-firmware-15.32.2.9-132.fc36_15. 317 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 1/25] iwl105-firmware-18.168.6.1-132.fc36_18.168.6.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 2/25] iwl100-firmware-39.31.5.1-132.fc36_39.31.5.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (9/39): iwl4965-firmware-228.61.2.24-132.fc36_2 231 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (10/39): iwl5000-firmware-8.83.5.1_1-132.fc36_8 253 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 3/25] iwl1000-firmware-39.31.5.1-132.fc36_39.31.5.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (11/39): iwl5150-firmware-8.24.2.2-132.fc36_8.2 314 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 4/25] iwl135-firmware-18.168.6.1-132.fc36_18.168.6.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (12/39): iwl6000-firmware-9.221.4.1-132.fc36_9. 319 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (13/39): iwl6000g2a-firmware-18.168.6.1-132.fc3 319 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 5/25] iwl2000-firmware-18.168.6.1-132.fc36_18.168.6.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (14/39): iwl6000g2b-firmware-18.168.6.1-132.fc3 281 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 6/25] iwl2030-firmware-18.168.6.1-132.fc36_18.168.6.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 7/25] iwl3945-firmware-15.32.2.9-132.fc36_15.32.2.9-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 8/25] iwl4965-firmware-228.61.2.24-132.fc36_228.61.2.24-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (15/39): iwl6050-firmware-41.28.5.1-132.fc36_41 232 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (16/39): libertas-usb8388-firmware-20220509-132 317 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 9/25] iwl5000-firmware-8.83.5.1_1-132.fc36_8.83.5.1_1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 10/25] iwl5150-firmware-8.24.2.2-132.fc36_8.24.2.2-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 11/25] iwl6000-firmware-9.221.4.1-132.fc36_9.221.4.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (17/39): librsvg2-devel-2.54.3-1.fc36_2.54.4-1. 348 kB/s | 22 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 12/25] iwl3160-firmware-25.30.13.0-132.fc36_25.30.13.0-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 13/25] iwl6000g2a-firmware-18.168.6.1-132.fc36_18.168.6.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 14/25] iwl6000g2b-firmware-18.168.6.1-132.fc36_18.168.6.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 15/25] iwl6050-firmware-41.28.5.1-132.fc36_41.28.5.1-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 16/25] libertas-usb8388-firmware-20220509-132.fc36_20220610-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (18/39): iwl7260-firmware-25.30.13.0-132.fc36_2 2.3 MB/s | 869 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (19/39): linux-firmware-whence-20220509-132.fc3 243 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (20/39): mozjs91-91.9.0-1.fc36_91.10.0-1.fc36.x 4.6 MB/s | 1.3 MB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 17/25] linux-firmware-whence-20220509-132.fc36_20220610-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (21/39): pcsc-lite-1.9.7-1.fc36_1.9.8-1.fc36.x8 212 kB/s | 60 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (22/39): pcsc-lite-libs-1.9.7-1.fc36_1.9.8-1.fc 173 kB/s | 10 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 18/25] librsvg2-devel-2.54.3-1.fc36_2.54.4-1.fc36.x86_64.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (23/39): vim-data-8.2.5052-1.fc36_8.2.5085-1.fc 270 kB/s | 17 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (24/39): kernel-5.17.14-300.fc36.x86_64.rpm 2.0 MB/s | 165 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (25/39): vim-common-8.2.5052-1.fc36_8.2.5085-1. 868 kB/s | 428 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 19/25] pcsc-lite-1.9.7-1.fc36_1.9.8-1.fc36.x86_64.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 20/25] pcsc-lite-libs-1.9.7-1.fc36_1.9.8-1.fc36.x86_64.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 21/25] vim-data-8.2.5052-1.fc36_8.2.5085-1.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (26/39): iwlax2xx-firmware-20220509-132.fc36_20 1.1 MB/s | 5.1 MB 00:04 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 22/25] iwl7260-firmware-25.30.13.0-132.fc36_25.30.13.0-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - (27/39): kernel-core-5.17.14-300.fc36.x86_64.rp 6.5 MB/s | 46 MB 00:07 Thu Jun 16 09:00:04 PM CDT 2022 - (28/39): kernel-debug-modules-extra-5.17.14-300 4.7 MB/s | 3.5 MB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (29/39): kernel-modules-5.17.14-300.fc36.x86_64 5.3 MB/s | 53 MB 00:09 Thu Jun 16 09:00:04 PM CDT 2022 - (30/39): kernel-debug-core-5.17.14-300.fc36.x86 2.5 MB/s | 48 MB 00:18 Thu Jun 16 09:00:04 PM CDT 2022 - (31/39): automake-1.16.5-7.fc36.noarch.rpm 371 kB/s | 675 kB 00:01 Thu Jun 16 09:00:04 PM CDT 2022 - (32/39): kernel-debug-modules-5.17.14-300.fc36. 2.0 MB/s | 54 MB 00:26 Thu Jun 16 09:00:04 PM CDT 2022 - (33/39): containerd-1.6.6-1.fc36.x86_64.rpm 2.8 MB/s | 38 MB 00:13 Thu Jun 16 09:00:04 PM CDT 2022 - (34/39): librsvg2-2.54.4-1.fc36.x86_64.rpm 1.6 MB/s | 3.6 MB 00:02 Thu Jun 16 09:00:04 PM CDT 2022 - (35/39): vim-X11-8.2.5085-1.fc36.x86_64.rpm 2.0 MB/s | 2.1 MB 00:01 Thu Jun 16 09:00:04 PM CDT 2022 - (36/39): vim-filesystem-8.2.5085-1.fc36.noarch. 224 kB/s | 21 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (37/39): vim-minimal-8.2.5085-1.fc36.x86_64.rpm 2.1 MB/s | 749 kB 00:00 Thu Jun 16 09:00:04 PM CDT 2022 - (38/39): firefox-101.0.1-4.fc36.x86_64.rpm 5.2 MB/s | 102 MB 00:19 Thu Jun 16 09:00:04 PM CDT 2022 - (39/39): linux-firmware-20220610-135.fc36.noarc 5.8 MB/s | 146 MB 00:25 Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 23/25] mozjs91-91.9.0-1.fc36_91.10.0-1.fc36.x86_64.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 24/25] vim-common-8.2.5052-1.fc36_8.2.5085-1.fc36.x86_64.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - [DRPM 25/25] iwlax2xx-firmware-20220509-132.fc36_20220610-135.fc36.noarch.drpm: done Thu Jun 16 09:00:04 PM CDT 2022 - -------------------------------------------------------------------------------- Thu Jun 16 09:00:04 PM CDT 2022 - Total 8.4 MB/s | 506 MB 00:59 Thu Jun 16 09:00:04 PM CDT 2022 - Delta RPMs reduced 567.8 MB of updates to 506.2 MB (10.9% saved) Thu Jun 16 09:00:04 PM CDT 2022 - Running transaction check Thu Jun 16 09:00:04 PM CDT 2022 - Transaction check succeeded. Thu Jun 16 09:00:04 PM CDT 2022 - Running transaction test Thu Jun 16 09:00:04 PM CDT 2022 - Transaction test succeeded. Thu Jun 16 09:00:04 PM CDT 2022 - Running transaction Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: firefox-101.0.1-4.fc36.x86_64 1/1 Thu Jun 16 09:00:04 PM CDT 2022 - Preparing : 1/1 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : linux-firmware-whence-20220610-135.fc36.noarch 1/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : linux-firmware-20220610-135.fc36.noarch 2/78 Thu Jun 16 09:00:04 PM CDT 2022 - Installing : kernel-core-5.17.14-300.fc36.x86_64 3/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-core-5.17.14-300.fc36.x86_64 3/78 Thu Jun 16 09:00:04 PM CDT 2022 - Installing : kernel-debug-core-5.17.14-300.fc36.x86_64 4/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-core-5.17.14-300.fc36.x86_64 4/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : vim-data-2:8.2.5085-1.fc36.noarch 5/78 Thu Jun 16 09:00:04 PM CDT 2022 - Installing : kernel-debug-modules-5.17.14-300.fc36.x86_64 6/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-modules-5.17.14-300.fc36.x86_64 6/78 Thu Jun 16 09:00:04 PM CDT 2022 - Installing : kernel-modules-5.17.14-300.fc36.x86_64 7/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-modules-5.17.14-300.fc36.x86_64 7/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwlax2xx-firmware-20220610-135.fc36.noarch 8/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl7260-firmware-1:25.30.13.0-135.fc36.noarch 9/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : vim-filesystem-2:8.2.5085-1.fc36.noarch 10/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : vim-common-2:8.2.5085-1.fc36.x86_64 11/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : pcsc-lite-libs-1.9.8-1.fc36.x86_64 12/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : librsvg2-2.54.4-1.fc36.x86_64 13/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : librsvg2-devel-2.54.4-1.fc36.x86_64 14/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : pcsc-lite-1.9.8-1.fc36.x86_64 15/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: pcsc-lite-1.9.8-1.fc36.x86_64 15/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : vim-X11-2:8.2.5085-1.fc36.x86_64 16/78 Thu Jun 16 09:00:04 PM CDT 2022 - Installing : kernel-5.17.14-300.fc36.x86_64 17/78 Thu Jun 16 09:00:04 PM CDT 2022 - Installing : kernel-debug-modules-extra-5.17.14-300.fc36.x86_64 18/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-modules-extra-5.17.14-300.fc36.x86_64 18/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : vim-minimal-2:8.2.5085-1.fc36.x86_64 19/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl100-firmware-39.31.5.1-135.fc36.noarch 20/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl1000-firmware-1:39.31.5.1-135.fc36.noarch 21/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl105-firmware-18.168.6.1-135.fc36.noarch 22/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl135-firmware-18.168.6.1-135.fc36.noarch 23/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl2000-firmware-18.168.6.1-135.fc36.noarch 24/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl2030-firmware-18.168.6.1-135.fc36.noarch 25/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl3160-firmware-1:25.30.13.0-135.fc36.noarch 26/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl3945-firmware-15.32.2.9-135.fc36.noarch 27/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl4965-firmware-228.61.2.24-135.fc36.noarch 28/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl5000-firmware-8.83.5.1_1-135.fc36.noarch 29/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl5150-firmware-8.24.2.2-135.fc36.noarch 30/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl6000-firmware-9.221.4.1-135.fc36.noarch 31/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl6000g2a-firmware-18.168.6.1-135.fc36.noarch 32/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl6000g2b-firmware-18.168.6.1-135.fc36.noarch 33/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : iwl6050-firmware-41.28.5.1-135.fc36.noarch 34/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : libertas-usb8388-firmware-2:20220610-135.fc36.noar 35/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : mozjs91-91.10.0-1.fc36.x86_64 36/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : firefox-101.0.1-4.fc36.x86_64 37/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: firefox-101.0.1-4.fc36.x86_64 37/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : containerd-1.6.6-1.fc36.x86_64 38/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: containerd-1.6.6-1.fc36.x86_64 38/78 Thu Jun 16 09:00:04 PM CDT 2022 - Upgrading : automake-1.16.5-7.fc36.noarch 39/78 Thu Jun 16 09:00:04 PM CDT 2022 - Erasing : kernel-debug-modules-extra-5.17.9-300.fc36.x86_64 40/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-modules-extra-5.17.9-300.fc36.x86_64 40/78 Thu Jun 16 09:00:04 PM CDT 2022 - Erasing : kernel-5.17.9-300.fc36.x86_64 41/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : librsvg2-devel-2.54.3-1.fc36.x86_64 42/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl7260-firmware-1:25.30.13.0-132.fc36.noarch 43/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwlax2xx-firmware-20220509-132.fc36.noarch 44/78 Thu Jun 16 09:00:04 PM CDT 2022 - Erasing : kernel-modules-5.17.9-300.fc36.x86_64 45/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-modules-5.17.9-300.fc36.x86_64 45/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-core-5.17.9-300.fc36.x86_64 46/78 Thu Jun 16 09:00:04 PM CDT 2022 - Erasing : kernel-core-5.17.9-300.fc36.x86_64 46/78 Thu Jun 16 09:00:04 PM CDT 2022 - Erasing : kernel-debug-modules-5.17.9-300.fc36.x86_64 47/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-modules-5.17.9-300.fc36.x86_64 47/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-core-5.17.9-300.fc36.x86_64 48/78 Thu Jun 16 09:00:04 PM CDT 2022 - Erasing : kernel-debug-core-5.17.9-300.fc36.x86_64 48/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : linux-firmware-20220509-132.fc36.noarch 49/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : libertas-usb8388-firmware-2:20220509-132.fc36.noar 50/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl6050-firmware-41.28.5.1-132.fc36.noarch 51/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl6000g2b-firmware-18.168.6.1-132.fc36.noarch 52/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl6000g2a-firmware-18.168.6.1-132.fc36.noarch 53/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl6000-firmware-9.221.4.1-132.fc36.noarch 54/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl5150-firmware-8.24.2.2-132.fc36.noarch 55/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl5000-firmware-8.83.5.1_1-132.fc36.noarch 56/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl4965-firmware-228.61.2.24-132.fc36.noarch 57/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl3945-firmware-15.32.2.9-132.fc36.noarch 58/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl3160-firmware-1:25.30.13.0-132.fc36.noarch 59/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl2030-firmware-18.168.6.1-132.fc36.noarch 60/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl2000-firmware-18.168.6.1-132.fc36.noarch 61/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl135-firmware-18.168.6.1-132.fc36.noarch 62/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl105-firmware-18.168.6.1-132.fc36.noarch 63/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl1000-firmware-1:39.31.5.1-132.fc36.noarch 64/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : iwl100-firmware-39.31.5.1-132.fc36.noarch 65/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : linux-firmware-whence-20220509-132.fc36.noarch 66/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : automake-1.16.5-4.fc36.noarch 67/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : vim-minimal-2:8.2.5052-1.fc36.x86_64 68/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : vim-X11-2:8.2.5052-1.fc36.x86_64 69/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : vim-common-2:8.2.5052-1.fc36.x86_64 70/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: pcsc-lite-1.9.7-1.fc36.x86_64 71/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : pcsc-lite-1.9.7-1.fc36.x86_64 71/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: pcsc-lite-1.9.7-1.fc36.x86_64 71/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : vim-data-2:8.2.5052-1.fc36.noarch 72/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : vim-filesystem-2:8.2.5052-1.fc36.noarch 73/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : pcsc-lite-libs-1.9.7-1.fc36.x86_64 74/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : librsvg2-2.54.3-1.fc36.x86_64 75/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : mozjs91-91.9.0-1.fc36.x86_64 76/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: firefox-101.0-1.fc36.x86_64 77/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : firefox-101.0-1.fc36.x86_64 77/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: firefox-101.0-1.fc36.x86_64 77/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: containerd-1.6.4-1.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Cleanup : containerd-1.6.4-1.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: containerd-1.6.4-1.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-core-5.17.14-300.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-core-5.17.14-300.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-debug-modules-5.17.14-300.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running: dracut -f --kver 5.17.14-300.fc36.x86_64+debug Thu Jun 16 09:00:04 PM CDT 2022 - Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: kernel-modules-5.17.14-300.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: firefox-101.0.1-4.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Running scriptlet: containerd-1.6.4-1.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-5.17.14-300.fc36.x86_64 1/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-core-5.17.14-300.fc36.x86_64 2/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-debug-core-5.17.14-300.fc36.x86_64 3/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-debug-modules-5.17.14-300.fc36.x86_64 4/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-debug-modules-extra-5.17.14-300.fc36.x86_64 5/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-modules-5.17.14-300.fc36.x86_64 6/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : automake-1.16.5-7.fc36.noarch 7/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : automake-1.16.5-4.fc36.noarch 8/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : containerd-1.6.6-1.fc36.x86_64 9/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : containerd-1.6.4-1.fc36.x86_64 10/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : firefox-101.0.1-4.fc36.x86_64 11/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : firefox-101.0-1.fc36.x86_64 12/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl100-firmware-39.31.5.1-135.fc36.noarch 13/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl100-firmware-39.31.5.1-132.fc36.noarch 14/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl1000-firmware-1:39.31.5.1-135.fc36.noarch 15/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl1000-firmware-1:39.31.5.1-132.fc36.noarch 16/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl105-firmware-18.168.6.1-135.fc36.noarch 17/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl105-firmware-18.168.6.1-132.fc36.noarch 18/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl135-firmware-18.168.6.1-135.fc36.noarch 19/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl135-firmware-18.168.6.1-132.fc36.noarch 20/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl2000-firmware-18.168.6.1-135.fc36.noarch 21/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl2000-firmware-18.168.6.1-132.fc36.noarch 22/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl2030-firmware-18.168.6.1-135.fc36.noarch 23/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl2030-firmware-18.168.6.1-132.fc36.noarch 24/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl3160-firmware-1:25.30.13.0-135.fc36.noarch 25/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl3160-firmware-1:25.30.13.0-132.fc36.noarch 26/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl3945-firmware-15.32.2.9-135.fc36.noarch 27/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl3945-firmware-15.32.2.9-132.fc36.noarch 28/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl4965-firmware-228.61.2.24-135.fc36.noarch 29/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl4965-firmware-228.61.2.24-132.fc36.noarch 30/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl5000-firmware-8.83.5.1_1-135.fc36.noarch 31/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl5000-firmware-8.83.5.1_1-132.fc36.noarch 32/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl5150-firmware-8.24.2.2-135.fc36.noarch 33/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl5150-firmware-8.24.2.2-132.fc36.noarch 34/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6000-firmware-9.221.4.1-135.fc36.noarch 35/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6000-firmware-9.221.4.1-132.fc36.noarch 36/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6000g2a-firmware-18.168.6.1-135.fc36.noarch 37/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6000g2a-firmware-18.168.6.1-132.fc36.noarch 38/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6000g2b-firmware-18.168.6.1-135.fc36.noarch 39/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6000g2b-firmware-18.168.6.1-132.fc36.noarch 40/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6050-firmware-41.28.5.1-135.fc36.noarch 41/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl6050-firmware-41.28.5.1-132.fc36.noarch 42/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl7260-firmware-1:25.30.13.0-135.fc36.noarch 43/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwl7260-firmware-1:25.30.13.0-132.fc36.noarch 44/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwlax2xx-firmware-20220610-135.fc36.noarch 45/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : iwlax2xx-firmware-20220509-132.fc36.noarch 46/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : libertas-usb8388-firmware-2:20220610-135.fc36.noar 47/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : libertas-usb8388-firmware-2:20220509-132.fc36.noar 48/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : librsvg2-2.54.4-1.fc36.x86_64 49/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : librsvg2-2.54.3-1.fc36.x86_64 50/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : librsvg2-devel-2.54.4-1.fc36.x86_64 51/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : librsvg2-devel-2.54.3-1.fc36.x86_64 52/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : linux-firmware-20220610-135.fc36.noarch 53/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : linux-firmware-20220509-132.fc36.noarch 54/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : linux-firmware-whence-20220610-135.fc36.noarch 55/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : linux-firmware-whence-20220509-132.fc36.noarch 56/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : mozjs91-91.10.0-1.fc36.x86_64 57/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : mozjs91-91.9.0-1.fc36.x86_64 58/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : pcsc-lite-1.9.8-1.fc36.x86_64 59/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : pcsc-lite-1.9.7-1.fc36.x86_64 60/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : pcsc-lite-libs-1.9.8-1.fc36.x86_64 61/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : pcsc-lite-libs-1.9.7-1.fc36.x86_64 62/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-X11-2:8.2.5085-1.fc36.x86_64 63/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-X11-2:8.2.5052-1.fc36.x86_64 64/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-common-2:8.2.5085-1.fc36.x86_64 65/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-common-2:8.2.5052-1.fc36.x86_64 66/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-data-2:8.2.5085-1.fc36.noarch 67/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-data-2:8.2.5052-1.fc36.noarch 68/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-filesystem-2:8.2.5085-1.fc36.noarch 69/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-filesystem-2:8.2.5052-1.fc36.noarch 70/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-minimal-2:8.2.5085-1.fc36.x86_64 71/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : vim-minimal-2:8.2.5052-1.fc36.x86_64 72/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-5.17.9-300.fc36.x86_64 73/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-core-5.17.9-300.fc36.x86_64 74/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-debug-core-5.17.9-300.fc36.x86_64 75/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-debug-modules-5.17.9-300.fc36.x86_64 76/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-debug-modules-extra-5.17.9-300.fc36.x86_64 77/78 Thu Jun 16 09:00:04 PM CDT 2022 - Verifying : kernel-modules-5.17.9-300.fc36.x86_64 78/78 Thu Jun 16 09:00:04 PM CDT 2022 - Thu Jun 16 09:00:04 PM CDT 2022 - Upgraded: Thu Jun 16 09:00:04 PM CDT 2022 - automake-1.16.5-7.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - containerd-1.6.6-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - firefox-101.0.1-4.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - iwl100-firmware-39.31.5.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl1000-firmware-1:39.31.5.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl105-firmware-18.168.6.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl135-firmware-18.168.6.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl2000-firmware-18.168.6.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl2030-firmware-18.168.6.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl3160-firmware-1:25.30.13.0-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl3945-firmware-15.32.2.9-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl4965-firmware-228.61.2.24-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl5000-firmware-8.83.5.1_1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl5150-firmware-8.24.2.2-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl6000-firmware-9.221.4.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl6000g2a-firmware-18.168.6.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl6000g2b-firmware-18.168.6.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl6050-firmware-41.28.5.1-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwl7260-firmware-1:25.30.13.0-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - iwlax2xx-firmware-20220610-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - libertas-usb8388-firmware-2:20220610-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - librsvg2-2.54.4-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - librsvg2-devel-2.54.4-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - linux-firmware-20220610-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - linux-firmware-whence-20220610-135.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - mozjs91-91.10.0-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - pcsc-lite-1.9.8-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - pcsc-lite-libs-1.9.8-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - vim-X11-2:8.2.5085-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - vim-common-2:8.2.5085-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - vim-data-2:8.2.5085-1.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - vim-filesystem-2:8.2.5085-1.fc36.noarch Thu Jun 16 09:00:04 PM CDT 2022 - vim-minimal-2:8.2.5085-1.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - Installed: Thu Jun 16 09:00:04 PM CDT 2022 - kernel-5.17.14-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-core-5.17.14-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-core-5.17.14-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules-5.17.14-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules-extra-5.17.14-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-modules-5.17.14-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - Removed: Thu Jun 16 09:00:04 PM CDT 2022 - kernel-5.17.9-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-core-5.17.9-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-core-5.17.9-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules-5.17.9-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-debug-modules-extra-5.17.9-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - kernel-modules-5.17.9-300.fc36.x86_64 Thu Jun 16 09:00:04 PM CDT 2022 - Thu Jun 16 09:00:04 PM CDT 2022 - Complete! Thu Jun 16 09:03:42 PM CDT 2022 - DNF UPDATE COMPLETED Thu Jun 16 09:03:42 PM CDT 2022 - DNF TASKS COMPLETED --------------------------------------------------------------------------------
There was a kernel update on Thursday, but lots else.
Thanks, Ranjan
On 6/23/22 14:59, Ranjan Maitra wrote:
On Thu Jun23'22 02:44:00PM, Samuel Sieb wrote:
Can you check the dnf history to see what packages were involved in that update that possibly made it stop working?
Thanks! Here are the updates from last Wed and Thu:
-------------------------------------------------------------------------------- Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15 09:00:01 PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 09:00:01 PM CDT 2022 -
I don't know what that is, but somehow you pasted it without newlines...
Run "dnf history", find the entry for that update (probably the first one), then run "dnf history info 38", but replace the 38 with the number of the entry. Copy and paste that list with newlines.
On Thu Jun23'22 05:07:01PM, Samuel Sieb wrote:
From: Samuel Sieb samuel@sieb.net Date: Thu, 23 Jun 2022 17:07:01 -0700 To: users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On 6/23/22 14:59, Ranjan Maitra wrote:
On Thu Jun23'22 02:44:00PM, Samuel Sieb wrote:
Can you check the dnf history to see what packages were involved in that update that possibly made it stop working?
Thanks! Here are the updates from last Wed and Thu:
Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15 09:00:01 PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 09:00:01 PM CDT 2022 -
I don't know what that is, but somehow you pasted it without newlines...
Yes, indeed, my apologies! But your suggestion below is far less of an effort.
Run "dnf history", find the entry for that update (probably the first one), then run "dnf history info 38", but replace the 38 with the number of the entry. Copy and paste that list with newlines.
$ sudo dnf history info 565 Transaction ID : 565 Begin time : Thu 16 Jun 2022 09:01:21 PM CDT Begin rpmdb : 67d1013735286669fc92237fc0a33e0c3c100626 End time : Thu 16 Jun 2022 09:03:41 PM CDT (140 seconds) End rpmdb : c398c99fde90fd93c5c2a2c1347884da53a2463f User : root <root> Return-Code : Success Releasever : 36 Command Line : -y update --refresh Comment : Packages Altered: Install kernel-5.17.14-300.fc36.x86_64 @updates Install kernel-core-5.17.14-300.fc36.x86_64 @updates Install kernel-debug-core-5.17.14-300.fc36.x86_64 @updates Install kernel-debug-modules-5.17.14-300.fc36.x86_64 @updates Install kernel-debug-modules-extra-5.17.14-300.fc36.x86_64 @updates Install kernel-modules-5.17.14-300.fc36.x86_64 @updates Upgrade automake-1.16.5-7.fc36.noarch @updates Upgraded automake-1.16.5-4.fc36.noarch @@System Upgrade containerd-1.6.6-1.fc36.x86_64 @updates Upgraded containerd-1.6.4-1.fc36.x86_64 @@System Upgrade firefox-101.0.1-4.fc36.x86_64 @updates Upgraded firefox-101.0-1.fc36.x86_64 @@System Upgrade iwl100-firmware-39.31.5.1-135.fc36.noarch @updates Upgraded iwl100-firmware-39.31.5.1-132.fc36.noarch @@System Upgrade iwl1000-firmware-1:39.31.5.1-135.fc36.noarch @updates Upgraded iwl1000-firmware-1:39.31.5.1-132.fc36.noarch @@System Upgrade iwl105-firmware-18.168.6.1-135.fc36.noarch @updates Upgraded iwl105-firmware-18.168.6.1-132.fc36.noarch @@System Upgrade iwl135-firmware-18.168.6.1-135.fc36.noarch @updates Upgraded iwl135-firmware-18.168.6.1-132.fc36.noarch @@System Upgrade iwl2000-firmware-18.168.6.1-135.fc36.noarch @updates Upgraded iwl2000-firmware-18.168.6.1-132.fc36.noarch @@System Upgrade iwl2030-firmware-18.168.6.1-135.fc36.noarch @updates Upgraded iwl2030-firmware-18.168.6.1-132.fc36.noarch @@System Upgrade iwl3160-firmware-1:25.30.13.0-135.fc36.noarch @updates Upgraded iwl3160-firmware-1:25.30.13.0-132.fc36.noarch @@System Upgrade iwl3945-firmware-15.32.2.9-135.fc36.noarch @updates Upgraded iwl3945-firmware-15.32.2.9-132.fc36.noarch @@System Upgrade iwl4965-firmware-228.61.2.24-135.fc36.noarch @updates Upgraded iwl4965-firmware-228.61.2.24-132.fc36.noarch @@System Upgrade iwl5000-firmware-8.83.5.1_1-135.fc36.noarch @updates Upgraded iwl5000-firmware-8.83.5.1_1-132.fc36.noarch @@System Upgrade iwl5150-firmware-8.24.2.2-135.fc36.noarch @updates Upgraded iwl5150-firmware-8.24.2.2-132.fc36.noarch @@System Upgrade iwl6000-firmware-9.221.4.1-135.fc36.noarch @updates Upgraded iwl6000-firmware-9.221.4.1-132.fc36.noarch @@System Upgrade iwl6000g2a-firmware-18.168.6.1-135.fc36.noarch @updates Upgraded iwl6000g2a-firmware-18.168.6.1-132.fc36.noarch @@System Upgrade iwl6000g2b-firmware-18.168.6.1-135.fc36.noarch @updates Upgraded iwl6000g2b-firmware-18.168.6.1-132.fc36.noarch @@System Upgrade iwl6050-firmware-41.28.5.1-135.fc36.noarch @updates Upgraded iwl6050-firmware-41.28.5.1-132.fc36.noarch @@System Upgrade iwl7260-firmware-1:25.30.13.0-135.fc36.noarch @updates Upgraded iwl7260-firmware-1:25.30.13.0-132.fc36.noarch @@System Upgrade iwlax2xx-firmware-20220610-135.fc36.noarch @updates Upgraded iwlax2xx-firmware-20220509-132.fc36.noarch @@System Upgrade libertas-usb8388-firmware-2:20220610-135.fc36.noarch @updates Upgraded libertas-usb8388-firmware-2:20220509-132.fc36.noarch @@System Upgrade librsvg2-2.54.4-1.fc36.x86_64 @updates Upgraded librsvg2-2.54.3-1.fc36.x86_64 @@System Upgrade librsvg2-devel-2.54.4-1.fc36.x86_64 @updates Upgraded librsvg2-devel-2.54.3-1.fc36.x86_64 @@System Upgrade linux-firmware-20220610-135.fc36.noarch @updates Upgraded linux-firmware-20220509-132.fc36.noarch @@System Upgrade linux-firmware-whence-20220610-135.fc36.noarch @updates Upgraded linux-firmware-whence-20220509-132.fc36.noarch @@System Upgrade mozjs91-91.10.0-1.fc36.x86_64 @updates Upgraded mozjs91-91.9.0-1.fc36.x86_64 @@System Upgrade pcsc-lite-1.9.8-1.fc36.x86_64 @updates Upgraded pcsc-lite-1.9.7-1.fc36.x86_64 @@System Upgrade pcsc-lite-libs-1.9.8-1.fc36.x86_64 @updates Upgraded pcsc-lite-libs-1.9.7-1.fc36.x86_64 @@System Upgrade vim-X11-2:8.2.5085-1.fc36.x86_64 @updates Upgraded vim-X11-2:8.2.5052-1.fc36.x86_64 @@System Upgrade vim-common-2:8.2.5085-1.fc36.x86_64 @updates Upgraded vim-common-2:8.2.5052-1.fc36.x86_64 @@System Upgrade vim-data-2:8.2.5085-1.fc36.noarch @updates Upgraded vim-data-2:8.2.5052-1.fc36.noarch @@System Upgrade vim-filesystem-2:8.2.5085-1.fc36.noarch @updates Upgraded vim-filesystem-2:8.2.5052-1.fc36.noarch @@System Upgrade vim-minimal-2:8.2.5085-1.fc36.x86_64 @updates Upgraded vim-minimal-2:8.2.5052-1.fc36.x86_64 @@System Reason Change AtomicParsley-0.9.5-19.fc36.x86_64 @fedora Removed kernel-5.17.9-300.fc36.x86_64 @@System Removed kernel-core-5.17.9-300.fc36.x86_64 @@System Removed kernel-debug-core-5.17.9-300.fc36.x86_64 @@System Removed kernel-debug-modules-5.17.9-300.fc36.x86_64 @@System Removed kernel-debug-modules-extra-5.17.9-300.fc36.x86_64 @@System Removed kernel-modules-5.17.9-300.fc36.x86_64 @@System
Scriptlet output: 1 Running: dracut -f --kver 5.17.14-300.fc36.x86_64+debug
Thanks again!
Ranjan
On 6/23/22 17:13, Ranjan Maitra wrote:
On Thu Jun23'22 05:07:01PM, Samuel Sieb wrote:
From: Samuel Sieb samuel@sieb.net Date: Thu, 23 Jun 2022 17:07:01 -0700 To: users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On 6/23/22 14:59, Ranjan Maitra wrote:
On Thu Jun23'22 02:44:00PM, Samuel Sieb wrote:
Can you check the dnf history to see what packages were involved in that update that possibly made it stop working?
Thanks! Here are the updates from last Wed and Thu:
Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15 09:00:01 PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 09:00:01 PM CDT 2022 -
I don't know what that is, but somehow you pasted it without newlines...
Yes, indeed, my apologies! But your suggestion below is far less of an effort.
Run "dnf history", find the entry for that update (probably the first one), then run "dnf history info 38", but replace the 38 with the number of the entry. Copy and paste that list with newlines.
$ sudo dnf history info 565 Install kernel-5.17.14-300.fc36.x86_64 @updates Install kernel-core-5.17.14-300.fc36.x86_64 @updates
You did have a kernel update.
Install kernel-debug-core-5.17.14-300.fc36.x86_64 @updates Install kernel-debug-modules-5.17.14-300.fc36.x86_64 @updates Install kernel-debug-modules-extra-5.17.14-300.fc36.x86_64 @updates
You must have been upgrading this system for quite a while. The debug kernel modules got accidentally pulled in back then. You can do "dnf remove kernel-debug*" to get rid of those.
I have no idea why hibernate stopped working, but it seems to not like something the BIOS is doing.
On Fri, Jun 24, 2022 at 4:21 AM Samuel Sieb samuel@sieb.net wrote:
On 6/23/22 17:13, Ranjan Maitra wrote: [...]
Thanks! Here are the updates from last Wed and Thu:
Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15
09:00:01
PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 09:00:01 PM CDT 2022 -
I don't know what that is, but somehow you pasted it without newlines...
Yes, indeed, my apologies! But your suggestion below is far less of an
effort.
Run "dnf history", find the entry for that update (probably the first
one),
then run "dnf history info 38", but replace the 38 with the number of
the
entry. Copy and paste that list with newlines.
$ sudo dnf history info 565 Install kernel-5.17.14-300.fc36.x86_64
@updates
Install kernel-core-5.17.14-300.fc36.x86_64@updates
You did have a kernel update.
Install kernel-debug-core-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-extra-5.17.14-300.fc36.x86_64@updates
You must have been upgrading this system for quite a while. The debug kernel modules got accidentally pulled in back then. You can do "dnf remove kernel-debug*" to get rid of those.
I have no idea why hibernate stopped working, but it seems to not like something the BIOS is doing.
Dell systems recently got BIOS updates. My newest Dell system did a 2-step BIOS firmware update dance. The updates are dated May 22.
" - Firmware updates to address security vulnerabilities including (Common Vulnerabilities and Exposures - CVE) such as CVE-2022-0004, CVE-2022-0005, CVE-2022-21123, CVE-2022-21125, CVE-2022-21127, CVE-2022-21151, CVE-2022-21166, and CVE-2022-21181"
These might have introduced something in the BIOS that kernels "don't like". I see a bunch of driver firmware updates around the same time. If these are problematic there may be reports for for other distros.
On Fri Jun24'22 08:00:57AM, George N. White III wrote:
From: "George N. White III" gnwiii@gmail.com Date: Fri, 24 Jun 2022 08:00:57 -0300 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Fri, Jun 24, 2022 at 4:21 AM Samuel Sieb samuel@sieb.net wrote:
On 6/23/22 17:13, Ranjan Maitra wrote: [...]
Thanks! Here are the updates from last Wed and Thu:
Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15
09:00:01
PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 09:00:01 PM CDT 2022 -
I don't know what that is, but somehow you pasted it without newlines...
Yes, indeed, my apologies! But your suggestion below is far less of an
effort.
Run "dnf history", find the entry for that update (probably the first
one),
then run "dnf history info 38", but replace the 38 with the number of
the
entry. Copy and paste that list with newlines.
$ sudo dnf history info 565 Install kernel-5.17.14-300.fc36.x86_64
@updates
Install kernel-core-5.17.14-300.fc36.x86_64@updates
You did have a kernel update.
Install kernel-debug-core-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-extra-5.17.14-300.fc36.x86_64@updates
You must have been upgrading this system for quite a while. The debug kernel modules got accidentally pulled in back then. You can do "dnf remove kernel-debug*" to get rid of those.
I have no idea why hibernate stopped working, but it seems to not like something the BIOS is doing.
Dell systems recently got BIOS updates. My newest Dell system did a 2-step BIOS firmware update dance. The updates are dated May 22.
" - Firmware updates to address security vulnerabilities including (Common Vulnerabilities and Exposures - CVE) such as CVE-2022-0004, CVE-2022-0005, CVE-2022-21123, CVE-2022-21125, CVE-2022-21127, CVE-2022-21151, CVE-2022-21166, and CVE-2022-21181"
These might have introduced something in the BIOS that kernels "don't like". I see a bunch of driver firmware updates around the same time. If these are problematic there may be reports for for other distros.
Thank you, I did not update the BIOS for quite a while, so are you suggesting that I do so and see? I have not updated the BIOS for a few years actually, and I have forgotten how to do this for a non-Windows system. I think you do it from the BIOS, through a USB drive and that can be a .exe file.
So, could my not having updated the BIOS, and the kernel having upgraded, have caused the issue? I have not had this issue before with multiple updates/upgrades (with lots of machines) because I do unfortunately forget to check the BIOS all the time.
Best wishes, Ranjan
On 24/06/2022 13.47, Ranjan Maitra wrote:
On Fri Jun24'22 08:00:57AM, George N. White III wrote:
From: "George N. White III" gnwiii@gmail.com Date: Fri, 24 Jun 2022 08:00:57 -0300 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Fri, Jun 24, 2022 at 4:21 AM Samuel Sieb samuel@sieb.net wrote:
On 6/23/22 17:13, Ranjan Maitra wrote: [...]
Thanks! Here are the updates from last Wed and Thu:
Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15
09:00:01
PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 09:00:01 PM CDT 2022 -
I don't know what that is, but somehow you pasted it without newlines...
Yes, indeed, my apologies! But your suggestion below is far less of an
effort.
Run "dnf history", find the entry for that update (probably the first
one),
then run "dnf history info 38", but replace the 38 with the number of
the
entry. Copy and paste that list with newlines.
$ sudo dnf history info 565 Install kernel-5.17.14-300.fc36.x86_64
@updates
Install kernel-core-5.17.14-300.fc36.x86_64@updates
You did have a kernel update.
Install kernel-debug-core-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-extra-5.17.14-300.fc36.x86_64@updates
You must have been upgrading this system for quite a while. The debug kernel modules got accidentally pulled in back then. You can do "dnf remove kernel-debug*" to get rid of those.
I have no idea why hibernate stopped working, but it seems to not like something the BIOS is doing.
Dell systems recently got BIOS updates. My newest Dell system did a 2-step BIOS firmware update dance. The updates are dated May 22.
" - Firmware updates to address security vulnerabilities including (Common Vulnerabilities and Exposures - CVE) such as CVE-2022-0004, CVE-2022-0005, CVE-2022-21123, CVE-2022-21125, CVE-2022-21127, CVE-2022-21151, CVE-2022-21166, and CVE-2022-21181"
These might have introduced something in the BIOS that kernels "don't like". I see a bunch of driver firmware updates around the same time. If these are problematic there may be reports for for other distros.
Thank you, I did not update the BIOS for quite a while, so are you suggesting that I do so and see? I have not updated the BIOS for a few years actually, and I have forgotten how to do this for a non-Windows system. I think you do it from the BIOS, through a USB drive and that can be a .exe file.
So, could my not having updated the BIOS, and the kernel having upgraded, have caused the issue? I have not had this issue before with multiple updates/upgrades (with lots of machines) because I do unfortunately forget to check the BIOS all the time.
I just performed the BIOS update on my XPS 13. I did it like this:
sudo dnf install fwupd # only needed once, of course
sudo fwupdmgr get-devices sudo fwupdmgr refresh sudo fwupdmgr get-updates sudo fwupdmgr update
Best wishes, Ranjan _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 6/23/22 17:13, Ranjan Maitra wrote: [...]
Thanks! Here are the updates from last Wed and Thu: > >
> Wed Jun 15 09:00:01 PM CDT 2022 - DNF UPDATE STARTED Wed Jun 15
09:00:01
> PM CDT 2022 - *** CHECKING FOR DNF UPDATES *** Wed Jun 15 09:00:01 PM > CDT 2022 - Last metadata expiration check: 1:09:47 ago on Wed 15 Jun > 2022 07:50:16 PM CDT. Wed Jun 15 09:00:01 PM CDT 2022 - Dependencies > resolved. Wed Jun 15 09:00:01 PM CDT 2022 - Nothing to do. Wed Jun 15 > 09:00:01 PM CDT 2022 - I don't know what that is, but somehow you pasted it without newlines...
Yes, indeed, my apologies! But your suggestion below is far less of an
effort.
Run "dnf history", find the entry for that update (probably the first
one),
then run "dnf history info 38", but replace the 38 with the number of
the
entry. Copy and paste that list with newlines.
$ sudo dnf history info 565 Install kernel-5.17.14-300.fc36.x86_64
@updates
Install kernel-core-5.17.14-300.fc36.x86_64@updates
You did have a kernel update.
Install kernel-debug-core-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-5.17.14-300.fc36.x86_64@updates
Install kernel-debug-modules-extra-5.17.14-300.fc36.x86_64@updates
You must have been upgrading this system for quite a while. The debug kernel modules got accidentally pulled in back then. You can do "dnf remove kernel-debug*" to get rid of those.
I have no idea why hibernate stopped working, but it seems to not like something the BIOS is doing.
Dell systems recently got BIOS updates. My newest Dell system did a 2-step BIOS firmware update dance. The updates are dated May 22.
" - Firmware updates to address security vulnerabilities including (Common Vulnerabilities and Exposures - CVE) such as CVE-2022-0004, CVE-2022-0005, CVE-2022-21123, CVE-2022-21125, CVE-2022-21127, CVE-2022-21151, CVE-2022-21166, and CVE-2022-21181"
These might have introduced something in the BIOS that kernels "don't like". I see a bunch of driver firmware updates around the same time. If these are problematic there may be reports for for other distros.
Thank you, I did not update the BIOS for quite a while, so are you suggesting that I do so and see? I have not updated the BIOS for a few years actually, and I have forgotten how to do this for a non-Windows system. I think you do it from the BIOS, through a USB drive and that can be a .exe file.
So, could my not having updated the BIOS, and the kernel having upgraded, have caused the issue? I have not had this issue before with multiple updates/upgrades (with lots of machines) because I do unfortunately forget to check the BIOS all the time.
I just performed the BIOS update on my XPS 13. I did it like this:
sudo dnf install fwupd # only needed once, of course
sudo fwupdmgr get-devices sudo fwupdmgr refresh sudo fwupdmgr get-updates sudo fwupdmgr update
Thanks for this. fwupd was surreptitiously already installed but the rest were easy to do, and I appear to have got a firmware update now.
I was not aware of this utility, and this is extremely useful, so thanks very much for this.
However, my resume issue does not go away.
Btw, I did try
$ sudo dracut -f
and got a blank. Is this what i am supposed to get?
Many thanks again and best wishes, Ranjan
On 6/24/22 05:36, Ranjan Maitra wrote:
However, my resume issue does not go away.
You could try filing a bug on the kernel in the redhat bugzilla. Include the log lines that I extracted and your kernel cmdline.
Btw, I did try
$ sudo dracut -f
and got a blank. Is this what i am supposed to get?
Yes. That recreates the initramfs for the current kernel and doesn't print anything unless there's a problem.
Just an update: a recent update, likely to the kernel, from around two weeks ago, appears to have reliably fixed this issue. So, whatever was the problem, appears to no longer show up as a symptom.
Ranjan
On Wed Jun22'22 06:42:50AM, Ranjan Maitra wrote:
From: Ranjan Maitra mlmaitra@gmx.com Date: Wed, 22 Jun 2022 06:42:50 -0500 To: Community Support for Fedora Users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Many thanks and best wishes, Ranjan _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Spoken too soon. The latest updates no longer allow coming back from hibernate. I must note that I do have an external monitor attached to the laptop (which I did not when it worked two weeks ago when I was away) however, this has not been an issue in the past, but I wonder if that can explain anything.
Best wishes, Ranjan
On Wed Jul13'22 10:16:19AM, Ranjan Maitra wrote:
From: Ranjan Maitra mlmaitra@gmx.com Date: Wed, 13 Jul 2022 10:16:19 -0500 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Just an update: a recent update, likely to the kernel, from around two weeks ago, appears to have reliably fixed this issue. So, whatever was the problem, appears to no longer show up as a symptom.
Ranjan
On Wed Jun22'22 06:42:50AM, Ranjan Maitra wrote:
From: Ranjan Maitra mlmaitra@gmx.com Date: Wed, 22 Jun 2022 06:42:50 -0500 To: Community Support for Fedora Users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Many thanks and best wishes, Ranjan _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Hi, my Lenovo X1 is suffering the same issue since the upgrade to F36 (from F35, where hibernate was working fine).
As in the thread, I tried: - Upgrade firmware with fwupd - Boot old kernel (5.17 from F35) both for creating hibernating and resuming - With and without external monitor
Would it be possible to collect more debugging info than
"Hibernate inconsistent memory map detected! kernel: PM: hibernation: Image mismatch: architecture specific data"
Thanks!
Spoken too soon. The latest updates no longer allow coming back from hibernate. I must note that I do have an external monitor attached to the laptop (which I did not when it worked two weeks ago when I was away) however, this has not been an issue in the past, but I wonder if that can explain anything.
Best wishes, Ranjan
On Wed Jul13'22 10:16:19AM, Ranjan Maitra wrote:
From: Ranjan Maitra <mlmaitra(a)gmx.com> Date: Wed, 13 Jul 2022 10:16:19 -0500 To: Community support for Fedora users <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)
Just an update: a recent update, likely to the kernel, from around two weeks ago,
appears to have reliably fixed this issue. So, whatever was the problem, appears to no longer show up as a symptom.
Ranjan
On Wed Jun22'22 06:42:50AM, Ranjan Maitra wrote:
From: Ranjan Maitra <mlmaitra(a)gmx.com> Date: Wed, 22 Jun 2022 06:42:50 -0500 To: Community Support for Fedora Users <users(a)lists.fedoraproject.org> Reply-To: Community support for Fedora users
<users(a)lists.fedoraproject.org>
Subject: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and
upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Many thanks and best wishes, Ranjan _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
So, I have found that the following works semi-reliably.
I hibernate, with the external monitor on and connected, and the system goes down. THen, when I resume, I do not switch on the external monitor until the system comes back up (and it does). After it is up, I switch on the external monitor and then we appear to be fine.
I do not understand, and may be a voodoo observation and solution, but this problem did not appear to be an issue before 15 June 2022.
Many thanks and best wishes, Ranjan
On Sat Jul16'22 01:51:59PM, Ranjan Maitra wrote:
From: Ranjan Maitra mlmaitra@gmx.com Date: Sat, 16 Jul 2022 13:51:59 -0500 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Spoken too soon. The latest updates no longer allow coming back from hibernate. I must note that I do have an external monitor attached to the laptop (which I did not when it worked two weeks ago when I was away) however, this has not been an issue in the past, but I wonder if that can explain anything.
Best wishes, Ranjan
On Wed Jul13'22 10:16:19AM, Ranjan Maitra wrote:
From: Ranjan Maitra mlmaitra@gmx.com Date: Wed, 13 Jul 2022 10:16:19 -0500 To: Community support for Fedora users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Just an update: a recent update, likely to the kernel, from around two weeks ago, appears to have reliably fixed this issue. So, whatever was the problem, appears to no longer show up as a symptom.
Ranjan
On Wed Jun22'22 06:42:50AM, Ranjan Maitra wrote:
From: Ranjan Maitra mlmaitra@gmx.com Date: Wed, 22 Jun 2022 06:42:50 -0500 To: Community Support for Fedora Users users@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Dear friends,
I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem.
Many thanks and best wishes, Ranjan _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users@lists.stg.fedoraproject.org
-
Barry -
Federico Nebiolo -
George N. White III -
Ranjan Maitra -
Samuel Sieb -
Sjoerd Mullender