>> FWIW, can you test this kernel:
https://people.canonical.com/~juergh/lp2099935/

Are you able to give some pointers on how to install this correctly?
I've tried several things but I must be doing something wrong or missing
a step.

As a starting point my test system already had(/has) 6.11.0-1010-raspi
installed.

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 6.11.0-1010-raspi #10-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 25 
02:37:49 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

I tried these steps:
sudo dpkg -i linux-buildinfo-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
sudo dpkg -i linux-headers-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
sudo dpkg -i linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
sudo dpkg -i linux-modules-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb

and they complete with no errors, but following reboot, 'uname -a' still
reports 6.11.0-1010-raspi and not 6.11.0-1009-raspi as I assume it
should.

I note that the output to 'ubuntu@ubuntu:~/test_kernel$ sudo dpkg -i
linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb' indicated it
was installing 1009 and then 1010... which looks suspicious (full output
attached):

update-initramfs: Generating /boot/initrd.img-6.11.0-1009-raspi
Using DTB: bcm2711-rpi-cm4.dtb
Installing 
/lib/firmware/6.11.0-1009-raspi/device-tree/broadcom/bcm2711-rpi-cm4.dtb into 
/boot/dtbs/6.11.0-1009-raspi/./bcm2711-rpi-cm4.dtb
Taking backup of bcm2711-rpi-cm4.dtb.
Installing new bcm2711-rpi-cm4.dtb.
flash-kernel: deferring update (trigger activated)
/etc/kernel/postinst.d/zz-flash-kernel:
Using DTB: bcm2711-rpi-cm4.dtb
Installing 
/lib/firmware/6.11.0-1009-raspi/device-tree/broadcom/bcm2711-rpi-cm4.dtb into 
/boot/dtbs/6.11.0-1009-raspi/./bcm2711-rpi-cm4.dtb
Taking backup of bcm2711-rpi-cm4.dtb.
Installing new bcm2711-rpi-cm4.dtb.
flash-kernel: deferring update (trigger activated)
Processing triggers for flash-kernel (3.107ubuntu13~24.10.2) ...
Using DTB: bcm2711-rpi-cm4.dtb
Installing 
/lib/firmware/6.11.0-1010-raspi/device-tree/broadcom/bcm2711-rpi-cm4.dtb into 
/boot/dtbs/6.11.0-1010-raspi/./bcm2711-rpi-cm4.dtb
Taking backup of bcm2711-rpi-cm4.dtb.
Installing new bcm2711-rpi-cm4.dtb.
flash-kernel: installing version 6.11.0-1010-raspi

-- 
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