Bug 2335126 - 6.12.7 makes kernel panic while booting
Summary: 6.12.7 makes kernel panic while booting
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 41
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-01 06:39 UTC by Christoph Karl
Modified: 2025-01-03 15:41 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-03 15:41:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
No block devices (180.19 KB, image/jpeg)
2025-01-01 06:45 UTC, Christoph Karl
no flags Details
Bootup screen (147.65 KB, image/jpeg)
2025-01-01 07:20 UTC, Christoph Karl
no flags Details
Part of dmesg (289.59 KB, image/jpeg)
2025-01-01 07:21 UTC, Christoph Karl
no flags Details

Description Christoph Karl 2025-01-01 06:39:34 UTC
1. Please describe the problem:
Kernel panic while booting:
KERNEL PANIC!
Please reboot your computer.
Attempted to kill init! exitcode=0x00007f00


2. What is the Version-Release number of the kernel:
kernel-6.12.7-200.fc41.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 :
First appears with 6.12.7.
6.12.6 is working fine


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Just boot this version of kernel


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


6. Are you running any modules that not shipped with directly Fedora's kernel?:
Yes, "xorg-x11-drv-nvidia-565.77-3.fc41.x86_64"

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 tried to boot with debug kernel 6.12.7, but it seems that no block devices are present,
so I cannot copy something on an USB device.


Reproducible: Always

Comment 1 Christoph Karl 2025-01-01 06:45:46 UTC
Created attachment 2064404 [details]
No block devices

Seems that there are no block devices.
(Sorry for the bad quality)

Comment 2 Christoph Karl 2025-01-01 07:20:56 UTC
Created attachment 2064405 [details]
Bootup screen

What is on my bootup screen in debug mode.

Comment 3 Christoph Karl 2025-01-01 07:21:59 UTC
Created attachment 2064406 [details]
Part of dmesg

Seems modules cannot be loaded (?)

Comment 4 Christoph Karl 2025-01-03 15:41:22 UTC
Uninstalling and reinstalling solved the problem.
Reason unclear.


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