Ubuntu
linux package

  1. Bug #1651602
  2. Comment #2

Comment 2 for bug 1651602

Revision history for this message
Joshua Powers (powersj) wrote : Re: [2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails

Saw a similar failure in Curtin's vmtests [1]. Here is output from the Xenial boot log:

[ 1.370713] nvme nvme0: Failed to get enough MSI/MSIX interrupts
[ 1.371798] nvme 0000:00:07.0: Removing after probe failure
[ 1.380426] FDC 0 is a S82078B
[ 1.398396] nvme nvme1: Failed to get enough MSI/MSIX interrupts
[ 1.399396] nvme 0000:00:08.0: Removing after probe failure

Looks like a kernel regression at this point. This failure was on Linux version 4.4.0-57-generic. The last test to pass was on Linux version 4.4.0-53-generic. From [2] it looks like there was an attempt to fix this, by allowing the kernel to fall-back to legacy interrupts in the events that MSI-X and even MSI interrupts failed to be allocated.

[1] https://jenkins.ubuntu.com/server/job/curtin-vmtest/649/artifact/output/XenialTestNvme/logs/
[2] http://lists.infradead.org/pipermail/linux-nvme/2016-May/004653.html