Thanks for the follow-up — I've done further debugging, and it turns out
this isn't a dracut bug after all; the root cause is in the kernel
(7.3.0-9-generic). I'll refile against `linux`.
Summary of what I found:
- `dracut --force --debug` from a *settled* session completes fine
(no hang), including writing to /var/lib/kdump on the NVMe. So dracut
itself is not hanging.
- The freeze only happens at boot, when kdump-tools regenerates its
capture initrd before basic.target, and during the release-upgrade
dracut trigger.
- With `bash -x` on the dracut invocation, the freeze occurs during
filesystem I/O on the ext4/NVMe root fs, at *varying* points across
runs:
* `find`/getdents enumerating /usr/lib/modules/7.3.0-9-generic/kernel/…
* `sync`/`syncfs` right after "*** Creating initramfs image file …
done ***"
- The recurring last kernel message across every hang is:
block nvme0n1: the capability attribute has been deprecated
(a change specific to the 7.3 kernel).
So dracut completes its work; the system freezes on NVMe I/O during
early boot on 7.3. Workaround: pre-generate the kdump initrd so dracut
doesn't run at boot.
Thanks again — refiling against the kernel.
** Changed in: dracut (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2171438
Title:
dracut initrd generation hangs during do-release-upgrade (26.04→26.10)
and at boot via kdump-tools
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2171438/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
