Is it possible to share the output of 'sudo lspci -vv'?
Since this is a laptop, I'm suspecting that ASPM states might have been
enabled which could be causing these errors.
Using 'pci=noaer' only suppresses the errors, but I feel it is better to
root cause the issue and understand the reasons better.
- Vidya Sagar
On 1/2/2021 10:33 PM, Samuel Thibault wrote:
External email: Use caution opening links or attachments
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
