Bug 1010331 - Kernel panic on boot 3.11.1-200.fc19.x86_64
Summary: Kernel panic on boot 3.11.1-200.fc19.x86_64
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
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: 2013-09-20 14:13 UTC by Karandeep Chahal
Modified: 2013-09-20 20:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-20 20:31:42 UTC
Type: Bug

Attachments (Terms of Use)
Screenshot of panic (2.62 MB, image/jpeg)
2013-09-20 14:13 UTC, Karandeep Chahal 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Karandeep Chahal 2013-09-20 14:13:32 UTC 
Created attachment 800516 [details]
Screenshot of panic

Description of problem:


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


How reproducible: 100%


Steps to Reproduce:
1. Power on PC boot kernel vmlinuz-3.11.1-200.fc19.x86_64
2.
3.

Actual results:
Kernel panic

Expected results:
No kernel panic

Additional info:
Comment 1 Josh Boyer 2013-09-20 18:37:46 UTC 
Please make sure you have a corresponding initramfs file in /boot with that kernel, and that your grub configuration file has it listed in the initrd line.
Comment 2 Karandeep Chahal 2013-09-20 20:07:37 UTC 
Yep. the initrd was not installed. I do not know how that happened. 'yum update' must have run into some problems. Anyroad, I removed and reinstalled the kernel.
Comment 3 Josh Boyer 2013-09-20 20:31:42 UTC 
(In reply to Karandeep Chahal from comment #2)
> Yep. the initrd was not installed. I do not know how that happened. 'yum
> update' must have run into some problems. Anyroad, I removed and reinstalled
> the kernel.

There's an issue somewhere in the rpm/grubby/dracut interaction.  There are already multiple bugs open for that, so we'll close this out.  Thanks.
Note You need to log in before you can comment on or make changes to this bug.