From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: bjorn@helgaas.com, "Naveen Naidu" <naveennaidu479@gmail.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Keith Busch" <kbusch@kernel.org>, "Jens Axboe" <axboe@fb.com>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>
Subject: Re: [Bug 215027] New: "PCIe Bus Error: severity=Corrected, type=Physical Layer" flood on Intel VMD + Samsung NVMe combination
Date: Mon, 15 Nov 2021 15:20:50 -0600 [thread overview]
Message-ID: <20211115212050.GA1588607@bhelgaas> (raw)
In-Reply-To: <bug-215027-41252@https.bugzilla.kernel.org/>
[+cc Naveen, NVMe, VMD folks]
On Mon, Nov 15, 2021 at 07:17:01AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215027
>
> Bug ID: 215027
> Summary: "PCIe Bus Error: severity=Corrected, type=Physical
> Layer" flood on Intel VMD + Samsung NVMe combination
> Product: Drivers
> Version: 2.5
> Kernel Version: mainline, linux-next
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: PCI
> Assignee: drivers_pci@kernel-bugs.osdl.org
> Reporter: kai.heng.feng@canonical.com
> Regression: No
>
> The following tests (and any combination of them) don't help:
> - Change NVMe LTR value to 0 or any other number
> - Disable NVMe APST
> - Disable PCIe ASPM
> - Any version of kernel, including linux-next
> - "Fix long standing AER Error Handling Issues" patch series [1]
>
> [1]
> https://lore.kernel.org/linux-pci/cover.1635179600.git.naveennaidu479@gmail.com/
Thanks a lot for the report, Kai-Heng. It's on v5.15, which is good,
and not marked as a regression. Samples from dmesg:
[ 0.408995] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[ 0.410076] acpi PNP0A08:00: _OSC: platform does not support [AER]
[ 0.412207] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME PCIeCapability LTR]
[ 1.367220] vmd 0000:00:0e.0: PCI host bridge to bus 10000:e0
[ 1.490742] vmd 0000:00:0e.0: Bound to PCI domain 10000
[ 1.569083] nvme nvme0: pci function 10000:e1:00.0
[ 1.571421] pcieport 10000:e0:06.0: can't derive routing for PCI INT A
[ 1.573997] nvme 10000:e1:00.0: PCI INT A: not connected
[ 1.579028] pcieport 10000:e0:06.0: AER: Corrected error received: 10000:e1:00.0
[ 1.584839] nvme 10000:e1:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver)
[ 1.587454] nvme 10000:e1:00.0: device [144d:a80a] error status/mask=00000001/0000e000
[ 1.589502] nvme 10000:e1:00.0: [ 0] RxErr
[ 1.589813] nvme nvme0: Shutdown timeout set to 10 seconds
[ 1.591509] pcieport 10000:e0:06.0: AER: Corrected error received: 10000:e1:00.0
[ 1.595252] pcieport 10000:e0:06.0: AER: can't find device of IDe100
[ 1.597213] pcieport 10000:e0:06.0: AER: Corrected error received: 10000:e1:00.0
...
next parent reply other threads:[~2021-11-15 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215027-41252@https.bugzilla.kernel.org/>
2021-11-15 21:20 ` Bjorn Helgaas [this message]
2021-11-15 21:52 ` [Bug 215027] New: "PCIe Bus Error: severity=Corrected, type=Physical Layer" flood on Intel VMD + Samsung NVMe combination Keith Busch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211115212050.GA1588607@bhelgaas \
--to=helgaas@kernel.org \
--cc=axboe@fb.com \
--cc=bjorn@helgaas.com \
--cc=hch@lst.de \
--cc=jonathan.derrick@linux.dev \
--cc=kbusch@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=naveennaidu479@gmail.com \
--cc=nirmal.patel@linux.intel.com \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox