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.

Description of problem:

Provide a kdump option so that memory usage can be logged in second kernel at various stages. This can be useful to determine how much memory is needed in second kernel and in debugging to figure out who is consuming most memory.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

We are now going to ship little modified crashkernel=auto logic in kdump and we are hoping that will work out of the box on 80% of x86 configurations by default. If it does not above debugging aid should be useful to give some idea who is consuming the memory. So 6.2 sounds like the right time to ship it out in kexec-tools.

Hi, Vivek,

POST status is invalid for kexec-tools bugs. What's more, Jan's patch is against Fedora, doesn't apply to RHEL6, so I need to re-generate the patch.

Tested with RHEL6.2-20110907.+kernel-2.6.32-198.el6+kexec-tools-2.0.0-202.el6, all PASS:
===================================
0  PASS
1  PASS
2  PASS
3  PASS

https://beaker.engineering.redhat.com/jobs/133148

Change status to VERIFIED.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1532.html