@vicamo At this time the kernel is available in proposed. I can confirm that the kernel 5.8.0-44, in proposed, solves the problem in Groovy.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1894778 Title: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X vectors") currently in vanilla kernel tree for v5.11. [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn .... Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee00000 Data: 0000 When it fails, the address is fee00000. And with a patched kernel: $ lspci -vvnn .... Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: 0000 [Where problems could occur] An unpatched kernel will not be able to probe SATA controllers moved behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks attached on it completely unusable. With this change, kernel would then be able to probe them but may also suffer from issues that only occur under such configuration. However, the worst case is to move away sata disks from VMD bus as they are currently without this fix, so the risk here should be justified. ========== Previous SRU ========== [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Proposed kernel patch https://patchwork.kernel.org/patch/11758345/ [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn .... Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee00000 Data: 0000 When it fails, the address is fee00000. And with a patched kernel: $ lspci -vvnn .... Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: 0000 [Regression Potential] Low. For previous NVMe based platforms, this patch brings no effective change for NVMe devices because they will still stay in fast-interrupt list. ========== Original Bug Description ========== When booting with root filesystem on sata disks under Intel VMD mode, following errors printed in dmesg and no disk is found, nor booting into it: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 16.659284] ata1.00: qc timeout (cmd 0xec) [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 48.147294] ata1.00: qc timeout (cmd 0xec) [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) $ lspci ... 10000:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1894778/+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