Bug 712157 - Kdump is not operational in RHEL6.1
Summary: Kdump is not operational in RHEL6.1
Keywords:
Status: CLOSED DUPLICATE of bug 734987
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-09 16:04 UTC by Steve Dickson
Modified: 2018-11-14 10:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-12 02:42:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
dmesg messages (52.25 KB, application/octet-stream)
2011-06-09 16:04 UTC, Steve Dickson 		no flags Details
cat /proc/iomem (3.04 KB, application/octet-stream)
2011-06-09 16:07 UTC, Steve Dickson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.