This bug was fixed in the package linux - 4.8.0-37.39
---------------
linux (4.8.0-37.39) yakkety; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1659381
* Mouse cursor invisible or does not move (LP: #1646574)
- drm/nouveau/disp/nv50-: split chid into chid.ctrl and chid.user
- drm/nouveau/disp/nv50-: specify ctrl/user separately when constructing
classes
- drm/nouveau/disp/gp102: fix cursor/overlay immediate channel indices
-- Benjamin M Romer <[email protected]> Wed, 25 Jan 2017
16:12:02 -0200
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
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 Released
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 : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
