From: Bjorn Helgaas <helgaas@kernel.org>
To: Harald Dunkel <harald.dunkel@aixigo.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: AER: Corrected error message received from 0000:00:06.0
Date: Thu, 29 Feb 2024 14:26:52 -0600 [thread overview]
Message-ID: <20240229202652.GA361290@bhelgaas> (raw)
In-Reply-To: <67576689-23ff-4e32-a93c-5bebbfc647b6@aixigo.com>
On Thu, Feb 29, 2024 at 03:52:36PM +0100, Harald Dunkel wrote:
> Hi folks,
>
> dmesg shows these messages I am unfamiliar with:
>
> [Thu Feb 29 13:47:22 2024] pcieport 0000:00:06.0: AER: Corrected error message received from 0000:00:06.0
> [Thu Feb 29 13:47:22 2024] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
> [Thu Feb 29 13:47:22 2024] pcieport 0000:00:06.0: device [8086:a74d] error status/mask=00000001/00002000
> [Thu Feb 29 13:47:22 2024] pcieport 0000:00:06.0: [ 0] RxErr (First)
> [Thu Feb 29 14:46:56 2024] pcieport 0000:00:06.0: AER: Corrected error message received from 0000:00:06.0
> [Thu Feb 29 14:46:56 2024] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
> [Thu Feb 29 14:46:56 2024] pcieport 0000:00:06.0: device [8086:a74d] error status/mask=00000001/00002000
> [Thu Feb 29 14:46:56 2024] pcieport 0000:00:06.0: [ 0] RxErr (First)
> [Thu Feb 29 15:04:33 2024] pcieport 0000:00:06.0: AER: Corrected error message received from 0000:00:06.0
> [Thu Feb 29 15:04:33 2024] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
> [Thu Feb 29 15:04:33 2024] pcieport 0000:00:06.0: device [8086:a74d] error status/mask=00000001/00002000
> [Thu Feb 29 15:04:33 2024] pcieport 0000:00:06.0: [ 0] RxErr (First)
> [Thu Feb 29 15:27:56 2024] pcieport 0000:00:06.0: AER: Corrected error message received from 0000:00:06.0
> [Thu Feb 29 15:27:56 2024] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
> [Thu Feb 29 15:27:56 2024] pcieport 0000:00:06.0: device [8086:a74d] error status/mask=00000001/00002000
> [Thu Feb 29 15:27:56 2024] pcieport 0000:00:06.0: [ 0] RxErr (First)
>
> Is this something to worry about?
Probably not, since these errors are normally corrected by hardware
without software intervention. But we do need to improve the way we
log these, so if you could open a report at
https://bugzilla.kernel.org in the Drivers/PCI component, and attach
a complete dmesg log and output of "sudo lspci -vvxxxx" to the
bugzilla, I'll take a look and make sure.
Bjorn
next prev parent reply other threads:[~2024-02-29 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 14:52 AER: Corrected error message received from 0000:00:06.0 Harald Dunkel
2024-02-29 20:26 ` Bjorn Helgaas [this message]
2024-03-04 7:19 ` Harald Dunkel
2024-03-12 7:35 ` Harald Dunkel
2024-03-12 17:37 ` 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=20240229202652.GA361290@bhelgaas \
--to=helgaas@kernel.org \
--cc=harald.dunkel@aixigo.com \
--cc=linux-pci@vger.kernel.org \
/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