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.

Description of problem:

According to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/7.2_Release_Notes/Red_Hat_Enterprise_Linux-7-7.2_Release_Notes-en-US.pdf, there has word as "system with large memory size".

How much bigger is large memory size? above 64GB? or how much of memory?


Version-Release number of selected component (if applicable):
- Red Hat Enterprise Linux 7.2 Release Note


How reproducible:
- it is document.


Steps to Reproduce:
1.
2.
3.

Actual results:
- write down specific memory size what large memory size is.


Expected results:


Additional info:

Hi,

I removed the mention of "large memory size" from the doc text - it wasn't the point of the message, it was just an aside and removing it doesn't change much.

FYI, there was no set size that was causing problems - it wasn't like "it was fine with 1 CPU as long as the memory was under 64 GB, above that kdump was always having issues". Using multiple CPUs prevents problems that *could* happen, and generally speeds up the process, depending on some other factors (e.g. target disk write speed). 

Of course, the more memory you have, the more time you save with the speedup - if adding a 2nd CPU made kdump twice as fast, then you might save 15 seconds on a 2GB RAM system and 1500 seconds on a 200GB RAM system.

Hope that clears it up.

- Petr

I have republished the Release Notes with the fixed description of Bug 1182376:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.2_Release_Notes/technology-preview-kernel.html