Bug 712157

Summary: Kdump is not operational in RHEL6.1
Product: Red Hat Enterprise Linux 6 Reporter: Steve Dickson <steved>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: qcai
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-12 02:42:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg messages
none
cat /proc/iomem none

Description Steve Dickson 2011-06-09 16:04:08 UTC
Created attachment 503928 [details]
dmesg messages

Description of problem:
kdump refuse to start in the latest RHEL6.1 kernel.

Version-Release number of selected component (if applicable):
kernel-2.6.32-131.0.15.el6.x86_64
kexec-tools-2.0.0-188.el6.x86_64

How reproducible:
All the time.

Steps to Reproduce:
1. Added crashkernel=128M@32M to the kernel line in grub.conf
   (Note: I as tried crashkernel=128M@64M and crashkernel=128M@0M
    as well as justcrashkernel=128M)
2. rebooted
3. service kdump start - fails with 
     kdump: No crashkernel parameter specified for running kernel
  

Additional info:

cat /sys/kernel/kexec_crash_size == 0

Note, the following like is in the attached dmesg
Reserving 128MB of memory at 64MB for crashkernel (System RAM: 1996MB)

Comment 1 Steve Dickson 2011-06-09 16:07:00 UTC
Created attachment 503931 [details]
cat /proc/iomem

Comment 3 Qian Cai 2011-09-28 02:30:20 UTC
This looks like the initscript issue. Can you "chkconfig kdump on" and try it again?

Comment 6 Steve Dickson 2011-10-11 18:05:25 UTC
(In reply to comment #3)
> This looks like the initscript issue. Can you "chkconfig kdump on" and try it
> again?

This took care of the problem for me....

Comment 7 Qian Cai 2011-10-12 02:42:05 UTC

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