This bug was fixed in the package linux - 5.4.0-25.29

---------------
linux (5.4.0-25.29) focal; urgency=medium

  * focal/linux: 5.4.0-25.29 -proposed tracker (LP: #1873459)

  * [TGL] VMD support in TGL (LP: #1855954)
    - PCI: vmd: Add bus 224-255 restriction decode
    - PCI: vmd: Add device id for VMD device 8086:9A0B

  * Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake
    (LP: #1871812)
    - ahci: Add Intel Comet Lake PCH RAID PCI ID

 -- Seth Forshee <seth.fors...@canonical.com>  Fri, 17 Apr 2020 08:41:16
-0500

** Changed in: linux (Ubuntu)
       Status: In Progress => 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/1855954

Title:
  [TGL] VMD support in TGL

Status in HWE Next:
  New
Status in intel:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  On platforms with VMD support, block devices won't be scanned if VMD
  controller is not previously probed.

  [Fix]
  Two commits from v5.5-rc1 to be backported.

  [Test Case]
  On platforms with VMD support, boot with prebuilt kernel and check if
  Intel Volume Management Device appears among PCI devices:

    $ lspci | grep 'Volume Management Device'
    0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management
  Device NVMe RAID Controller

  [Regression Potential]
  Low. This only enables VMD controller on platforms with such device.

  ========== original description ==========

  Description:
  VMD support in Tiger Lake Platform

  Target Kernel: TBD
  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855954/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to