Bug 1045879 - Kernel panic on boot after upgrade to 3.12 kernel
Summary: Kernel panic on boot after upgrade to 3.12 kernel
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grubby
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-22 18:57 UTC by ajs
Modified: 2015-02-17 19:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:45:19 UTC
Type: Bug


Attachments (Terms of Use)
Photo of laptop screen after kernel panic (1.11 MB, image/png)
2013-12-22 18:57 UTC, ajs
no flags Details

Description ajs 2013-12-22 18:57:46 UTC
Created attachment 840406 [details]
Photo of laptop screen after kernel panic

Description of problem:
When attempting to boot with the latest f19 kernel, I get a kernel panic before I should be prompted for the password for my encrypted root partition.

Booting to the following kernels still works:
kernel-3.11.10-200.fc19.x86_64
kernel-3.11.9-200.fc19.x86_64
kernel-3.11.8-200.fc19.x86_64
kernel-3.11.7-200.fc19.x86_64


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

How reproducible:
Always

Steps to Reproduce:
1. boot
2. select 3.12.5 kernel
 
Actual results:
kernel panic

(See attached photo)


Expected results:
prompt for password to encrypted root partition

Additional info:
If there is something else that I can do to collect more information, please let me know.

Comment 1 Josh Boyer 2013-12-24 14:13:42 UTC
The kernel can't find the rootfs.  You are most likely either missing a corresponding initramfs file in /boot, or the grub configuration file is missing the initrd line that laods it.  Please check those two things.

Comment 2 ajs 2013-12-27 18:13:21 UTC
I had to both create the initramfs file and add the initrd line to grub.cfg.

Everything is now booting fine.

When I couldn't boot to the new kernel after yum updating, I booted to an older kernel to search /v/l/yum.log and /v/l/messages for errors but I didn't find anything.  Shouldn't there be an error message somewhere?

Comment 3 Fedora End Of Life 2015-01-09 20:56:08 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 4 Fedora End Of Life 2015-02-17 19:45:19 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
bug.

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.