| 2020-09-08 03:32:16 |
You-Sheng Yang |
bug |
|
|
added bug |
| 2020-09-08 03:33:18 |
You-Sheng Yang |
bug |
|
|
added subscriber Canonical Hardware Enablement |
| 2020-09-08 03:33:22 |
You-Sheng Yang |
tags |
|
oem-priority originate-from-1891445 somerville |
|
| 2020-09-08 03:33:28 |
You-Sheng Yang |
tags |
oem-priority originate-from-1891445 somerville |
oem-priority originate-from-1891445 originate-from-1892806 somerville |
|
| 2020-09-08 03:36:33 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.6 (Ubuntu) |
|
| 2020-09-08 03:36:50 |
You-Sheng Yang |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-09-08 03:36:50 |
You-Sheng Yang |
bug task added |
|
linux (Ubuntu Groovy) |
|
| 2020-09-08 03:36:50 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.6 (Ubuntu Groovy) |
|
| 2020-09-08 03:36:50 |
You-Sheng Yang |
nominated for series |
|
Ubuntu Focal |
|
| 2020-09-08 03:36:50 |
You-Sheng Yang |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2020-09-08 03:36:50 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.6 (Ubuntu Focal) |
|
| 2020-09-08 03:37:01 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Groovy): status |
New |
Confirmed |
|
| 2020-09-08 03:37:08 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Focal): status |
New |
Confirmed |
|
| 2020-09-08 03:37:16 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Groovy): status |
Confirmed |
Invalid |
|
| 2020-09-08 03:37:19 |
You-Sheng Yang |
linux (Ubuntu Groovy): status |
New |
Confirmed |
|
| 2020-09-08 03:37:22 |
You-Sheng Yang |
linux (Ubuntu Focal): status |
New |
Confirmed |
|
| 2020-09-08 03:37:32 |
You-Sheng Yang |
linux (Ubuntu Focal): importance |
Undecided |
High |
|
| 2020-09-08 03:37:36 |
You-Sheng Yang |
linux (Ubuntu Groovy): importance |
Undecided |
High |
|
| 2020-09-08 03:37:38 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Focal): importance |
Undecided |
High |
|
| 2020-09-08 06:46:25 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2020-09-08 06:46:45 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Focal): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2020-09-08 06:47:17 |
You-Sheng Yang |
linux (Ubuntu Groovy): status |
Confirmed |
In Progress |
|
| 2020-09-08 06:47:20 |
You-Sheng Yang |
linux (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2020-09-08 06:47:24 |
You-Sheng Yang |
linux (Ubuntu Focal): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2020-09-08 06:47:28 |
You-Sheng Yang |
linux (Ubuntu Groovy): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2020-09-08 08:04:36 |
You-Sheng Yang |
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) |
[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) |
|
| 2020-09-08 08:39:29 |
Timo Aaltonen |
linux-oem-5.6 (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-09-11 15:16:45 |
Ubuntu Kernel Bot |
tags |
oem-priority originate-from-1891445 originate-from-1892806 somerville |
oem-priority originate-from-1891445 originate-from-1892806 somerville verification-needed-focal |
|
| 2020-09-15 06:01:32 |
You-Sheng Yang |
tags |
oem-priority originate-from-1891445 originate-from-1892806 somerville verification-needed-focal |
oem-priority originate-from-1891445 originate-from-1892806 somerville verification-done-focal |
|
| 2020-09-22 09:26:42 |
Launchpad Janitor |
linux-oem-5.6 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-09-22 09:26:42 |
Launchpad Janitor |
cve linked |
|
2020-12888 |
|
| 2020-12-21 10:08:02 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.10 (Ubuntu) |
|
| 2020-12-21 10:08:23 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Focal): status |
New |
Confirmed |
|
| 2020-12-21 10:08:36 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Groovy): status |
New |
Invalid |
|
| 2020-12-21 10:08:53 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu): status |
New |
Invalid |
|
| 2020-12-22 04:23:56 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Focal): importance |
Undecided |
High |
|
| 2020-12-22 04:23:56 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2020-12-22 04:23:56 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Focal): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2020-12-22 07:54:00 |
You-Sheng Yang |
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]
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) |
[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) |
|
| 2020-12-22 07:55:46 |
You-Sheng Yang |
linux (Ubuntu Focal): status |
In Progress |
Won't Fix |
|
| 2020-12-29 14:09:19 |
fabianbur |
bug |
|
|
added subscriber fabianbur |
| 2021-01-11 08:15:21 |
Timo Aaltonen |
linux-oem-5.10 (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-01-12 14:55:16 |
Timo Aaltonen |
linux (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2021-01-26 03:24:53 |
Kelsey Steele |
linux (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2021-01-27 10:16:46 |
Launchpad Janitor |
linux-oem-5.10 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-01-29 07:39:12 |
Ubuntu Kernel Bot |
tags |
oem-priority originate-from-1891445 originate-from-1892806 somerville verification-done-focal |
oem-priority originate-from-1891445 originate-from-1892806 somerville verification-done-focal verification-needed-groovy |
|
| 2021-01-30 21:09:50 |
fabianbur |
linux (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-01-30 21:24:12 |
fabianbur |
tags |
oem-priority originate-from-1891445 originate-from-1892806 somerville verification-done-focal verification-needed-groovy |
oem-priority originate-from-1891445 originate-from-1892806 somerville verification-done-focal verification-done-groovy |
|
| 2021-02-19 23:03:37 |
Launchpad Janitor |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2022-09-05 10:21:32 |
Timo Aaltonen |
hwe-next: status |
New |
Fix Released |
|
