Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 748327

Summary: capture kernel load failed on ppc64
Product: Red Hat Enterprise Linux 6 Reporter: Dave Young <ruyang>
Component: kexec-toolsAssignee: 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:
Embargoed:

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.