On Fri, Jun 24, 2022 at 4:21 AM Samuel Sieb <sam...@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.

-- 
George N. White III
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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

Reply via email to