pcieport 0000:00:1d.0: AER: Corrected error received: 0000:04:00.0

Question

I'm running Kubuntu 20.04. I recently cloned my system from a 2.5" SSD over to a new 2280 (via dd - aka it's an exact replica of the previous install). Everything runs smoothly, however I've noticed that sometimes I see the following during bootup or shutdown:

[  125.110891] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:04:00.0
[  125.110895] nvme 0000:04:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  125.110898] nvme 0000:04:00.0: AER:   device [10ec:5762] error status/mask=00000001/00006000
[  125.110899] nvme 0000:04:00.0: AER:    [ 0] RxErr                 
[  125.118946] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:04:00.0
[  125.118950] nvme 0000:04:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  125.118952] nvme 0000:04:00.0: AER:   device [10ec:5762] error status/mask=00000001/00006000
[  125.118954] nvme 0000:04:00.0: AER:    [ 0] RxErr
...repeating

It only happens maybe 1 out of 10 reboots, and I've never seen any actual behavioral issues (i.e. crashes, etc). As a small side note, the only other difference I've noticed since moving over to the new SSD is that system audio is very subtly choppy (as described here).

I've found some other posts that suggest getting rid of the "PCIe Bus Error" by adding pci=nomsi and pci=noaer to /etc/default/grub, but those all seem to be addressing other issues (i.e. Ubuntu can't install, or other behavioral problems). Some posts suggest that the OS or kernel may just be too out-of-date for the particular hardware, so since I've been wanting to switch to Neon anyway, I tried a fresh install of Neon 5.24 (different partition). Unfortunately, the behavior was the same: 100% functional OS, just very occasionally pages of the above message shown during bootup or shutdown.

1. Is there a chance that the actual physical SSD is faulty? It was purchased new.
2. If not, is the above of concern?
3. Is there a good solution? My understanding is that pci=noaer just tells it to disable advanced error reporting, which doesn't really seem like the best solution.

The system is a Dell Latitude 5490, and the BIOS is up to date. The SSD is a Teamgroup MP34 4TB (if that's relevant).

Answer 1

The solution was adding pci=nommconf to the kernel boot parameters, which disables Memory-Mapped PCI Configuration Space & reverts to the traditional handling of configuration space

Solution was found here.

Answer 2

I am seeing a similar report, but not on boot or shutdown. It happens once-in-a-while while the system is otherwise operating normally.

It may occur several days after boot, only once every second week, or so. The log says

[171398.391600] pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[171398.391639] pcieport 0000:00:1d.0: AER:   device [8086:a298] error status/mask=00001000/00002000
[171398.391656] pcieport 0000:00:1d.0: AER:    [12] Timeout               
[174951.350475] perf: interrupt took too long (3147 > 3142), lowering kernel.perf_event_max_sample_rate to 63500

There is a slight log difference in the AER:[0] RxErr in the original log, and the AER:[12] Timeout, otherwise they are nearly indectical.

Using lspci the device is a PCI bridge the '1d' device i an Intel PCI bridge

00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (Q270)

My hardware is a HP Elitedesk 800 running Ubuntu 20.04.4.

But maybe the log-error could be safely be ignored due to the

severity=Corrected

message in the log?