Bug 1047541 - kernel panic early in boot
Summary: kernel panic early in boot
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
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: 2013-12-31 15:52 UTC by sean darcy
Modified: 2014-01-02 01:31 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-02 01:31:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
top half of screen after panic (2.15 MB, image/jpeg)
2013-12-31 15:52 UTC, sean darcy
no flags Details
bottom of screen after panic (1.88 MB, image/jpeg)
2013-12-31 15:53 UTC, sean darcy
no flags Details
early dmesg from kernel-3.11.10-100.fc18.x86_64 (52.23 KB, text/plain)
2013-12-31 16:10 UTC, sean darcy
no flags Details

Description sean darcy 2013-12-31 15:52:23 UTC
Created attachment 843823 [details]
top half of screen after panic

Description of problem:
kernel panic on boot

Version-Release number of selected component (if applicable):
kernel-3.12.5-200.fc19.x86_64

How reproducible:
boot kernel

Steps to Reproduce:
1.boot kernel
2.
3.

Actual results:

kernel panic. The screen scrolls beyond the beginning of the panic. I'm attaching screen shots of what does show on the console. It's too early in boot for any logging.

Expected results:

boot

Additional info:

I've just upgraded to 19 from 18. kernel-3.11.10-100.fc18.x86_64 boots without problems.

I've attached two jpeg's of the screen after the panic. Also, I've attached a text file of dmesg from a boot of kernel-3.11.10-100.fc18.x86_64.

Comment 1 sean darcy 2013-12-31 15:53:34 UTC
Created attachment 843824 [details]
bottom of screen after panic

Comment 2 sean darcy 2013-12-31 16:10:43 UTC
Created attachment 843826 [details]
early dmesg from kernel-3.11.10-100.fc18.x86_64

Comment 3 Michele Baldessari 2014-01-01 09:54:41 UTC
Hi Sean,

the panic happens in init/do_mounts.c:mount_block_root() and is explicitely
forced by the kernel because it has not been able to find the specified
root (UUID=0ee4b2cd-0143-4172-9d7f-c1bef74a1150): panic("VFS: Unable to mount root fs on %s", b);

This can happen for different reasons. My first thought would be that the
initrd file is missing some driver or has some other issues (although other
causes are certainly possible).

Could you attach /boot/grub2/grub.cfg and the initrd file under /boot 
corresponding to the 3.12.5 kernel?

Thanks,
Michele

Comment 4 sean darcy 2014-01-02 01:31:26 UTC
You put me on the right path: initramfs-3.12.5-200.fc19.x86_64.img was not installed. I reinstalled the kernel, and all is well.

It seems there was some error by fedup on the upgrade.

Thanks for the help.
sean


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