linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Are AER corrected errors worrying?
@ 2021-01-02 17:03 Samuel Thibault
  2021-01-03  6:45 ` Vidya Sagar
  0 siblings, 1 reply; 10+ messages in thread
From: Samuel Thibault @ 2021-01-02 17:03 UTC (permalink / raw)
  To: linux-pci

Hello,

Our lab has bought a new Dell Latitude 5410 laptop, I installed debian
bullseye on it with kernel 5.9.0-5-amd64, but it is spitting these
errors now and then (sometimes a dozen per a minute):

Jan  1 23:30:53 begin kernel: [   46.675818] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:02:00.0
Jan  1 23:30:53 begin kernel: [   46.675933] nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan  1 23:30:53 begin kernel: [   46.676048] nvme 0000:02:00.0:   device [15b7:5006] error status/mask=00000001/0000e000
Jan  1 23:30:53 begin kernel: [   46.676140] nvme 0000:02:00.0:    [ 0] RxErr

Since it's corrected it's not actually an issue, but how worrying is it
to see such errors on new hardware? Documentation/PCI/pcieaer-howto.rst
is not commenting whether we are really supposed to see some of them. I
see forums telling to use pci=noaer to stop the error logging, but is
that really something to do?

Samuel

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2021-01-06 22:40 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20210101224028.4akud7meibjavvtf@function>
     [not found] ` <20210104184435.GE1024941@dhcp-10-100-145-180.wdc.com>
2021-01-04 20:12   ` Are AER corrected errors worrying? Samuel Thibault
2021-01-04 21:36     ` Samuel Thibault
2021-01-04 22:33       ` Samuel Thibault
2021-01-06 20:28       ` Samuel Thibault
2021-01-06 21:48         ` Keith Busch
2021-01-06 22:40           ` Samuel Thibault
2021-01-02 17:03 Samuel Thibault
2021-01-03  6:45 ` Vidya Sagar
2021-01-03 11:25   ` Samuel Thibault
2021-01-03 13:48     ` Samuel Thibault

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).