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 2065013

Summary: RHEL9[aarch64:ampere-mtjade-altra-*] kdump cannot reserve memory on mtjade machines
Product: Red Hat Enterprise Linux 9 Reporter: Jie Li <jieli>
Component: kexec-toolsAssignee: Pingfan Liu <piliu>
Status: CLOSED CURRENTRELEASE QA Contact: Jie Li <jieli>
Severity: unspecified Docs Contact: Sujata Kurup <skurup>
Priority: unspecified    
Version: 9.0CC: bgoncalv, coxu, dyoung, efuller, lkuprova, piliu, ruyang, skurup, xiawu
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
.Allocating crash kernel memory fails at boot time On certain Ampere Altra systems, allocating the crash kernel memory for `kdump` usage fails during boot when the available memory is below 1 GB. Consequently, the `kdumpctl` command fails to start the `kdump` service. To workaround this problem, do one of the following: * Decrease the value of the `crashkernel` parameter by a minimum of 240 MB to fit the size requirement, for example `crashkernel=240M`. * Use the `crashkernel=x,high` option to reserve crash kernel memory above 4 GB for `kdump`. As a result, the crash kernel memory allocation for `kdump` does not fail on Ampere Altra systems.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-06 09:26:56 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:

Comment 7 Jaroslav Klech 2022-04-04 12:13:30 UTC 
Re-assiging to Sujata
Comment 28 Pingfan Liu 2022-12-30 13:50:05 UTC 
It should share the same solution with https://bugzilla.redhat.com/show_bug.cgi?id=2112877.

Now the kernel can automatically fall back to a proper region to reserve the crash region