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:
kdump service takes a few seconds to start even no need to rebuild initramfs, which is a little longer compared to other systemd services, it may affects the system boot time a little, we better optimize it as possible as we can.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
kdump service takes a few seconds to start even no need to rebuild initramfs.
The main root cause of this is the use of "lsinitrd".
Expected results:
kdump service starts every boot quickly.
Additional info:
After some tests I found that the list_modules and list_files function in lsinitrd would cause 13%~15% overhead on kdumpctl start with or without rebuilding initramfs.
The point is that, the scripts calling lsinitrd may not need all the information currently given by it. For example, the image built by dracut will not change if list_modules and list_files calls are removed, according to my experiments.
Maybe we need make lsinitrd more customizable, in which condition we can selectively show image information that we want only.
If argument -m(--mod) is not given, the $modules variable controlled by would be set to 0, which leads to list_modules and list_files to be executed, which caused serious overhead:
if [ "$modules" -eq 1 ]; then
list_modules
echo "========================================================================"
else
echo -n "Arguments: "
$CAT "$image" | cpio --extract --verbose --quiet --to-stdout -- \
$(dracutlibdirs build-parameter.txt) 2>/dev/null
echo
list_modules
list_files
(In reply to glennduffy from comment #9)
> I am running into this issue too. Can someone provide instructions on how to
> configure kdump to mitigate this?
It's been solved in the latest version(since kexec-tools-2.0.14-10.el7), please update it.
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.
https://access.redhat.com/errata/RHBA-2017:2300