Bug 2321671

Summary: Kernel Panic with 6.11.4-201 kernel
Product: [Fedora] Fedora Reporter: Edward <epp>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 40CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, josef, kernel-maint, linville, masami256, mchehab, ptalbert, steved, suraj.ghimire7
Target Milestone: ---Keywords: Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-05-20 20:07:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Photo of display showing last lines of the Kernel Panic output. none

Description Edward 2024-10-24 23:53:48 UTC
1. Please describe the problem:

Updated Fedora 40, which included a new kernel, 6.11.4-201. Upon a boot into the new kernel, it resulted in a Kernel Panic.

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

6.11.4-201.fc40

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 :

No.


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

Kernel Panic appears when booting into this kernel each time.

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``:

N/A

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

No.

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.

Unable to obtain due to kernel panic, required a boot into the previous kernel. Only log information available is from the successful boot into the previous kernel.

I am attaching a photo of the display showing the last lines of the output from the kernel panic.

Reproducible: Always

Comment 1 Edward 2024-10-24 23:55:04 UTC
Created attachment 2053577 [details]
Photo of display showing last lines of the Kernel Panic output.

Photo of display showing the last lines of the Kernel Panic output, before the system froze.

Comment 2 Edward 2024-10-25 17:31:20 UTC
Update:

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``:

No. Latest Rawhide kernel now installed and it boots perfectly.

Linux fedora 6.12.0-0.rc4.20241023gitc2ee9f594da8.41.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Oct 23 15:42:54 UTC 2024 x86_64 GNU/Linux

Comment 3 Aoife Moloney 2025-04-28 14:03:19 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2025-05-20 20:07:26 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.