Bug 1298386 - Kernel panic on boot
Kernel panic on boot
Product: Fedora
Classification: Fedora
Component: grubby (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-13 18:27 EST by Trond Aasan
Modified: 2016-12-20 12:52 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 12:52:21 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Photo of crash screen (679.46 KB, image/png)
2016-01-13 18:27 EST, Trond Aasan
no flags Details
contents of /var/log/grubby (5.47 KB, text/plain)
2016-01-13 20:09 EST, Trond Aasan
no flags Details
contents of /boot/grub2/grub.cfg (7.16 KB, text/plain)
2016-01-13 20:45 EST, Trond Aasan
no flags Details

  None (edit)
Description Trond Aasan 2016-01-13 18:27:25 EST
Created attachment 1114610 [details]
Photo of crash screen

Description of problem:
Kernel panic on boot

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot

Actual results:
Kernel panic

Expected results:

Additional info:
kernel-debug 4.3.3-300.fc23 boots OK, but no WIFI
4.2.x booted OK
Comment 1 Josh Boyer 2016-01-13 18:33:16 EST
Your initramfs is missing or broken, or the stanza in the grub.conf file is missing the initrd line to load it.
Comment 2 Trond Aasan 2016-01-13 18:53:57 EST
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 
	initrd16 /boot/initramfs-4.3.3-300.fc23.x86_64+debug.img
	initrd16 /boot/initramfs-4.2.8-300.fc23.x86_64.img
	initrd16 /boot/initramfs-4.2.7-300.fc23.x86_64.img
	initrd16 /boot/initramfs-0-rescue-95814f5053d94c9fad5ed43fe1cb2781.img
Comment 3 Josh Boyer 2016-01-13 19:22:35 EST
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.
Comment 4 Trond Aasan 2016-01-13 19:37:41 EST
initrd16 seems to come from /etc/grub.d/10_linux

  case "$machine" in

and later:
   initrd${sixteenbit} ${rel_dirname}/${initrd}

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.
Comment 5 Brian Lane 2016-01-13 20:00:53 EST
Please attach /var/log/grubby as a text/plain attachment, that might shed some light on it.
Comment 6 Trond Aasan 2016-01-13 20:09 EST
Created attachment 1114628 [details]
contents of /var/log/grubby
Comment 7 Trond Aasan 2016-01-13 20:45 EST
Created attachment 1114629 [details]
contents of /boot/grub2/grub.cfg
Comment 8 Trond Aasan 2016-01-13 20:48:31 EST
grub2-mkconfig seems to work as expected though

$ /usr/sbin/grub2-mkconfig -o test.cfg

$ grep initramfs test.cfg 
	initrd16 /boot/initramfs-4.3.3-300.fc23.x86_64.img
	initrd16 /boot/initramfs-4.2.8-300.fc23.x86_64.img
	initrd16 /boot/initramfs-4.2.7-300.fc23.x86_64.img
	initrd16 /boot/initramfs-4.3.3-300.fc23.x86_64+debug.img
	initrd16 /boot/initramfs-0-rescue-95814f5053d94c9fad5ed43fe1cb2781.img
Comment 9 Fedora End Of Life 2016-11-24 09:55:12 EST
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'
of '23'.

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.
Comment 10 Fedora End Of Life 2016-12-20 12:52:21 EST
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.

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