Trusty NVMe boot fails on some systems

[Kamal Mostafa]

Trusty linux (3.13) fails to boot on some NVMe-based cloud instance types.

[Impact]

 * Ubuntu trusty images can't be used on some NVMe-based cloud instance types.

 * Mainline commit a522905 "NVMe: Always use MSI/MSI-x interrupts" fixes the issue; application of this to 3.13 requires a set of prerequisite patches, and a minor backport.

a522905 NVMe: Always use MSI/MSI-x interrupts
e32efbf NVMe: make setup work for devices that don't do INTx
be577fa nvme: Use pci_enable_msi_range() and pci_enable_msix_range()
42f6142 NVMe: per-cpu io queues
4f5099a NVMe: IOCTL path RCU protect queue access
5a92e70 NVMe: RCU protected access to io queues

[Test Case]

 * Verify that a trusty-based image can boot on the affected instance type.

[Regression Potential]

 * This change set affects all users of the NVMe driver, so regression potential is moderate to high. Additional soak testing may be warranted before merging this patch set.

 * The patched NVMe driver has been exercised by Dan Streetman, and given the thumbs-up.

[Kamal Mostafa (kamalmostafa)]

Taihsiang Ho (Canonical Cert) has performed the routine desktop certification test plan for SRU, and reports NO REGRESSIONS from the test kernel with this patch set:

------

Test release: 14.04.1

The base kernel: 3.13.0-133.182
The patch kernel: 3.13.0-133.182+nvmemsi

Test platforms:

Dell OptiPlex 7450 AIO (CID 201606-22472)
Sky Lake Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller [8086:1901]
Non-Volatile memory controller [0108]: Device [1c5c:1284]

Dell Computer Corporation Precision 5510 (Code name: Berlinetta P) (CID 201612-25281)
Sky Lake Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller [8086:1901]
Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd Device [144d:a802] (rev 01)

[Kleber Sacilotto de Souza (kleber-souza)]

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-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 3.13.0-135.184

---------------
linux (3.13.0-135.184) trusty; urgency=low

  * linux: 3.13.0-135.184 -proposed tracker (LP: #1724500)

  * Trusty NVMe boot fails on some systems (LP: #1720867)
    - NVMe: RCU protected access to io queues
    - NVMe: IOCTL path RCU protect queue access
    - powerpc/mm: fix ".__node_distance" undefined
    - NVMe: per-cpu io queues
    - nvme: Use pci_enable_msi_range() and pci_enable_msix_range()
    - NVMe: make setup work for devices that don't do INTx
    - NVMe: Always use MSI/MSI-x interrupts

linux (3.13.0-134.183) trusty; urgency=low

  * linux: 3.13.0-134.183 -proposed tracker (LP: #1722335)

  [ Thadeu Lima de Souza Cascardo ]
  * CVE-2017-10661
    - timerfd: Protect the might cancel mechanism proper

  * CVE-2017-10662
    - f2fs: sanity check segment count

  * CVE-2017-10663
    - f2fs: sanity check checkpoint segno and blkoff

  * CVE-2017-14340
    - xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present

  * CVE-2017-10911
    - xen-blkback: don't leak stack data via response ring

  * CVE-2017-11176
    - mqueue: fix a use-after-free in sys_mq_notify()

  * CVE-2016-8632
    - tipc: check minimum bearer MTU

 -- Thadeu Lima de Souza Cascardo <email address hidden> Wed, 18 Oct 2017 07:09:04 -0200