Re: [PATCH v2] PCI/DPC: Increase recovery timeout to 60 seconds
From: Ziyou Wang (Lenovo)
Date: Thu Nov 19 2026 - 22:22:46 EST
Hi Lukas,
The ACS Violation in that log is not organic, it is injected on purpose.
The platform is AMD and we use AMD's RAS Error Injection Test tool to
inject an "ACS fatal" error at the Root Port. The test steps are:
1. Shorten the machine check polling interval:
echo 1 > /sys/devices/system/machinecheck/machinecheck0/check_interval
2. List the PCIe slot info to find the socket/die/NBIO, PCIe core and
port that the NVMe drive is attached to:
./cmdline_amdraserrorinjectiontest --listpcieslotinfo
3. Start I/O traffic on the NVMe drive:
dd if=/dev/nvmeXnY of=/dev/null bs=64k status=progress conv=noerror,sync
4. Inject the ACS fatal error at that Root Port:
./cmdline_amdraserrorinjectiontest --pcieerror \
--sockdienbio <socket:die:nbio> --errortype 4 \
--pciecore <core> --pcieport <port> --enablestatusregisterpolling 1
This raises ACSViol in the Root Port's AER Uncorrectable Error Status.
The BIOS has AER and ACS enabled and AER reporting is set to firmware
first, so firmware signals the EDR event and DPC containment follows.
The TLP you decoded is a regular in-flight DMA write from the NVMe drive
that happened to be captured in the AER Header Log (there was read
traffic on the drive at injection time). Its Requester ID is valid and
Source Validation is enabled, so nothing in it violates any ACS rule.
The ACSViol comes from the injector, not from real ACS logic.
The ACS settings on the Root Port (same platform, 1022:1108):
ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans+
ACSCtl: SrcValid+ TransBlk- ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
The goal of the test was to produce a DPC containment event on an NVMe
device that needs about 4 seconds to become config-ready again, in order
to exercise the recovery path.
Thanks,
Ziyou