Public bug reported:
Several of our devices are experiencing crashes/reboots, after which the
PCI bus is not fully reset and the Wi-Fi card (Intel BE200) is not
visible until a hard-reboot is performed.
We're running
ubuntu/24.10 (arm64) linux
6.11.0-1007-raspi
Firmware version: 92.67ce4588.0 gl
dmesg output following kernel panic with pci failing...
[0.590299] brcm-pcie fd50.pcie: link down
Line 120: [0.094533] platform fd50.pcie: Fixed dependency
cycle(s) with /scb/pcie@7d50
Line 160: [0.227727] PCI: CLS 0 bytes, default 64
Line 177: [
dmesg output in cold boot with pci initialization working
** Attachment added: "ubuntu_dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5860224/+files/ubuntu_dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
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-F
correcting package to 'linux'
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099935
Title:
PCI initialization failure following kernel pan
RE #5: A attached the apport information to the ticket submission. It's
a headless system so I just copied/attached it directly. Are there any
debug outputs I can gather to help troubleshoot?
RE #6: "Was there a time in the past when you did not encounter this
behavior with an Ubuntu image, or has
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099935
Title:
PCI initialization failure following kernel panic reboot on Raspberry
Pi
Is it possible that the issue might be related to the hardware watchdog
timer? I note the following lines in the dmesg output:
[2.214004] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[2.288820] watchdog: Delayed init of the lockup detector failed: -19
[2.295372] watchdog: H
>> via the -proposed pocket you could even try out the latest version
6.11.0-1010.10.
With the proposed pocket the issue is improved- the issue occurs about
~50% of the time the test is repeated.
Linux ubuntu 6.11.0-1010-raspi #10-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 25
02:37:49 UTC 2025 aarch64
Yes, it's reproducible on the latest raspi kernel.
Please find attached the dmesg output from cold boot (where pci is
working) and following panic/restart (where pci is not working) captured
from upgraded kernel:
Linux ubuntu 6.11.0-1008-raspi #8-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 21
12:05:23 UTC
dmesg output from cold boot (where pci is working) and following
panic/restart (where pci is not working) captured from upgraded kernel:
** Attachment added: "dmesg output from Linux ubuntu 6.11.0-1008-raspi"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5860609/+fi
The problem doesn't occur on Raspberry Pi OS so I thought it might be
helpful to compare the following for each platform:
/boot/config-$(uname -r)
/boot/firmware/cmdline.txt
/boot/firmware/config.txt
dmesg
The zip file attached contains the files.
** Attachment added: "Ubuntu and RPI OS kernel
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098131
Title:
iwlwifi Microcode SW error and restart issue on Ubuntu 24.04/24.10
To manage notifications
>> 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
Confirmed - this issue does not occur with the CM5.
For whatever reason, it's specific the CM4
--
You rece
After upgrade to pieeprom-2024-04-15.bin the problem is still
reproducible following panic/reboot.
ubuntu@ubuntu:~$ sudo dmesg | grep Down
[ 24.148659] bcmgenet fd58.ethernet eth0: Link is Down
ubuntu@ubuntu:~$ lspci
ubuntu@ubuntu:~$ sudo vcgencmd bootloader_version
2024/04/15 14:12:14
ve
Full output from:
sudo dpkg -i linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
** Attachment added: "dpkg output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5862884/+files/dpkg_output.txt
--
You received this bug notification because you are a member
>> >> FWIW, can you test this kernel:
https://people.canonical.com/~juergh/lp2099935/
Got it working (I think) by removing linux-image-6.11.0-1010.
Unfortunately, the PCI problem persists.
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 6.11.0-1009-raspi #9+cbd1 SMP PREEMPT_DYNAMIC Thu Mar 6 12:57:06
>> 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
Full output from:
sudo dpkg -i linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
** Attachment added: "dpkg output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5862885/+files/dpkg_output.txt
--
You received this bug notification because you are a member
The CM4 is plugged into a Wi-Fi 7 Expansion Board (with Intel BE200 Wi-
Fi card) with PoE Ethernet from MCU Zone.
The system is configured to reboot by modifying the /etc/sysctl.conf
file to include:
kernel.panic = 5
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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 8ba17717fbcedd
Please find attached the output of "sudo lspci -vvv" for a 'good state'.
The output for the bad state is empty.
** Attachment added: "sudo lspci -vvv (good state)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5862832/+files/lspci_vvv_good_state.txt
--
You receive
Hi Juerg,
The problem appears to be fixed by updating the unit with the latest
pieeprom-2025-02-11.bin that is shipping with Raspberry Pi OS
https://github.com/raspberrypi/rpi-
eeprom/blob/master/firmware-2711/default/pieeprom-2025-02-11.bin.
I've been unable to reproduce the issue after upgradi
Yes, the problem exists with 6.8 (that's actually where we first noticed it was
occurring).
"operatingSystem": "Ubuntu 24.04 LTS"
"kernel": "6.8.0-1019-raspi"
One update to share is that the problem does also occur on Raspberry Pi
OS as well (contrary to what I stated above). It also occurs ~50%
24 matches
Mail list logo
