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-tools | Assignee: | Pingfan Liu <piliu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jie Li <jieli> |
| Severity: | unspecified | Docs Contact: | Sujata Kurup <skurup> |
| Priority: | unspecified | ||
| Version: | 9.0 | CC: | bgoncalv, coxu, dyoung, efuller, lkuprova, piliu, ruyang, skurup, xiawu |
| Target Milestone: | rc | Keywords: | 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
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 |