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
