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.
Created attachment 440517[details]
Logs running mkdumprd
Description of problem:
I am trying to create a kdump image by running mkdumprd. My purpose is to create a custome kdump image after adding some new drivers. Now I found that basic mkdumprd command itself is not working..
I ran the following command..
#mkdumprd -v -f /boot/initrd-2.6.32-44.el6.x86_64kdump1.img `uname -r`
Found that this command never completes.
Version-Release number of selected component (if applicable):
#uname -a
Linux myMachine 2.6.32-59.el6.x86_64 #1 SMP Wed Aug 4 12:47:47 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
How reproducible:
Consistantly everytime..
Steps to Reproduce:
1. Install RHEL 6.
2. Run the command mkdumprd.
Actual results:
Command never completes..
Expected results:
Command completes and generates the kdump image..
Additional info:
I have attached the logs after running this command.
Note: The easy workaround for this bug, if encountered in the field, until it is fixed properly in 6.1, is to create an empty /etc/modprobe.conf file, or empty /etc/modprobe.d/modprobe.conf file via:
touch /etc/modprobe.d/modprobe.conf
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0736.html
Comment 9Charlotte Richardson
2011-06-30 14:18:36 UTC
This still happens on RHEL 6.1 GA, which has kexec-tools-2.0.0-188.el6. It is not reproducible on demand for us, at least not yet, probably meaning it is a race condition due to having 24 CPUs running. I verified that the mkdumprd does include the suggested patch.
Charlotte, if you find some way to reproduce it, please file a new BZ.
Thanks.
Comment 11Charlotte Richardson
2011-07-05 13:10:34 UTC
Will do. I've never managed to reproduce it myself, but three different engineers have seen it, one of them twice, when IPLing 6.1 systems. It appears that the loop at depsolve_modlist never exits, and it seems to have something to do with having installed some patched drivers that occlude the standard ones by being in /lib/modules/<kernel>/updates. In one case we know that mkdumprd got hung up there trying to resolve dependencies for the fusion drivers we have to patch, which are mptbase, mptsas, and mptscsih. Unknown what happened in the other cases. The problem never reproduces even when the same person reinstalls the same system in the exact same way, which makes it feel like a timing problem to me (these are 24-core systems, so plenty of chances for those sorts of bugs). That's all I know at present, sorry!
Comment 12Charlotte Richardson
2011-07-05 19:24:36 UTC
Created attachment 440517 [details] Logs running mkdumprd Description of problem: I am trying to create a kdump image by running mkdumprd. My purpose is to create a custome kdump image after adding some new drivers. Now I found that basic mkdumprd command itself is not working.. I ran the following command.. #mkdumprd -v -f /boot/initrd-2.6.32-44.el6.x86_64kdump1.img `uname -r` Found that this command never completes. Version-Release number of selected component (if applicable): #uname -a Linux myMachine 2.6.32-59.el6.x86_64 #1 SMP Wed Aug 4 12:47:47 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Consistantly everytime.. Steps to Reproduce: 1. Install RHEL 6. 2. Run the command mkdumprd. Actual results: Command never completes.. Expected results: Command completes and generates the kdump image.. Additional info: I have attached the logs after running this command.