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
Verified with the 4.8.0-36-generic kernel on an AWS i3 instance, all the
NVMe drives initialized successfully. Checked the git log and verified
the initial commit had been fully reverted (see comment 7).
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
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)
** Changed in: linux (Ubuntu Zesty)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648449
Title:
NVMe drives in Amazon AWS instance fail to initialize
To
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648449
Title:
NVMe drives in Amazon AWS instance fail to initialize
To
This bug was fixed in the package linux - 4.4.0-57.78
---
linux (4.4.0-57.78) xenial; urgency=low
* Release Tracking Bug
- LP: #1648867
* Miscellaneous Ubuntu changes
- SAUCE: Do not build the xr-usb-serial driver for s390
linux (4.4.0-56.77) xenial; urgency=low
*
I verified kernel linux-image-generic 4.4.0.57.60 (uname
4.4.0-57-generic #78-Ubuntu) does fix this.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648449
Title:
NVMe drives in Amazon AWS instance fail to initialize
To
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Assignee: Dan Streetman (ddstreet)
Status: Incomplete
This is a problem only in xenial and later (yakkety, zesty, upstream).
The issue is the driver configures an MSIX interrupt to use with the
admin queue during initialization, and then when setting up its I/O
queues, it releases the MSIX interrupt for the admin queue, and then
immediately
12 matches
Mail list logo
