The CM4 is plugged into "CM4_WiFi7-PoE" board, please see
http://wiki.mcuzone.com/index.php?title=2004_CM4_WiFi7_WiFi6_WLANPi for
more information.

Is this the correct way to check the bootloader version?

ubuntu@ubuntu:~$ sudo vcgencmd bootloader_version
2023/01/11 17:40:52
version 8ba17717fbcedd4c3b6d4bce7e50c7af4155cba9 (release)
timestamp 1673458852
update-time 0
capabilities 0x0000007f
ubuntu@ubuntu:~$

ubuntu@ubuntu:~$ sudo vcgencmd version
Feb 29 2024 12:24:53
Copyright (c) 2012 Broadcom
version f4e2138c2adc8f3a92a3a65939e458f11d7298ba (clean) (release) (start)


A few notes:
- The manufacturer is able to reproduce the same issue. They have reported that 
the same issue does not occur if you swap the CM4 with a CM5, but I need to 
verify this once I obtain a CM5.
- The issue does not occur when using Raspberry Pi OS (as noted above)

>> I cannot reproduce this locally. For me, PCI devices always show up
after a reboot-after-crash.

Thanks for trying to reproduce - I can make a remote test environment
available if that helps.

It occurs ~half the time for us. I've attached some example test runs
dmesg outputs (these were done with additional
/boot/firmware/cmdline.txt parameters set (pcie_aspm=off as part of an
experiment)

** Attachment added: "dmesg output after panic - 10 runs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5861155/+files/dmesg%20output%20from%2010%20tests.zip

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2099935

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  •     On the first boot, everything works correctly.
  •     However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  •     When this happens:
  o     The Wi-Fi card is not recognized.
  o     The lspci command shows no PCI devices.
  o     The dmesg log includes the message:

  [    0.591441] brcm-pcie fd500000.pcie: link down

  •     A soft reboot does not fix the issue.
  •     The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.    Power up the hardware
  2.    Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.    Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.    Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to