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:
64k arm kernel failed to output module_summary and module_top info on hpe-apache-cn99xx-10.khw4.lab.eng.bos.redhat.com with rd.memdebug=5 when dong nfs dump.
Version-Release number of selected component (if applicable):
RHEL-9.2.0-20230115.7
How reproducible:
always
Steps to Reproduce:
1. Install&boot 64k kernel 5.14.0-228.dd64kv4.el9.aarch64+64k and install memstrack
2. Set up nfs dumping
3. Append rd.memdebug=5 to KDUMP_COMMANDLINE_APPEND in /etc/sysconfig/kdump
4. kdumpctl restart
5. Trigger kernel crash
Actual results:
No module_summary and module_top info is printed.
Expected results:
module_summary and module_top should be printed.
Additional info:
1. If I make kdump.sh wait 20s after finishing local dumping, module_summary and module_top info can be printed successfully.
2. This issue is not found on 4k arm kernel for nfs dumping. But it can also reproduced for local dumping.
I notice this issue can also reproduced for 4k kernel with local dumping. So actually there are two issues,
1) memstrack-report.sh which reports module_summary and module_top info is installed as a dracut cleanup hook but it doesn't have a chance to be executed when vmcore dumping is finished early
2) vmcore dumping is done slower for 64k arm kernel compared with 4k arm kernel