Hi,
We (Ubuntu) have a user who reported [1] occasional PCIe link-down problems on a CM4 after a reboot following a kernel crash. They were able to reproduce the problem with Raspberry Pi OS, so it doesn't seem to be Ubuntu specific. The CM4 is plugged into [2].
I.e.:Leads to (~1 out of 10 times):A good boot:It seems the problem went away after they upgraded the EEPROM from 2024-04-15 to 2025-02-11. I'm not seeing any specific fixes mentioned in the rpi-eeprom git log that would explain this new/better behavior. Are there any fixes in that area for Pi4?
Thanks
...Juerg
[1] https://bugs.launchpad.net/bugs/2099935
[2] http://wiki.mcuzone.com/index.php?title ... Fi6_WLANPi
We (Ubuntu) have a user who reported [1] occasional PCIe link-down problems on a CM4 after a reboot following a kernel crash. They were able to reproduce the problem with Raspberry Pi OS, so it doesn't seem to be Ubuntu specific. The CM4 is plugged into [2].
I.e.:
Code:
echo 1 > /proc/sys/kernel/panicecho c > /proc/sysrq-triggerCode:
[ 0.346323] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring[ 0.346673] pci_bus 0000:01: supply vpcie3v3 not found, using dummy regulator[ 0.346881] pci_bus 0000:01: supply vpcie3v3aux not found, using dummy regulator[ 0.346990] pci_bus 0000:01: supply vpcie12v not found, using dummy regulator[ 0.590299] brcm-pcie fd500000.pcie: link down[ 0.590642] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01[ 0.590703] pci 0000:00:00.0: PCI bridge to [bus 01]Code:
[ 0.347484] pci_bus 0000:01: supply vpcie12v not found, using dummy regulator[ 0.451325] brcm-pcie fd500000.pcie: clkreq-mode set to default[ 0.453464] brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC)Thanks
...Juerg
[1] https://bugs.launchpad.net/bugs/2099935
[2] http://wiki.mcuzone.com/index.php?title ... Fi6_WLANPi
Statistics: Posted by juergh — Tue Mar 18, 2025 10:08 am