It appears these workaround patches introduced NVMe initialization
problems on some non-Xen systems, see bug 1626894. I sent patches to
revert this for xenial and yakkety. Instead, this problem should be
fixed by a patch to Xen kernel code, in bug 1656831.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Zesty)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1648449
Title:
NVMe drives in Amazon AWS instance fail to initialize
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Invalid
Bug description:
[Impact]
On an Amazon AWS instance that has NVMe drives, the NVMe drives fail
to initialize, and so aren't usable by the system. If one of the NVMe
drives contains the root filesystem, the instance won't boot.
[Test Case]
Boot an AWS instance with a NVMe drive. It will fail to initialize
the NVMe drive(s), and errors will appear in the system log (if the
system boots at all). With a patched kernel, all NVMe drives are
initialized and enumerated and work properly.
[Regression Potential]
Patching the NVMe driver may cause problems on other systems using
NVMe drives.
[Other Info]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648449/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
