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.

Bug 1972463

Summary: [RHEL9] kdump kernel: failed to switch to dump_to_rootfs if initial dumping failed. Stuck at: "Waiting for rootfs mount, will timeout after 90 seconds "
Product: Red Hat Enterprise Linux 9 Reporter: Jie Li <jieli>
Component: kexec-toolsAssignee: kdump-bugs <kdump-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Jie Li <jieli>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: coxu, cye, dracut-maint-list, dtardon, ltao, qzhang, ruqin, ruyang, xiawu, yfu, yihyu, yiyan, zhenyzha
Target Milestone: betaKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kexec-tools-2.0.22-11.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-07 21:50:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1971841    

Comment 6 Kairui Song 2021-07-01 19:52:58 UTC
Following patch should solve the problem, tested with the beaker job:

https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/EJAYSCJWUQCBY3F73FXYDKQN2UQ4RFZC/

Comment 8 Coiby 2021-07-15 05:14:11 UTC
(In reply to Kairui Song from comment #6)
> Following patch should solve the problem, tested with the beaker job:
> 
> https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/
> thread/EJAYSCJWUQCBY3F73FXYDKQN2UQ4RFZC/

Hi,

When testing the kdump functionality for ARM machine, I found with "systemctl cancel" before "systemctl start sysroot.mount", this issue still bothers this aarch64 machine hp-moonshot-03-c03.lab.eng.rdu2.redhat.com. The system would hang after printing "Waiting for rootfs mount, will timeout after 90 seconds". For the details, you can check http://lab-02.hosts.prod.upshift.rdu2.redhat.com/beaker/logs/recipes/10295+/10295475/console.log.

Comment 9 Kairui Song 2021-07-18 16:19:56 UTC
Hi Coiby, can you share the kdump.conf file and how did you trigger the initqueue failure? Previously QE configured kdump to dump to another partition and wiped the partition before the dump start so kdump will fail to setup the partition. How did you created the dump failure?

Comment 10 Coiby 2021-07-19 00:59:59 UTC
(In reply to Kairui Song from comment #9)
> Hi Coiby, can you share the kdump.conf file and how did you trigger the
> initqueue failure? Previously QE configured kdump to dump to another
> partition and wiped the partition before the dump start so kdump will fail
> to setup the partition. How did you created the dump failure?

The iniqueque failure happened without doing anything. I changed failture_action to dump_to_rootfs because I knew your patch and wanted to know if kdump works for ARM in this situcation.