From: Bjorn Helgaas <helgaas@kernel.org>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver OHalloran <oohall@gmail.com>,
Jon Pan-Doh <pandoh@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Sizhe Liu <liusizhe5@huawei.com>
Subject: Re: [PATCH v1] PCI/DPC: Fix AER error logging for DPC/EDR triggered events
Date: Wed, 18 Mar 2026 12:22:03 -0500 [thread overview]
Message-ID: <20260318172203.GA51847@bhelgaas> (raw)
In-Reply-To: <20260318170449.2733581-1-sathyanarayanan.kuppuswamy@linux.intel.com>
[+cc Sizhe]
On Wed, Mar 18, 2026 at 10:04:49AM -0700, Kuppuswamy Sathyanarayanan wrote:
> aer_print_error() skips printing if ratelimit_print[i] is not set.
> In the native AER path, ratelimit_print is initialized by
> add_error_device() during source device discovery, and is set to 1
> for fatal errors to bypass rate limiting since fatal errors should
> always be logged.
>
> The DPC/EDR path uses the DPC-capable port as the error source and
> reads its AER uncorrectable error status registers directly in
> dpc_get_aer_uncorrect_severity(). Since it does not go through
> add_error_device(), ratelimit_print[0] is left uninitialized and zero.
> As a result, aer_print_error() silently drops all AER error messages
> for DPC/EDR triggered events.
>
> Set ratelimit_print[0] to 1 to bypass rate limiting and always print
> AER logs for fatal errors.
>
> Fixes: a57f2bfb4a58 ("PCI/AER: Ratelimit correctable and non-fatal error logging")
> Co-developed-by: Goudar Manjunath Ramanagouda <manjunath.ramanagouda.goudar@intel.com>
> Signed-off-by: Goudar Manjunath Ramanagouda <manjunath.ramanagouda.goudar@intel.com>
> Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
I think this does the same as
https://git.kernel.org/cgit/linux/kernel/git/pci/pci.git/commit/?id=d4d1ecff2c2d
which is already queued for v7.1.
> ---
> drivers/pci/pcie/dpc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pci/pcie/dpc.c b/drivers/pci/pcie/dpc.c
> index fc18349614d7..7605ddd9f0ba 100644
> --- a/drivers/pci/pcie/dpc.c
> +++ b/drivers/pci/pcie/dpc.c
> @@ -256,6 +256,7 @@ static int dpc_get_aer_uncorrect_severity(struct pci_dev *dev,
>
> info->dev[0] = dev;
> info->error_dev_num = 1;
> + info->ratelimit_print[0] = 1;
>
> return 1;
> }
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-03-18 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 17:04 [PATCH v1] PCI/DPC: Fix AER error logging for DPC/EDR triggered events Kuppuswamy Sathyanarayanan
2026-03-18 17:22 ` Bjorn Helgaas [this message]
2026-03-18 17:48 ` Kuppuswamy Sathyanarayanan
2026-03-30 22:20 ` Bjorn Helgaas
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=20260318172203.GA51847@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liusizhe5@huawei.com \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=pandoh@google.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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