------- Comment From [email protected] 2016-11-14 11:17 EDT------- dougmill-ibm commented 6 days ago It appears that one of NVMe drives failed to function correctly during boot/probe. The 'lspci' output does not show that drive, which means it was taken after the failure but before recovery (reboot). It means we don't have full info on that drive.
>From a high-level look at the code, the vfree error seems to be for freeing the PCI BAR. The code path through the initialization might allow for a failure before/during allocation of BAR and not account for that during device removal. The stack trace is not much help because the "remove dead controller" routine is invoked as "work" on a kthread, and so we do not have the stack trace of the thread that actually encountered the original failure (I/O timeout). So, there are two problems shown here. One is the vfree WARNING which indicates that the error paths are not quite right. The other is why the NVMe drive failed to function correctly - which is the primary issue for this test case. NOTE: the vfree message is only a WARNING and should not cause any sort of permanent problem with the running kernel. ------- Comment From [email protected] 2016-11-14 16:42 EDT------- Debug continues. ** Tags added: architecture-ppc64le bugnameltc-148618 severity-critical targetmilestone-inin1604 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639920 Title: NVMe detection failed during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639920/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
