Bug 909601 - Panic booting 3.7.6-201, 3.7.5-201 boots OK. Encrypted / partition.
Summary: Panic booting 3.7.6-201, 3.7.5-201 boots OK. Encrypted / partition.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-09 18:57 UTC by Madison Kelly
Modified: 2013-03-27 18:42 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-27 18:42:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
pic of panic (1.84 MB, image/jpeg)
2013-02-09 18:57 UTC, Madison Kelly
no flags Details

Description Madison Kelly 2013-02-09 18:57:10 UTC
Created attachment 695537 [details]
pic of panic

Description of problem:

I updated my laptop to 3.7.6-201 and rebooted. Twice it panic'ed with "kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)". I suspect this is related to my disk being encrypted (LVM with <swap> and / being encrypted). Booting into 3.7.5-201 works fine.

Crappy cellphone pic of panic is attached.

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

Works:
kernel.x86_64 ver 3.7.5-201.fc18

Panics:
kernel.x86_64 ver 3.7.6-201.fc18

How reproducible:

100% (on two tries)

Steps to Reproduce:
1. Install kernel
2. Have encrypted LV for / and <swap>
3. Boot
  
Actual results:

panics

Expected results:

boots

Additional info:

Comment 1 Josh Boyer 2013-02-11 12:43:28 UTC
Do you have an initramfs file in /boot for 3.7.6-201?  If so, does it look to be of similar size as 3.7.5-201?

This is basically the error the kernel gives when it can't find the rootfs that has been specified.  Without seeing the full boot logs, it's difficult to say what went wrong.  However, I don't believe there were any changes in this area of the kernel between 3.7.5 and 3.7.6, so it could very well be a problem in the generated initramfs.

Comment 2 Jack Scheible 2013-02-14 16:43:42 UTC
I've got the same issue.

The initramfs files are similar in size.

-rw-------. 1 root root 32092348 Jan 27 12:43 initramfs-3.7.4-204.fc18.x86_64.img
-rw-------. 1 root root 32045708 Feb 14 11:19 initramfs-3.7.6-201.fc18.x86_64.img

-Jack

Comment 3 Justin M. Forbes 2013-03-13 17:02:05 UTC
Is this still an issue with 3.8.2 kernels?

Comment 4 Justin M. Forbes 2013-03-27 18:42:03 UTC
Closing this bug as it has been more than 2 weeks without a response. I assume the issue is no longer occurring. Please feel free to reopen if this is not the case.


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