| 2017-01-13 18:37:43 |
Dan Streetman |
bug |
|
|
added bug |
| 2017-01-13 18:37:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-01-13 18:37:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Trusty |
|
| 2017-01-13 18:37:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-01-13 18:37:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-01-13 18:38:08 |
Dan Streetman |
linux (Ubuntu): assignee |
|
Dan Streetman (ddstreet) |
|
| 2017-01-13 18:38:18 |
Dan Streetman |
linux (Ubuntu): status |
New |
In Progress |
|
| 2017-01-13 18:38:24 |
Dan Streetman |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2017-01-16 12:05:10 |
Luis Henriques |
bug task added |
|
linux (Ubuntu Trusty) |
|
| 2017-01-16 12:05:21 |
Luis Henriques |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2017-01-16 12:05:30 |
Luis Henriques |
bug task added |
|
linux (Ubuntu Zesty) |
|
| 2017-01-16 12:05:36 |
Luis Henriques |
bug task added |
|
linux (Ubuntu Yakkety) |
|
| 2017-01-16 15:41:29 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2017-01-17 11:45:22 |
Luis Henriques |
linux (Ubuntu Yakkety): status |
New |
Fix Committed |
|
| 2017-01-18 15:24:23 |
Dan Streetman |
description |
[Impact]
This bug fixes the root problem reported in bug 1648449, so its description can be mostly reused here:
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 multiple NVMe drives. All except the first will fail to initialize, 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 Xen MSI setup function may cause problems with other PCI devices using MSI/MSIX interrupts on a Xen guest.
[Other Info]
The patch from bug 1648449 was only a workaround, that changed the NVMe driver to not trigger this Xen bug. However, there have been reports of that patch causing non-Xen systems with NVMe drives to stop working, in bug 1626894. So, the best thing to do is revert the workaround patch (and its regression fix patch from bug 1651602) back to the original NVMe drive code, and apply the real Xen patch to fix the problem. That should restore functionality for non-Xen systems, and should allow Xen systems with multiple NVMe controllers to work. |
[Impact]
This bug fixes the root problem reported in bug 1648449, so its description can be mostly reused here:
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 multiple NVMe drives. All except the first will fail to initialize, 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 Xen MSI setup function may cause problems with other PCI devices using MSI/MSIX interrupts on a Xen guest.
Note this patch restores correct behavior for guests running under Xen 4.5 or later hypervisors - specifically Xen hypervisors with qemu 2.1.0 or later. For Xen hypervisors with qemu 2.0.0 or earlier, this patch causes a regression. With an Ubuntu hypervisor, Vivid or later qemu is patched, as well as UCA Kilo or later qemu. Trusty qemu or UCA Icehouse qemu are not patched - see bug 1657489.
[Other Info]
The patch from bug 1648449 was only a workaround, that changed the NVMe driver to not trigger this Xen bug. However, there have been reports of that patch causing non-Xen systems with NVMe drives to stop working, in bug 1626894. So, the best thing to do is revert the workaround patch (and its regression fix patch from bug 1651602) back to the original NVMe drive code, and apply the real Xen patch to fix the problem. That should restore functionality for non-Xen systems, and should allow Xen systems with multiple NVMe controllers to work.
Upstream discussion:
https://lists.xen.org/archives/html/xen-devel/2017-01/msg00447.html
Related: bug 1657489 ("qemu-xen: free all the pirqs for msi/msix when driver unload") |
|
| 2017-01-19 12:43:39 |
John Donnelly |
tags |
|
verification-needed-yakkety |
|
| 2017-01-19 13:16:44 |
John Donnelly |
tags |
verification-needed-yakkety |
verification-needed-xenial verification-needed-yakkety |
|
| 2017-01-19 20:53:12 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2017-01-20 00:03:33 |
Dan Streetman |
tags |
verification-needed-xenial verification-needed-yakkety |
verification-done-xenial verification-needed-yakkety |
|
| 2017-01-20 00:13:51 |
Dan Streetman |
tags |
verification-done-xenial verification-needed-yakkety |
verification-done-xenial verification-done-yakkety |
|
| 2017-01-20 12:57:05 |
Luis Henriques |
linux (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2017-02-02 16:59:00 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-02-02 16:59:59 |
Launchpad Janitor |
linux (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-02-09 22:01:41 |
Thadeu Lima de Souza Cascardo |
tags |
verification-done-xenial verification-done-yakkety |
verification-done-xenial verification-done-yakkety verification-needed-trusty |
|
| 2017-02-10 21:33:09 |
Dan Streetman |
tags |
verification-done-xenial verification-done-yakkety verification-needed-trusty |
verification-done-trusty verification-done-xenial verification-done-yakkety |
|
| 2017-02-20 07:36:41 |
Launchpad Janitor |
linux (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2017-02-20 07:36:41 |
Launchpad Janitor |
cve linked |
|
2016-7910 |
|
| 2017-02-20 07:36:41 |
Launchpad Janitor |
cve linked |
|
2016-7911 |
|
| 2017-10-13 16:03:22 |
Dan Streetman |
linux (Ubuntu Zesty): status |
In Progress |
Fix Released |
|
| 2018-05-25 14:44:35 |
Dan Streetman |
linux (Ubuntu): status |
In Progress |
Fix Released |
|
