Is anyone else seeing the issue where the touchscreen/pen don't work
when the computer is first powered on (needs to be rebooted at least
once)? If so, was this supposed to be fixed by this or should that be a
separate bug report?
--
You received this bug notification because you are a member of
** Also affects: linux
Importance: Undecided
Status: New
--
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/1871408
Title:
Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:00
The only solution I found to that speed drop was to reconnect to Wi-Fi
or turn it off and on again. I'm not a developer and I don't know how to
report with more data.
All I know is that running the command lspci:
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Polar
apport information
Distro: Ubuntu 20.04 LTS (Focal Fossa)
Kernel version: 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
apport information
The problem affects other linux distributions:
https://forums.linuxmint.com/viewtopic.php?t=309561
** Bug watch added: Linux Kernel Bug Tracker #203709
https://bugzilla.kernel.org/show_bug.cgi?id=203709
--
You received this bug notification because you are a member of Kern
apport information
More information about the problem:
https://bugzilla.kernel.org/show_bug.cgi?id=203709
--
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/1871408
Title:
Intel Wireless 82
It seems that the error is with some IPv6 configuration. In Ubuntu, I
disabled DNS and Auto Routes and the error went almost unnoticed
--
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/1871408
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
Public bug reported:
Platform: Raspberry Pi CM4
Wi-Fi chipset: Intel BE200 (Wi-Fi 7).
Driver: iwlwifi loaded with firmware version 96.44729d4e.0.
Error:
iwlwifi :01:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
"This indicates a Non-Maskable Interrupt (NMI), which is typically a critical,
unhandle
** Package changed: ubuntu => linux (Ubuntu)
--
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/2098131
Title:
iwlwifi Microcode SW error and restart issue on Ubuntu 24.04/24.10
Status in l
>> >> 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
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
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%
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/
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
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
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
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 Kernel
Packa
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
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
>> 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
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
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
>> 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
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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 Ra
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
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 Kernel
Packages, which
correcting package to 'linux'
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
--
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 followi
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
29 matches
Mail list logo
