From: Bjorn Helgaas <helgaas@kernel.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Grant Grundler <grundler@chromium.org>,
bhelgaas@google.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
mahesh@linux.ibm.com, oohall@gmail.com,
rajat.khandelwal@linux.intel.com, rajatja@chromium.org
Subject: Re: [PATCHv3 pci-next 1/2] PCI/AER: correctable error message as KERN_INFO
Date: Mon, 18 Sep 2023 14:39:13 -0500 [thread overview]
Message-ID: <20230918193913.GA203601@bhelgaas> (raw)
In-Reply-To: <3c3f9a2ee7f9effe7cf9d1077652e85de0eae66c.camel@xry111.site>
On Mon, Sep 18, 2023 at 07:42:30PM +0800, Xi Ruoyao wrote:
> ...
> My workstation suffers from too much correctable AER reporting as well
> (related to Intel's errata "RPL013: Incorrectly Formed PCIe Packets May
> Generate Correctable Errors" and/or the motherboard design, I guess).
We should rate-limit correctable error reporting so it's not
overwhelming.
At the same time, I'm *also* interested in the cause of these errors,
in case there's a Linux defect or a hardware erratum that we can work
around. Do you have a bug report with any more details, e.g., a dmesg
log and "sudo lspci -vv" output?
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: rajatja@chromium.org, rajat.khandelwal@linux.intel.com,
Grant Grundler <grundler@chromium.org>,
linux-pci@vger.kernel.org, mahesh@linux.ibm.com,
linux-kernel@vger.kernel.org, oohall@gmail.com,
bhelgaas@google.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCHv3 pci-next 1/2] PCI/AER: correctable error message as KERN_INFO
Date: Mon, 18 Sep 2023 14:39:13 -0500 [thread overview]
Message-ID: <20230918193913.GA203601@bhelgaas> (raw)
In-Reply-To: <3c3f9a2ee7f9effe7cf9d1077652e85de0eae66c.camel@xry111.site>
On Mon, Sep 18, 2023 at 07:42:30PM +0800, Xi Ruoyao wrote:
> ...
> My workstation suffers from too much correctable AER reporting as well
> (related to Intel's errata "RPL013: Incorrectly Formed PCIe Packets May
> Generate Correctable Errors" and/or the motherboard design, I guess).
We should rate-limit correctable error reporting so it's not
overwhelming.
At the same time, I'm *also* interested in the cause of these errors,
in case there's a Linux defect or a hardware erratum that we can work
around. Do you have a bug report with any more details, e.g., a dmesg
log and "sudo lspci -vv" output?
Bjorn
next prev parent reply other threads:[~2023-09-18 19:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 3:54 [PATCHv3 pci-next 1/2] PCI/AER: correctable error message as KERN_INFO Grant Grundler
2023-06-06 3:54 ` Grant Grundler
2023-06-06 3:54 ` [PATCHv3 pci-next 2/2] PCI/AER: Rate limit the reporting of the correctable errors Grant Grundler
2023-06-06 3:54 ` Grant Grundler
2023-06-06 7:21 ` kernel test robot
2023-06-06 7:21 ` kernel test robot
2023-06-06 9:49 ` kernel test robot
2023-06-06 9:49 ` kernel test robot
2023-08-13 0:44 ` [PATCHv3 pci-next 1/2] PCI/AER: correctable error message as KERN_INFO David Heidelberg
2023-08-13 0:44 ` David Heidelberg
2023-08-14 15:40 ` Grant Grundler
2023-08-14 15:40 ` Grant Grundler
2023-09-18 11:42 ` Xi Ruoyao
2023-09-18 11:42 ` Xi Ruoyao
2023-09-18 18:33 ` Grant Grundler
2023-09-18 18:33 ` Grant Grundler
2023-09-18 19:39 ` Bjorn Helgaas [this message]
2023-09-18 19:39 ` Bjorn Helgaas
2024-03-24 17:19 ` Xi Ruoyao
2024-03-24 17:19 ` Xi Ruoyao
2024-03-25 8:45 ` Ethan Zhao
2024-03-25 8:45 ` Ethan Zhao
2024-03-25 10:15 ` Xi Ruoyao
2024-03-25 10:15 ` Xi Ruoyao
2024-03-25 21:40 ` Xi Ruoyao
2024-03-25 21:40 ` Xi Ruoyao
2024-03-26 1:39 ` Ethan Zhao
2024-03-26 1:39 ` Ethan Zhao
2024-03-26 21:17 ` Bjorn Helgaas
2024-03-26 21:17 ` Bjorn Helgaas
2024-03-27 3:49 ` Ethan Zhao
2024-03-27 3:49 ` Ethan Zhao
2024-04-02 0:27 ` Xi Ruoyao
2024-04-02 0:27 ` Xi Ruoyao
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=20230918193913.GA203601@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=grundler@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rajat.khandelwal@linux.intel.com \
--cc=rajatja@chromium.org \
--cc=xry111@xry111.site \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.