Kernel team, looks like the root cause identified by IBM (taken from description of the bug) is:
== Comment: #8 - Hari Krishna Bathini <> - 2018-06-26 06:06:13 == The dump target (/var/crash) is on NVMe device (also, the root disk). But the kdump initrd is not being built with nvme driver modules. Eventually, nvme disk is not found and kdump kernel is hitting the initramfs shell. Using the default initrd, which has the nvme driver modules included, dump was captured successfully. Can someone from Canonical take a look at this and comment on why nvme modules are not included in kdump initrd despite it being the root disk.. Thanks Hari -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1778844/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
