Description of problem:
The arch_default_crash_size function in kernel/kexec.c tries to figure out the automatic size to use for the crashkernel. The existing calculation turns out to be independent of the system_ram -- it's always 135266304 (129M) for any reasonable values of system_ram.
A comment in the code indicates that the calculation is meant to use a 1:8192 ratio. This could be done by changing the (1ULL<<23) to (1ULL<<13).
It's not clear that this should be the calculation or if it should be something else. Larger memory systems will certainly consume more slab space and result in the 70% warning when running mkdumprd.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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.
Hi kdump developer,
Any update for this bug?
(In reply to Wayne H. Badger from comment #0)
> It's not clear that this should be the calculation or if it should be
> something else. Larger memory systems will certainly consume more slab
> space and result in the 70% warning when running mkdumprd.
Please let us know a use-case or reproducer where we can reproduce warning when running mkdumprd with current crash size allocation scheme.
Closing , because it is working in current release as per comment 6.
The main part of this ticket was fixed in 2011. In the 5 years since this ticket was created, we have not noticed additional issues with kdump related to this ticket.