From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: linux-nvme@lists.infradead.org
Subject: Are AER corrected errors worrying?
Date: Fri, 1 Jan 2021 23:40:28 +0100 [thread overview]
Message-ID: <20210101224028.4akud7meibjavvtf@function> (raw)
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
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-01-01 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 22:40 Samuel Thibault [this message]
2021-01-04 18:44 ` Are AER corrected errors worrying? Keith Busch
2021-01-04 20:12 ` 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
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=20210101224028.4akud7meibjavvtf@function \
--to=samuel.thibault@ens-lyon.org \
--cc=linux-nvme@lists.infradead.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