Bug 209149
Summary: | "iommu/vt-d: Enable PCI ACS for platform opt in hint" makes NVMe config space not accessible after S3 | ||
---|---|---|---|
Product: | Drivers | Reporter: | Kai-Heng Feng (kai.heng.feng) |
Component: | PCI | Assignee: | drivers_pci (drivers_pci) |
Status: | NEW --- | ||
Severity: | normal | CC: | baolu.lu |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | mainline | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg with dynamic debug enabled
lspci -vvnn lspci -t workaround patch dmesg with the quirk patch applied dmesg lspci -tv, Intel NVMe Proposed patch Print AER status dmesg with AER status printed |
Description
Kai-Heng Feng
2020-09-04 14:31:20 UTC
Created attachment 292327 [details]
dmesg with dynamic debug enabled
Created attachment 292329 [details]
lspci -vvnn
Created attachment 292331 [details]
lspci -t
Created attachment 292333 [details]
workaround patch
Once using a quirk for the root port, the issue is gone.
Created attachment 292335 [details]
dmesg with the quirk patch applied
So I wonder if ACS quirk is also required for Comet Lake? Created attachment 292565 [details]
dmesg
Same issue on Intel NVMe, after ACS quirk applied.
Created attachment 292567 [details]
lspci -tv, Intel NVMe
Created attachment 292569 [details]
Proposed patch
Unconditionally disable ACS redir for Intel bridges can workaround the issue.
#9 is just a placebo. The issue is still reproducible with ACS redir forcibly disabled. Created attachment 295077 [details]
Print AER status
Created attachment 295079 [details]
dmesg with AER status printed
|