From: Lukas Wunner <lukas@wunner.de>
To: "Ziyou Wang (Lenovo)" <ziyou.dev@foxmail.com>
Cc: helgaas@kernel.org, bhelgaas@google.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] PCI/DPC: Increase recovery timeout to 60 seconds
Date: Thu, 19 Nov 2026 10:01:29 +0100 [thread overview]
Message-ID: <av666Q38S0q5HqYS@wunner.de> (raw)
In-Reply-To: <tencent_F14FD4212049828EDB98B55B6E0FE116CF07@qq.com>
On Thu, Nov 19, 2026 at 11:30:36AM +0800, Ziyou Wang (Lenovo) wrote:
> [121.693046] pcieport 0000:00:03.1: EDR: EDR event received
> [121.695743] pcieport 0000:00:03.1: DPC: containment event, status:0x1f01: unmasked uncorrectable error detected
> [121.695825] pcieport 0000:00:03.1: PCIe Bus Error: severity=Uncorrectable (Fatal)
> [121.695829] pcieport 0000:00:03.1: device [1022:1108] error status/mask=00200000/00000000
> [121.695831] pcieport 0000:00:03.1: [21] ACSViol | Receiver | Transaction Layer (First)
> [121.695834] pcieport 0000:00:03.1: AER: TLP Header: 0x60002080 0x010042ff 0x00000017 0x7e325c00
[...]
> [123.018691] nvme 0000:01:00.0: not ready 1023ms after DPC; waiting
I'm wondering why the ACS Violation Error is raised in the first place.
The TLP causing the DPC event is a Memory Write Request from the NVMe
drive to memory address 0x000000177e325c00. The Requester ID 0x100
seems to match the bus address 0000:01:00.0.
What are the ACS settings at the Root Port and why is it signaling an
ACS violation?
TLP decoded with tlp-tool (https://github.com/mmpg-x86/tlp-tool):
+----------+-------------+----------------------+
| TLP Type | MemWriteReq | 4DW with Data Header |
+----------+-------------+----------------------+
+------------+--------+--------+-------+
| Field Name | Offset | Length | Value |
| | (bits) | (bits) | |
+------------+--------+--------+-------+
| Fmt | 0 | 3 | 3 |
| Type | 3 | 5 | 0 |
| T9 | 8 | 1 | 0 |
| TC | 9 | 3 | 0 |
| T8 | 12 | 1 | 0 |
| Attr_b2 | 13 | 1 | 0 |
| LN | 14 | 1 | 0 |
| TH | 15 | 1 | 0 |
| Td | 16 | 1 | 0 |
| Ep | 17 | 1 | 0 |
| Attr | 18 | 2 | 2 |
| AT | 20 | 2 | 0 |
| Length | 22 | 10 | 128 |
+------------+--------+--------+-------+
+-----------------+----------------------+
| TLP: | 4DW with Data Header |
+-----------------+----------------------+
| Req ID | 0x100 |
| Tag | 0x42 |
| Last DW BE | 0xF |
| First DW BE | 0xF |
| Addr High (DW2) | 0x00000017 |
| Addr Low (DW3) | 0x7E325C00 |
+-----------------+----------------------+
Thanks,
Lukas
prev parent reply other threads:[~2026-11-19 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261106082612.1840817-1-ziyou.dev@foxmail.com>
2026-11-06 8:56 ` Ziyou Wang (Lenovo)
2026-11-06 15:21 ` Bjorn Helgaas
2026-11-19 3:30 ` Ziyou Wang (Lenovo)
2026-11-19 9:01 ` Lukas Wunner [this message]
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=av666Q38S0q5HqYS@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=ziyou.dev@foxmail.com \
/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
all inboxes | Powered by JetHome®