From: Bjorn Helgaas <helgaas@kernel.org>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: bhelgaas@google.com, mahesh@linux.ibm.com, mani@kernel.org,
Jonathan.Cameron@huawei.com,
sathyanarayanan.kuppuswamy@linux.intel.com, oohall@gmail.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 3/3] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd
Date: Thu, 18 Sep 2025 15:33:15 -0500 [thread overview]
Message-ID: <20250918203315.GA1920702@bhelgaas> (raw)
In-Reply-To: <20250917063352.19429-4-xueshuai@linux.alibaba.com>
On Wed, Sep 17, 2025 at 02:33:52PM +0800, Shuai Xue wrote:
> 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: 0x80
When 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.
next prev parent reply other threads:[~2025-09-18 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 6:33 [PATCH v5 0/3] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2025-09-17 6:33 ` [PATCH v5 1/3] PCI/DPC: Clarify naming for error port in DPC Handling Shuai Xue
2025-09-17 6:33 ` [PATCH v5 2/3] PCI/DPC: Run recovery on device that detected the error Shuai Xue
2025-09-17 22:01 ` kernel test robot
2025-09-17 6:33 ` [PATCH v5 3/3] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2025-09-17 19:09 ` Kuppuswamy Sathyanarayanan
2025-09-18 2:45 ` Shuai Xue
2025-09-18 20:33 ` Bjorn Helgaas [this message]
2025-09-19 1:41 ` Shuai Xue
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=20250918203315.GA1920702@bhelgaas \
--to=helgaas@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mani@kernel.org \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=xueshuai@linux.alibaba.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