Red Hat Bugzilla – Bug 1298386
Kernel panic on boot
Last modified: 2016-12-20 12:52:21 EST
Created attachment 1114610 [details]
Photo of crash screen
Description of problem:
Kernel panic on boot
Version-Release number of selected component (if applicable):
Steps to Reproduce:
kernel-debug 4.3.3-300.fc23 boots OK, but no WIFI
4.2.x booted OK
Your initramfs is missing or broken, or the stanza in the grub.conf file is missing the initrd line to load it.
Tried to reinstall kernel packed, but nothing changed
$ ls -ltr /boot/initramfs-*
-rw-rw-r--. 1 root root 50958974 des. 18 07:01 /boot/initramfs-0-rescue-95814f5053d94c9fad5ed43fe1cb2781.img
-rw-r--r--. 1 root root 19397058 des. 18 07:48 /boot/initramfs-4.2.7-300.fc23.x86_64.img
-rw-r--r--. 1 root root 19386095 des. 23 14:14 /boot/initramfs-4.2.8-300.fc23.x86_64.img
-rw-r--r--. 1 root root 19455645 jan. 13 01:19 /boot/initramfs-4.3.3-300.fc23.x86_64.img
-rw-r--r--. 1 root root 19489718 jan. 13 23:44 /boot/initramfs-4.3.3-300.fc23.x86_64+debug.img
$ grep initramfs /boot/grub2/grub.cfg
The output you've pasted would seem to correlate with what I said earlier. You have an initramfs file for both 4.3.3-300.fc23.x86_64 and 4.3.3-300.fc23.x86_64+debug, but you do not show a corresponding initrd line for the 4.3.3-300.fc23.x86_64 kernel.
Also, I have no idea why your grub config uses initrd16 but that is likely unrelated.
initrd16 seems to come from /etc/grub.d/10_linux
case "$machine" in
But yes, probably unrelated.
It looks like the kernel install scripts somehow skips writing the inintrd to /boot/grub2/grub.cfg
I'm sorry, but I think this is how far my knowledge of fedora goes, just a user, not a hacker.
Please attach /var/log/grubby as a text/plain attachment, that might shed some light on it.
Created attachment 1114628 [details]
contents of /var/log/grubby
Created attachment 1114629 [details]
contents of /boot/grub2/grub.cfg
grub2-mkconfig seems to work as expected though
$ /usr/sbin/grub2-mkconfig -o test.cfg
$ grep initramfs test.cfg
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.