dmesg output following kernel panic with pci failing...

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


        Line 120: [    0.094533] platform fd500000.pcie: Fixed dependency 
cycle(s) with /scb/pcie@7d500000
        Line 160: [    0.227727] PCI: CLS 0 bytes, default 64
        Line 177: [    0.339913] brcm-pcie fd500000.pcie: host bridge 
/scb/pcie@7d500000 ranges:
        Line 178: [    0.339985] brcm-pcie fd500000.pcie:   No bus range found 
for /scb/pcie@7d500000, using [bus 00-ff]
        Line 179: [    0.340077] brcm-pcie fd500000.pcie:      MEM 
0x0600000000..0x063fffffff -> 0x00c0000000
        Line 180: [    0.340172] brcm-pcie fd500000.pcie:   IB MEM 
0x0000000000..0x007fffffff -> 0x0400000000
        Line 181: [    0.341474] brcm-pcie fd500000.pcie: PCI host bridge to 
bus 0000:00
        Line 182: [    0.341534] pci_bus 0000:00: root bus resource [bus 00-ff]
        Line 183: [    0.341567] pci_bus 0000:00: root bus resource [mem 
0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff])
        Line 184: [    0.341792] pci 0000:00:00.0: [14e4:2711] type 01 class 
0x060400 PCIe Root Port
        Line 185: [    0.341872] pci 0000:00:00.0: PCI bridge to [bus 00]
        Line 186: [    0.341909] pci 0000:00:00.0:   bridge window [mem 
0x00000000-0x000fffff]
        Line 187: [    0.341952] pci 0000:00:00.0:   bridge window [mem 
0x00000000-0x000fffff 64bit pref]
        Line 188: [    0.342122] pci 0000:00:00.0: PME# supported from D0 D3hot
        Line 189: [    0.346323] pci 0000:00:00.0: bridge configuration invalid 
([bus 00-00]), reconfiguring
        Line 190: [    0.346673] pci_bus 0000:01: supply vpcie3v3 not found, 
using dummy regulator
        Line 191: [    0.346881] pci_bus 0000:01: supply vpcie3v3aux not found, 
using dummy regulator
        Line 192: [    0.346990] pci_bus 0000:01: supply vpcie12v not found, 
using dummy regulator
        Line 193: [    0.590299] brcm-pcie fd500000.pcie: link down
        Line 194: [    0.590642] pci_bus 0000:01: busn_res: [bus 01-ff] end is 
updated to 01
        Line 195: [    0.590703] pci 0000:00:00.0: PCI bridge to [bus 01]
        Line 196: [    0.590749] pci_bus 0000:00: resource 4 [mem 
0x600000000-0x63fffffff]
        Line 197: [    0.591562] pcieport 0000:00:00.0: PME: Signaling with IRQ 
27
        Line 198: [    0.592134] pcieport 0000:00:00.0: AER: enabled with IRQ 27
        Line 199: [    0.593033] pci_bus 0000:01: busn_res: [bus 01] is released
        Line 200: [    0.593911] pci_bus 0000:00: busn_res: [bus 00-ff] is 
released

** Attachment added: "dmesg output following kernel panic with pci failing to 
initialize"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2099935/+attachment/5860223/+files/ubuntu_dmesg_not_working.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell 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:
  New

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/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to