------- Comment From [email protected] 2018-07-23 07:30 EDT------- Indira, I think Cascardo is looking for /tmp/initrd.img-`uname -r` file whne MODULES=dep is used. Also, sosreport?
(In reply to comment #26) > Created attachment 128855 [details] > woo_kdump_nvmedisk_console logs btw, looks like PHB initialization is failing. So, whether nvme driver is present or not in the initrd is secondary here, the device initialization itself could be at fault. What is the f/w level. Is it latest? Thanks Hari ------- Comment From [email protected] 2018-07-23 07:35 EDT------- (In reply to comment #28) > Indira, I think Cascardo is looking for /tmp/initrd.img-`uname -r` file > whne MODULES=dep is used. Also, sosreport? > > (In reply to comment #26) > > Created attachment 128855 [details] > > woo_kdump_nvmedisk_console logs > > btw, looks like PHB initialization is failing. So, whether nvme driver > is present or not in the initrd is secondary here, the device initialization > itself could be at fault. What is the f/w level. Is it latest? also, the initial console log is different from this.. Was the f/w on the system updated as well.. 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
