Bug 2115733 - Kernel 5.18.15-200 Not Working
Summary: Kernel 5.18.15-200 Not Working
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 36
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-05 07:57 UTC by Buford T. Justice
Modified: 2022-08-07 21:10 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-07 21:07:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg.txt (113.90 KB, text/plain)
2022-08-05 07:57 UTC, Buford T. Justice
no flags Details
All other present updates installed other than kernel 5.18.15-200.fc36.x86_64. (106.44 KB, image/png)
2022-08-05 07:57 UTC, Buford T. Justice
no flags Details
Serial numbers removed. Corrected version of dmesg.txt (113.88 KB, text/plain)
2022-08-05 08:18 UTC, Buford T. Justice
no flags Details

Description Buford T. Justice 2022-08-05 07:57:07 UTC
Created attachment 1903818 [details]
dmesg.txt

1. Please describe the problem:

Upon doing updates, the latest kernel update for 5.18.15-200 breaks my computer.  It will not boot.  It boots to black & white text and shows USB devices then stops.  I have to revert back to the Btrfs snapshot of root to use my computer.

2. What is the Version-Release number of the kernel:

5.18.15-200.fc36.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

The kernel I am using now that works perfectly fine is 5.18.13-200.fc36.x86_64.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Let either dnf or Discover download and install updates which has kernel 5.18.15-200.fc36.x86_64.  Reboot.  Fail.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Not sure if I want to use the rawhide kernel or not.  I did not do this.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

Not that I am aware of.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

I am not going to try kernel 5.18.15-200.fc36.x86_64 again.  I am not sure how I would even get this log since Fedora will not boot up for me with kernel 5.18.15-200.fc36.x86_64.  Kernel 5.18.13-200.fc36.x86_64 is working perfectly fine.  I will attach the log for it.

Comment 1 Buford T. Justice 2022-08-05 07:57:39 UTC
Created attachment 1903819 [details]
All other present updates installed other than kernel 5.18.15-200.fc36.x86_64.

Comment 2 Buford T. Justice 2022-08-05 08:00:12 UTC
uname -r says I am using kernel 5.18.15-200.fc36.x86_64.  Discover looks like I am using kernel 5.17.5-300.fc36.x86_64.  Strange.

Comment 3 Buford T. Justice 2022-08-05 08:05:45 UTC
It would be nice if Bugzilla allowed editing additional comments.  Grrr!

uname -r says I am using kernel 5.18.13-200.fc36.x86_64.  Discover looks like I am using kernel 5.17.5-300.fc36.x86_64.  Strange.

Comment 4 Buford T. Justice 2022-08-05 08:18:56 UTC
Created attachment 1903823 [details]
Serial numbers removed.  Corrected version of dmesg.txt

Please delete obsolete version.

Comment 5 alan.flambard 2022-08-06 10:27:53 UTC
Hello,
Starting fedora with version 5.18.16 of the kernel works.

Comment 6 Buford T. Justice 2022-08-06 10:30:11 UTC
Not for me.  As soon as I install it and reboot, I get a list of USB devices and nothing more.

Comment 7 Buford T. Justice 2022-08-07 21:07:06 UTC
5.18.16-200.fc36.x86_64 is working fine.  Thanks!


Note You need to log in before you can comment on or make changes to this bug.