Re: [PATCH v5 3/3] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd
From: Shuai Xue <xueshuai@linux.alibaba.com>
Date: 2025-09-19 01:41:55
Also in:
linux-pci, lkml
From: Shuai Xue <xueshuai@linux.alibaba.com>
Date: 2025-09-19 01:41:55
Also in:
linux-pci, lkml
在 2025/9/19 04:33, Bjorn Helgaas 写道:
On Wed, Sep 17, 2025 at 02:33:52PM +0800, Shuai Xue wrote:quoted
The AER driver has historically avoided reading the configuration space of an endpoint or RCiEP that reported a fatal error, considering the link to that device unreliable. Consequently, when a fatal error occurs, the AER and DPC drivers do not report specific error types, resulting in logs like: pcieport 0015:00:00.0: EDR: EDR event received pcieport 0015:00:00.0: EDR: Reported EDR dev: 0015:00:00.0 pcieport 0015:00:00.0: DPC: containment event, status:0x200d, ERR_FATAL received from 0015:01:00.0 pcieport 0015:00:00.0: AER: broadcast error_detected message pcieport 0015:00:00.0: AER: broadcast mmio_enabled message pcieport 0015:00:00.0: AER: broadcast resume message pcieport 0015:00:00.0: pciehp: Slot(21): Link Down/Up ignored pcieport 0015:00:00.0: AER: device recovery successful pcieport 0015:00:00.0: EDR: DPC port successfully recovered pcieport 0015:00:00.0: EDR: Status for 0015:00:00.0: 0x80When you update this series, can you indent these messages with two spaces instead of a tab? That will preserve a little space and also preserve the formatting when "git log" adds its own indentation.
Sure, will align with space. Thanks. Shuai