Bug 748327

Summary:	capture kernel load failed on ppc64
Product:	Red Hat Enterprise Linux 6	Reporter:	Dave Young <ruyang>
Component:	kexec-tools	Assignee:	Dave Young <ruyang>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1
Target Milestone:	rc
Target Release:	---
Hardware:	ppc64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-08 06:58:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Young 2011-10-24 06:47:36 UTC

Description of problem:

Failed to load kdump kernel on a ppc64 machine ibm-js22-vios-03-lp2.rhts.eng.brq.redhat.com

boot with crashkernel=256M@256M

remove the 2>/dev/null after kexec in /etc/init.d/kdump, will see:

[root@ibm-js22-vios-03-lp2 ~]# /etc/init.d/kdump start
get memory ranges:1
Could not find a free area of memory of f9a458 bytes...
Could not find a free area of memory of 1416f9d bytes...
Cannot load /boot/vmlinuz-2.6.32-131.0.15.el6.ppc64
Starting kdump:[FAILED]


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


How reproducible:


Steps to Reproduce:
1. set the crashkernel param and boot
2. /etc/init.d/kdump start
3.
  
Actual results:

service failed to load the capture kernel

Expected results:

service start ok and load capture kernel into memory


Additional info:

Comment 2 RHEL Program Management 2011-10-28 05:47:21 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Dave Young 2011-11-08 06:58:50 UTC

mahesh.ibm.com point out:
On Power, crashkernel base addr must fall inside RMO region. The is
because ppc64 kernel needs some of its memory in the RMO region. The
memory ranges below shows that the system has RMO region of size 128M,
Hence crashkernel base addr @64M should work just fine.

So the crashkernel base should be within 128M.