Bug 964346

Summary: Kernel panic at boot time after upgrading from kernel 3.8.9-200 to 3.9.2-200
Product: [Fedora] Fedora Reporter: lu.error
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: gansalmon, itamar, jonathan, kernel-maint, lu.error, madhu.chinakonda, the.ridikulus.rat
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-18 01:21:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
A photo of the screen capturing the kernel 3.9.2-200 oops and panic.
none
Transcript of the previous attachment. none

Description lu.error 2013-05-18 00:48:27 UTC
Created attachment 749512 [details]
A photo of the screen capturing the kernel 3.9.2-200 oops and panic.

Description of problem:
A kernel panic occurs after a kernel oops, when trying to boot kernel 3.9.2-200 after an upgrade from kernel 3.8.9-200.

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

How reproducible:
Always.

Steps to Reproduce:
1. Install Fedora 18 and fully upgrade no further than to kernel-3.8.9-200.fc18.x86_64.
2. Perform "sudo yum upgrade".
3. Reboot and at the bootscreen choose "Fedora 18 (3.9.2-200.fc18.x86_64)".
  
Actual results:
[   3.299809] BUG: unable to handle kernel NULL pointer dereference at           (null)
[   3.299854] IP: [<ffff88003a12dfed>] 0xffff88003a12dfec
[   3.299875] PGD 0
[   3.299886] Oops: 0002 [#1] SMP
[   3.299903] Modules linked in:
[   3.299917] CPU 2
 ...
[   3.300945] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[   3.300945]
_

See the attachments for a picture of the screen and a full transcription of the picture.

Expected results:
Successful boot of kernel-3.9.2-200.fc18.x86_64.

Additional info:
kernel-3.8.11-200.fc18.x86_64 does not seem to be affected by this problem; in other words I can succesfully boot with kernel-3.8.9-200.fc18.x86_64 and kernel-3.8.11-200.fc18.x86_64.

Kernel parameters for kernel-3.8.9-200.fc18.x86_64, kernel-3.8.11-200.fc18.x86_64, kernel-3.9.2-200.fc18.x86_64 are (from /etc/default/grub):

GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 acpi_apic_instance=2 acpi_backlight=vendor discard elevator=noop log_buf_len=1M vconsole.keymap=dk-latin1 rhgb quiet"

Comment 1 lu.error 2013-05-18 00:52:03 UTC
Created attachment 749513 [details]
Transcript of the previous attachment.

Comment 2 lu.error 2013-05-18 01:21:03 UTC

*** This bug has been marked as a duplicate of bug 964335 ***