[monaco][monaco-evk][rb4] Mainline 7.1.0~rc4-g27fa82620cba PCI debug spews during boot: AER: Multiple Correctable error message received from 0000:00:00.0

[lool]

Hi

With latest QLI boot binaries (00123), latest linux mainline as of 2026-05-20 + defconfig, rb4/monaco-evk spews a lot of PCI debug messages during boot . LAVA boot log, GH workflow with link to image:

[    7.342172] pci_bus 0001:01: resource 2 [mem 0x60500000-0x606fffff 64bit pref]
[    7.342355] pcieport 0001:00:00.0: PME: Signaling with IRQ 313
[    7.342682] pcieport 0001:00:00.0: AER: enabled with IRQ 313
...
[    7.748399] pci_bus 0000:01: resource 2 [mem 0x40600000-0x407fffff 64bit pref]
[    7.755994] pcieport 0000:00:00.0: PME: Signaling with IRQ 314
[    7.762870] pcieport 0000:00:00.0: AER: enabled with IRQ 314
[    7.763134] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[    7.777420] pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
[    7.787350] pci 0000:01:00.0:   device [17cb:1103] error status/mask=00001000/0000e000
[    7.795500] pci 0000:01:00.0:    [12] Timeout               
[    7.801532] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[    7.810210] pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
[    7.820122] pci 0000:01:00.0:   device [17cb:1103] error status/mask=00001000/0000e000
[    7.828267] pci 0000:01:00.0:    [12] Timeout               

Also affects linux-next as of 2026-05-20: LAVA boot log, GH workflow with link to image

Thanks

[lool]

It looks like this issue isn't present in latest qcom-next release 7.1.0~rc2-g9f3cbcbfaa5a: LAVA boot log, GH workflow with link to image

[loicpoulain]

This seems to help: c94608e

[krishnachaitanya-linux]

when L0s in PCIe ASPM is enabled, we see lot of errors at the link level and that is causing these prints. we will share a PR which disables L0s in the driver for this platform, we are working with verification team to resolve this. I will update the PR shortly