* AER: Corrected error message received from 0000:00:06.0
@ 2024-02-29 14:52 Harald Dunkel
2024-02-29 20:26 ` Bjorn Helgaas
0 siblings, 1 reply; 5+ messages in thread
From: Harald Dunkel @ 2024-02-29 14:52 UTC (permalink / raw)
To: linux-pci
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?
Regards
Harri
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: AER: Corrected error message received from 0000:00:06.0
2024-02-29 14:52 AER: Corrected error message received from 0000:00:06.0 Harald Dunkel
@ 2024-02-29 20:26 ` Bjorn Helgaas
2024-03-04 7:19 ` Harald Dunkel
0 siblings, 1 reply; 5+ messages in thread
From: Bjorn Helgaas @ 2024-02-29 20:26 UTC (permalink / raw)
To: Harald Dunkel; +Cc: linux-pci
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: AER: Corrected error message received from 0000:00:06.0
2024-02-29 20:26 ` Bjorn Helgaas
@ 2024-03-04 7:19 ` Harald Dunkel
2024-03-12 7:35 ` Harald Dunkel
0 siblings, 1 reply; 5+ messages in thread
From: Harald Dunkel @ 2024-03-04 7:19 UTC (permalink / raw)
To: Bjorn Helgaas; +Cc: linux-pci
On 2024-02-29 21:26:52, Bjorn Helgaas wrote:
>
> 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.
>
This is https://bugzilla.kernel.org/show_bug.cgi?id=218556
Thank you very much
Harri
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: AER: Corrected error message received from 0000:00:06.0
2024-03-04 7:19 ` Harald Dunkel
@ 2024-03-12 7:35 ` Harald Dunkel
2024-03-12 17:37 ` Bjorn Helgaas
0 siblings, 1 reply; 5+ messages in thread
From: Harald Dunkel @ 2024-03-12 7:35 UTC (permalink / raw)
To: Bjorn Helgaas; +Cc: linux-pci
For the records: Booting with pcie_aspm=off seems to help.
Regards
Harri
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: AER: Corrected error message received from 0000:00:06.0
2024-03-12 7:35 ` Harald Dunkel
@ 2024-03-12 17:37 ` Bjorn Helgaas
0 siblings, 0 replies; 5+ messages in thread
From: Bjorn Helgaas @ 2024-03-12 17:37 UTC (permalink / raw)
To: Harald Dunkel; +Cc: linux-pci
On Tue, Mar 12, 2024 at 08:35:31AM +0100, Harald Dunkel wrote:
> For the records: Booting with pcie_aspm=off seems to help.
Thanks the bug report and the ASPM connection. We have some important
ASPM fixes queued for v6.9, and it would be interesting to see if they
help here. The fixes have been in linux-next since about 20240307, so
that's probably the easiest thing to test.
Bjorn
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-03-12 17:37 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-02-29 14:52 AER: Corrected error message received from 0000:00:06.0 Harald Dunkel
2024-02-29 20:26 ` Bjorn Helgaas
2024-03-04 7:19 ` Harald Dunkel
2024-03-12 7:35 ` Harald Dunkel
2024-03-12 17:37 ` Bjorn Helgaas
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).