** Tags removed: dcr-incoming
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139276
Title:
[usrmerge] evaluate kernel owned packages for DEP17 compliance
Status in alsa-driver package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware-xilinx-ap1302 package in Ubuntu:
New
Status in linux-firmware-xilinx-vcu package in Ubuntu:
New
Status in nouveau-firmware package in Ubuntu:
New
Status in nvidia-imex-580 package in Ubuntu:
New
Bug description:
The following packages have been identified as having a possible issue
related to usr-merge. DEP-17 describes the issue and problems at
length[0]. The check done was not perfect, and may lead to false
positives. The following was the run to identify possible packages,
further refined with slight pruning of obvious false positives
apt-file search --package-only --regexp
'^/(sbin|bin|lib|lib32|lib64|libx32)/*'
Lintian, when run on a suitably new system (such as within a resolute
build environment), will provide some errors related to usr-merge. an
example of a Lintian error from busybox
E: busybox-static: aliased-location [bin/]
E: busybox-static: aliased-location [bin/static-sh]
Please evaluate the follow packages for any issues dictated in dep17.
If any package below is not a part of the Kernel set, please let me
know and I'll file separate bugs for those packages (a bunch are
nvidia based, and I'm not sure who is owning them)
[0] https://dep-team.pages.debian.net/deps/dep17/
alsa-driver
fabric-manager-570
fabric-manager-580
fabric-manager-590
linux
linux-firmware-xilinx-ap1302
linux-firmware-xilinx-vcu
linux-realtime
linux-restricted-modules
linux-restricted-modules-aws
linux-restricted-modules-azure
linux-restricted-modules-gcp
linux-restricted-modules-oracle
linux-restricted-signatures
linux-riscv
nouveau-firmware
nvidia-graphics-drivers-580
nvidia-graphics-drivers-580-server
nvidia-graphics-drivers-590
nvidia-graphics-drivers-590-server
nvidia-imex-570
nvidia-imex-580
nvidia-imex-590
nvidia-prime
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2139276/+subscriptions
четверг
[Bug 2142878] Re: While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing several readlink msg
** No longer affects: initramfs-tools (Ubuntu)
** No longer affects: multipath-tools (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142878
Title:
While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing
several readlink msg
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in rust-coreutils package in Ubuntu:
New
Bug description:
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-6.19.0-6-generic:
Installed: 6.19.0-6.6
Candidate: 6.19.0-6.6
Version table:
*** 6.19.0-6.6 500
500 http://ports.ubuntu.com/ubuntu-ports resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$ sudo add-apt-repository --yes ppa:canonical-kernel-team/unstable
Repository: 'Types: deb
URIs: https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu/
Suites: resolute
Components: main
'
Description:
CONFIGURED FOR DEVELOPMENT
Cowboy builders all the way.
More info: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute InRelease [20.2 kB]
Hit:2 http://ports.ubuntu.com/ubuntu-ports resolute InRelease
Get:3 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages [8,560 B]
Hit:4 http://ports.ubuntu.com/ubuntu-ports resolute-updates InRelease
Get:5 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main Translation-en [8,188 B]
Hit:6 http://ports.ubuntu.com/ubuntu-ports resolute-backports InRelease
Hit:7 http://ports.ubuntu.com/ubuntu-ports resolute-security InRelease
Fetched 37.0 kB in 1s (44.4 kB/s)
Reading package lists... Done
ubuntu@zlin:~$ sudo apt install linux-image-7.0.0-2-generic=7.0.0-2.2 linux-modules-7.0.0-2-generic=7.0.0-2.2
Installing:
linux-image-7.0.0-2-generic linux-modules-7.0.0-2-generic
Suggested packages:
linux-unstable-tools linux-headers-7.0.0-2-generic
Summary:
Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 43.9 MB
Space needed: 95.0 MB / 181 GB available
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-modules-7.0.0-2-generic s390x 7.0.0-2.2 [33.3 MB]
Get:2 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-image-7.0.0-2-generic s390x 7.0.0-2.2 [10.6 MB]
Fetched 43.9 MB in 47s (937 kB/s)
Selecting previously unselected package linux-modules-7.0.0-2-generic.
(Reading database ... 71022 files and directories currently installed.)
Preparing to unpack .../linux-modules-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Selecting previously unselected package linux-image-7.0.0-2-generic.
Preparing to unpack .../linux-image-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-image-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-image-7.0.0-2-generic (7.0.0-2.2) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-7.0.0-2-generic
I: /boot/initrd.img is now a symlink to initrd.img-7.0.0-2-generic
Processing triggers for linux-image-7.0.0-2-generic (7.0.0-2.2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-7.0.0-2-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-7.0.0-2-generic
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/sda/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-0/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-1/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: '/sys/class/extcon/*': No such file or directory
readlink: /sys/class/gpio/export/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: /sys/class/gpio/unexport/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: '/sys/class/phy/*': No such file or directory
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or dir
ectory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
/etc/kernel/postinst.d/zz-zipl:
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Pending kernel upgrade!
Running kernel version:
6.19.0-6-generic
Diagnostics:
The currently running kernel version is not the expected kernel version
7.0.0-2-generic.
Restarting the system to load the new kernel will not be handled automatically,
so you should consider rebooting.
Failed to check for processor microcode upgrades.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
ubuntu@zlin:~$ reboot
Call to Reboot failed: Access denied as the requested operation requires interactive authentication. However, interactive authentication has not been enabled by the calling program.
ubuntu@zlin:~$ sudo reboot
ubuntu@zlin:~$ Connection to zlin closed by remote host.
Connection to zlin closed.
user@workstation:~$ ssh ubuntu@zlin
Welcome to Ubuntu Resolute Raccoon (development branch) (GNU/Linux 7.0.0-2-generic s390x)
* Documentation: https://docs.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri 27 Feb 2026 05:14:49 PM UTC
System load: 0.33 Memory usage: 1% Processes: 177
Usage of /: 5.3% of 187.93GB Swap usage: 0% Users logged in: 0
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status
Last login: Fri Feb 27 17:10:32 2026 from 10.172.66.67
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-7.0.0-2-generic:
Installed: 7.0.0-2.2
Candidate: 7.0.0-2.2
Version table:
*** 7.0.0-2.2 500
500 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$
The installation of the snaptshot4 ISO itself was fine.
Could actually be kernel, updateinitramfs or apparmor ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142878/+subscriptions
** No longer affects: multipath-tools (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142878
Title:
While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing
several readlink msg
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in rust-coreutils package in Ubuntu:
New
Bug description:
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-6.19.0-6-generic:
Installed: 6.19.0-6.6
Candidate: 6.19.0-6.6
Version table:
*** 6.19.0-6.6 500
500 http://ports.ubuntu.com/ubuntu-ports resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$ sudo add-apt-repository --yes ppa:canonical-kernel-team/unstable
Repository: 'Types: deb
URIs: https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu/
Suites: resolute
Components: main
'
Description:
CONFIGURED FOR DEVELOPMENT
Cowboy builders all the way.
More info: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute InRelease [20.2 kB]
Hit:2 http://ports.ubuntu.com/ubuntu-ports resolute InRelease
Get:3 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages [8,560 B]
Hit:4 http://ports.ubuntu.com/ubuntu-ports resolute-updates InRelease
Get:5 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main Translation-en [8,188 B]
Hit:6 http://ports.ubuntu.com/ubuntu-ports resolute-backports InRelease
Hit:7 http://ports.ubuntu.com/ubuntu-ports resolute-security InRelease
Fetched 37.0 kB in 1s (44.4 kB/s)
Reading package lists... Done
ubuntu@zlin:~$ sudo apt install linux-image-7.0.0-2-generic=7.0.0-2.2 linux-modules-7.0.0-2-generic=7.0.0-2.2
Installing:
linux-image-7.0.0-2-generic linux-modules-7.0.0-2-generic
Suggested packages:
linux-unstable-tools linux-headers-7.0.0-2-generic
Summary:
Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 43.9 MB
Space needed: 95.0 MB / 181 GB available
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-modules-7.0.0-2-generic s390x 7.0.0-2.2 [33.3 MB]
Get:2 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-image-7.0.0-2-generic s390x 7.0.0-2.2 [10.6 MB]
Fetched 43.9 MB in 47s (937 kB/s)
Selecting previously unselected package linux-modules-7.0.0-2-generic.
(Reading database ... 71022 files and directories currently installed.)
Preparing to unpack .../linux-modules-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Selecting previously unselected package linux-image-7.0.0-2-generic.
Preparing to unpack .../linux-image-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-image-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-image-7.0.0-2-generic (7.0.0-2.2) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-7.0.0-2-generic
I: /boot/initrd.img is now a symlink to initrd.img-7.0.0-2-generic
Processing triggers for linux-image-7.0.0-2-generic (7.0.0-2.2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-7.0.0-2-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-7.0.0-2-generic
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/sda/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-0/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-1/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: '/sys/class/extcon/*': No such file or directory
readlink: /sys/class/gpio/export/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: /sys/class/gpio/unexport/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: '/sys/class/phy/*': No such file or directory
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or dir
ectory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
/etc/kernel/postinst.d/zz-zipl:
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Pending kernel upgrade!
Running kernel version:
6.19.0-6-generic
Diagnostics:
The currently running kernel version is not the expected kernel version
7.0.0-2-generic.
Restarting the system to load the new kernel will not be handled automatically,
so you should consider rebooting.
Failed to check for processor microcode upgrades.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
ubuntu@zlin:~$ reboot
Call to Reboot failed: Access denied as the requested operation requires interactive authentication. However, interactive authentication has not been enabled by the calling program.
ubuntu@zlin:~$ sudo reboot
ubuntu@zlin:~$ Connection to zlin closed by remote host.
Connection to zlin closed.
user@workstation:~$ ssh ubuntu@zlin
Welcome to Ubuntu Resolute Raccoon (development branch) (GNU/Linux 7.0.0-2-generic s390x)
* Documentation: https://docs.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri 27 Feb 2026 05:14:49 PM UTC
System load: 0.33 Memory usage: 1% Processes: 177
Usage of /: 5.3% of 187.93GB Swap usage: 0% Users logged in: 0
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status
Last login: Fri Feb 27 17:10:32 2026 from 10.172.66.67
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-7.0.0-2-generic:
Installed: 7.0.0-2.2
Candidate: 7.0.0-2.2
Version table:
*** 7.0.0-2.2 500
500 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$
The installation of the snaptshot4 ISO itself was fine.
Could actually be kernel, updateinitramfs or apparmor ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142878/+subscriptions
[Bug 2146477] [NEW] 26.04 amd64 snapshot 4 "ModuleNotFoundError: No module named 'cutin.vendor'"
Public bug reported:
The installer boots up to a point where it continuously cycles every few
seconds between a screen that just says "Ubuntu Resolute Raccoon
(development branch) ubuntu-server tty1" and the python backtrace in the
screenshot. The backtrace blips by fast enough that I was only able to
see it by capturing it on video and scrubbing it frame by frame.
What I did:
I downloaded the 26.04 snapshot4 amd64 iso
I put it on a ventoy usb stick
I booted the image on an amd64 pc (dell t5500)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "20260326_093851.jpg"
https://bugs.launchpad.net/bugs/2146477/+attachment/5956034/+files/20260326_093851.jpg
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146477
Title:
26.04 amd64 snapshot 4 "ModuleNotFoundError: No module named
'cutin.vendor'"
Status in linux package in Ubuntu:
New
Bug description:
The installer boots up to a point where it continuously cycles every
few seconds between a screen that just says "Ubuntu Resolute Raccoon
(development branch) ubuntu-server tty1" and the python backtrace in
the screenshot. The backtrace blips by fast enough that I was only
able to see it by capturing it on video and scrubbing it frame by
frame.
What I did:
I downloaded the 26.04 snapshot4 amd64 iso
I put it on a ventoy usb stick
I booted the image on an amd64 pc (dell t5500)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146477/+subscriptions
The installer boots up to a point where it continuously cycles every few
seconds between a screen that just says "Ubuntu Resolute Raccoon
(development branch) ubuntu-server tty1" and the python backtrace in the
screenshot. The backtrace blips by fast enough that I was only able to
see it by capturing it on video and scrubbing it frame by frame.
What I did:
I downloaded the 26.04 snapshot4 amd64 iso
I put it on a ventoy usb stick
I booted the image on an amd64 pc (dell t5500)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "20260326_093851.jpg"
https://bugs.launchpad.net/bugs/2146477/+attachment/5956034/+files/20260326_093851.jpg
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146477
Title:
26.04 amd64 snapshot 4 "ModuleNotFoundError: No module named
'cutin.vendor'"
Status in linux package in Ubuntu:
New
Bug description:
The installer boots up to a point where it continuously cycles every
few seconds between a screen that just says "Ubuntu Resolute Raccoon
(development branch) ubuntu-server tty1" and the python backtrace in
the screenshot. The backtrace blips by fast enough that I was only
able to see it by capturing it on video and scrubbing it frame by
frame.
What I did:
I downloaded the 26.04 snapshot4 amd64 iso
I put it on a ventoy usb stick
I booted the image on an amd64 pc (dell t5500)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146477/+subscriptions
[Bug 2146472] [NEW] Fix potential page fault caused by sha256 calculation
Public bug reported:
SRU Justification:
[Impact]
Calculating the SHA-256 of a buffer with a size larger than 2GB and is
not divisible by 64 will lead to a page fault.
More specifically, this was seen in the firmware loader on Ubuntu
24.04.4 LTS, where CONFIG_FW_LOADER_DEBUG is enabled. Loading a firmware
file that is 3619035928 bytes fails with the following splat:
[1667258.914177] BUG: unable to handle page fault for address: ffffb731b3fbcd40
[1667258.914188] #PF: supervisor read access in kernel mode
[1667258.914193] #PF: error_code(0x0000) - not-present page
[1667258.914198] PGD 100000067 P4D 100000067 PUD 1002d4067 PMD 529eec067 PTE 0
[1667258.914208] Oops: 0000 [#3] PREEMPT SMP PTI
[1667258.914214] CPU: 11 PID: 1252644 Comm: kworker/11:1 Tainted: P D W OE 6.8.0-62-generic #65-Ubuntu
[1667258.914223] Hardware name: Wiwynn Twin Lakes MP/Twin Lakes Passive MP, BIOS YMGPE07 12/23/2019
[1667258.914229] Workqueue: events sahara_processing [qaic]
[1667258.914257] RIP: 0010:memcpy_orig+0x105/0x130
[1667258.914267] Code: 0f 1f 44 00 00 83 fa 04 72 1b 8b 0e 44 8b 44 16 fc 89 0f 44 89 44 17 fc c3 cc cc cc cc 0f 1f 84 00 00 00 00 00 83 ea 01 72 19 <0f> b6 0e 74 12 4c 0f b6 46 01 4c 0f b6 0c 16 44 88 47 01 44 88 0c
[1667258.914278] RSP: 0018:ffffb731a3c57c78 EFLAGS: 00010202
[1667258.914284] RAX: ffffa0ac564f41b0 RBX: ffffa0ac564f41b0 RCX: 00000000d7af7212
[1667258.914290] RDX: 0000000000000001 RSI: ffffb731b3fbcd40 RDI: ffffa0ac564f41b0
[1667258.914295] RBP: ffffb731a3c57ca8 R08: 000000005ab6c582 R09: 0000000072a12f7b
[1667258.914301] R10: 0000000064f65b73 R11: 000000001cb47ae9 R12: ffffffff93d71d40
[1667258.914306] R13: ffffb731b3fbcd40 R14: 0000000000000002 R15: ffffb7322024b000
[1667258.914311] FS: 0000000000000000(0000) GS:ffffa0bb7f580000(0000) knlGS:0000000000000000
[1667258.914318] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[1667258.914323] CR2: ffffb731b3fbcd40 CR3: 0000000b09e3c005 CR4: 00000000007706f0
[1667258.914329] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[1667258.914334] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[1667258.914339] PKRU: 55555554
[1667258.914342] Call Trace:
[1667258.914346] <TASK>
[1667258.914350] ? show_regs+0x6d/0x80
[1667258.914358] ? __die+0x24/0x80
[1667258.914364] ? page_fault_oops+0x99/0x1b0
[1667258.914372] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[1667258.914380] ? __bad_area_nosemaphore+0x19e/0x2c0
[1667258.914388] ? bad_area_nosemaphore+0x16/0x30
[1667258.914394] ? do_kern_addr_fault+0x7b/0xa0
[1667258.914400] ? exc_page_fault+0x1a4/0x1b0
[1667258.914407] ? asm_exc_page_fault+0x27/0x30
[1667258.914417] ? memcpy_orig+0x105/0x130
[1667258.914425] ? lib_sha256_base_do_update.isra.0+0x5d/0x1d0 [sha256_ssse3]
[1667258.914433] ? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]
[1667258.914440] sha256_finup+0xf5/0x150 [sha256_ssse3]
[1667258.914447] sha256_avx2_digest+0x55/0x70 [sha256_ssse3]
[1667258.914453] crypto_shash_digest+0x2a/0x60
[1667258.914460] fw_log_firmware_info+0x113/0x1b0
[1667258.914469] _request_firmware+0x19d/0x4b0
[1667258.914476] firmware_request_nowarn+0x36/0x60
[1667258.914482] sahara_processing+0x399/0x710 [qaic]
[1667258.914501] process_one_work+0x181/0x3a0
[1667258.914508] worker_thread+0x306/0x440
[1667258.914514] ? _raw_spin_lock_irqsave+0xe/0x20
[1667258.914521] ? __pfx_worker_thread+0x10/0x10
[1667258.914526] kthread+0xef/0x120
[1667258.914533] ? __pfx_kthread+0x10/0x10
[1667258.914540] ret_from_fork+0x44/0x70
[1667258.914546] ? __pfx_kthread+0x10/0x10
[1667258.914552] ret_from_fork_asm+0x1b/0x30
[1667258.914561] </TASK>
[1667258.914564] Modules linked in: tls nfsv3 rpcsec_gss_krb5 nfsv4 nfs netfs snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore qrtr_mhi(OE) qrtr(OE) xt_conntrack xt_MASQUERADE bridge stp llc xt_set ip_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nf_tables xfrm_user xfrm_algo openafs(POE-) overlay cfg80211 binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common isst_if_common skx_edac skx_edac_common nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm cmdlinepart spi_nor irqbypass mtd qaic(OE) mei_me rapl intel_cstate i2c_i801 mhi(OE) spi_intel_pci mei switchtec(OE) ioatdma spi_intel i2c_smbus intel_pch_thermal dca ipmi_si acpi_power_meter acpi_ipmi ipmi_devintf ipmi_msghandler acpi_pad mac_hid sch_fq_codel dm_multipath nfsd msr parport_pc auth_rpcgss nfs_acl lockd ppdev grace lp parport sunrpc efi_pstore nfnetlink dmi_sysfs
[1667258.914665] ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel sha256_ssse3 bnxt_en sha1_ssse3 nvme_core xhci_pci nvme_auth xhci_pci_renesas wmi aesni_intel crypto_simd cryptd
[1667258.914741] CR2: ffffb731b3fbcd40
[1667258.914746] ---[ end trace 0000000000000000 ]---
[Fix]
Cherry-pick upstream commit:
70165dc3ec8c ("crypto: sha256 - fix crash at kexec")
[Test Plan]
* An x86_64 system with Ubuntu 24.04.4 LTS, Linux 6.8.0-101-generic x86_64 and Qualcomm AIC100 PCIe card installed
* Create a dummy file with size larger than 2GB and not divisible by 64, compress it using zstd, then replace it with any of the firmware files in /lib/firmware/qcom/aic100/
* Reset the AIC100 device to force reloading the firmware files by writing 1 to /sys/bus/mhi/devices/mhi0/soc_reset
[Where Problems Could Occur]
Any <v6.16 kernel entity that makes use of sha256_update()
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146472
Title:
Fix potential page fault caused by sha256 calculation
Status in linux package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
Calculating the SHA-256 of a buffer with a size larger than 2GB and is
not divisible by 64 will lead to a page fault.
More specifically, this was seen in the firmware loader on Ubuntu
24.04.4 LTS, where CONFIG_FW_LOADER_DEBUG is enabled. Loading a
firmware file that is 3619035928 bytes fails with the following splat:
[1667258.914177] BUG: unable to handle page fault for address: ffffb731b3fbcd40
[1667258.914188] #PF: supervisor read access in kernel mode
[1667258.914193] #PF: error_code(0x0000) - not-present page
[1667258.914198] PGD 100000067 P4D 100000067 PUD 1002d4067 PMD 529eec067 PTE 0
[1667258.914208] Oops: 0000 [#3] PREEMPT SMP PTI
[1667258.914214] CPU: 11 PID: 1252644 Comm: kworker/11:1 Tainted: P D W OE 6.8.0-62-generic #65-Ubuntu
[1667258.914223] Hardware name: Wiwynn Twin Lakes MP/Twin Lakes Passive MP, BIOS YMGPE07 12/23/2019
[1667258.914229] Workqueue: events sahara_processing [qaic]
[1667258.914257] RIP: 0010:memcpy_orig+0x105/0x130
[1667258.914267] Code: 0f 1f 44 00 00 83 fa 04 72 1b 8b 0e 44 8b 44 16 fc 89 0f 44 89 44 17 fc c3 cc cc cc cc 0f 1f 84 00 00 00 00 00 83 ea 01 72 19 <0f> b6 0e 74 12 4c 0f b6 46 01 4c 0f b6 0c 16 44 88 47 01 44 88 0c
[1667258.914278] RSP: 0018:ffffb731a3c57c78 EFLAGS: 00010202
[1667258.914284] RAX: ffffa0ac564f41b0 RBX: ffffa0ac564f41b0 RCX: 00000000d7af7212
[1667258.914290] RDX: 0000000000000001 RSI: ffffb731b3fbcd40 RDI: ffffa0ac564f41b0
[1667258.914295] RBP: ffffb731a3c57ca8 R08: 000000005ab6c582 R09: 0000000072a12f7b
[1667258.914301] R10: 0000000064f65b73 R11: 000000001cb47ae9 R12: ffffffff93d71d40
[1667258.914306] R13: ffffb731b3fbcd40 R14: 0000000000000002 R15: ffffb7322024b000
[1667258.914311] FS: 0000000000000000(0000) GS:ffffa0bb7f580000(0000) knlGS:0000000000000000
[1667258.914318] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[1667258.914323] CR2: ffffb731b3fbcd40 CR3: 0000000b09e3c005 CR4: 00000000007706f0
[1667258.914329] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[1667258.914334] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[1667258.914339] PKRU: 55555554
[1667258.914342] Call Trace:
[1667258.914346] <TASK>
[1667258.914350] ? show_regs+0x6d/0x80
[1667258.914358] ? __die+0x24/0x80
[1667258.914364] ? page_fault_oops+0x99/0x1b0
[1667258.914372] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[1667258.914380] ? __bad_area_nosemaphore+0x19e/0x2c0
[1667258.914388] ? bad_area_nosemaphore+0x16/0x30
[1667258.914394] ? do_kern_addr_fault+0x7b/0xa0
[1667258.914400] ? exc_page_fault+0x1a4/0x1b0
[1667258.914407] ? asm_exc_page_fault+0x27/0x30
[1667258.914417] ? memcpy_orig+0x105/0x130
[1667258.914425] ? lib_sha256_base_do_update.isra.0+0x5d/0x1d0 [sha256_ssse3]
[1667258.914433] ? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]
[1667258.914440] sha256_finup+0xf5/0x150 [sha256_ssse3]
[1667258.914447] sha256_avx2_digest+0x55/0x70 [sha256_ssse3]
[1667258.914453] crypto_shash_digest+0x2a/0x60
[1667258.914460] fw_log_firmware_info+0x113/0x1b0
[1667258.914469] _request_firmware+0x19d/0x4b0
[1667258.914476] firmware_request_nowarn+0x36/0x60
[1667258.914482] sahara_processing+0x399/0x710 [qaic]
[1667258.914501] process_one_work+0x181/0x3a0
[1667258.914508] worker_thread+0x306/0x440
[1667258.914514] ? _raw_spin_lock_irqsave+0xe/0x20
[1667258.914521] ? __pfx_worker_thread+0x10/0x10
[1667258.914526] kthread+0xef/0x120
[1667258.914533] ? __pfx_kthread+0x10/0x10
[1667258.914540] ret_from_fork+0x44/0x70
[1667258.914546] ? __pfx_kthread+0x10/0x10
[1667258.914552] ret_from_fork_asm+0x1b/0x30
[1667258.914561] </TASK>
[1667258.914564] Modules linked in: tls nfsv3 rpcsec_gss_krb5 nfsv4 nfs netfs snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore qrtr_mhi(OE) qrtr(OE) xt_conntrack xt_MASQUERADE bridge stp llc xt_set ip_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nf_tables xfrm_user xfrm_algo openafs(POE-) overlay cfg80211 binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common isst_if_common skx_edac skx_edac_common nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm cmdlinepart spi_nor irqbypass mtd qaic(OE) mei_me rapl intel_cstate i2c_i801 mhi(OE) spi_intel_pci mei switchtec(OE) ioatdma spi_intel i2c_smbus intel_pch_thermal dca ipmi_si acpi_power_meter acpi_ipmi ipmi_devintf ipmi_msghandler acpi_pad mac_hid sch_fq_codel dm_multipath nfsd msr parport_pc auth_rpcgss nfs_acl lockd ppdev grace lp parport sunrpc efi_pstore nfnetlink dmi_sysfs
[1667258.914665] ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel sha256_ssse3 bnxt_en sha1_ssse3 nvme_core xhci_pci nvme_auth xhci_pci_renesas wmi aesni_intel crypto_simd cryptd
[1667258.914741] CR2: ffffb731b3fbcd40
[1667258.914746] ---[ end trace 0000000000000000 ]---
[Fix]
Cherry-pick upstream commit:
70165dc3ec8c ("crypto: sha256 - fix crash at kexec")
[Test Plan]
* An x86_64 system with Ubuntu 24.04.4 LTS, Linux 6.8.0-101-generic x86_64 and Qualcomm AIC100 PCIe card installed
* Create a dummy file with size larger than 2GB and not divisible by 64, compress it using zstd, then replace it with any of the firmware files in /lib/firmware/qcom/aic100/
* Reset the AIC100 device to force reloading the firmware files by writing 1 to /sys/bus/mhi/devices/mhi0/soc_reset
[Where Problems Could Occur]
Any <v6.16 kernel entity that makes use of sha256_update()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146472/+subscriptions
SRU Justification:
[Impact]
Calculating the SHA-256 of a buffer with a size larger than 2GB and is
not divisible by 64 will lead to a page fault.
More specifically, this was seen in the firmware loader on Ubuntu
24.04.4 LTS, where CONFIG_FW_LOADER_DEBUG is enabled. Loading a firmware
file that is 3619035928 bytes fails with the following splat:
[1667258.914177] BUG: unable to handle page fault for address: ffffb731b3fbcd40
[1667258.914188] #PF: supervisor read access in kernel mode
[1667258.914193] #PF: error_code(0x0000) - not-present page
[1667258.914198] PGD 100000067 P4D 100000067 PUD 1002d4067 PMD 529eec067 PTE 0
[1667258.914208] Oops: 0000 [#3] PREEMPT SMP PTI
[1667258.914214] CPU: 11 PID: 1252644 Comm: kworker/11:1 Tainted: P D W OE 6.8.0-62-generic #65-Ubuntu
[1667258.914223] Hardware name: Wiwynn Twin Lakes MP/Twin Lakes Passive MP, BIOS YMGPE07 12/23/2019
[1667258.914229] Workqueue: events sahara_processing [qaic]
[1667258.914257] RIP: 0010:memcpy_orig+0x105/0x130
[1667258.914267] Code: 0f 1f 44 00 00 83 fa 04 72 1b 8b 0e 44 8b 44 16 fc 89 0f 44 89 44 17 fc c3 cc cc cc cc 0f 1f 84 00 00 00 00 00 83 ea 01 72 19 <0f> b6 0e 74 12 4c 0f b6 46 01 4c 0f b6 0c 16 44 88 47 01 44 88 0c
[1667258.914278] RSP: 0018:ffffb731a3c57c78 EFLAGS: 00010202
[1667258.914284] RAX: ffffa0ac564f41b0 RBX: ffffa0ac564f41b0 RCX: 00000000d7af7212
[1667258.914290] RDX: 0000000000000001 RSI: ffffb731b3fbcd40 RDI: ffffa0ac564f41b0
[1667258.914295] RBP: ffffb731a3c57ca8 R08: 000000005ab6c582 R09: 0000000072a12f7b
[1667258.914301] R10: 0000000064f65b73 R11: 000000001cb47ae9 R12: ffffffff93d71d40
[1667258.914306] R13: ffffb731b3fbcd40 R14: 0000000000000002 R15: ffffb7322024b000
[1667258.914311] FS: 0000000000000000(0000) GS:ffffa0bb7f580000(0000) knlGS:0000000000000000
[1667258.914318] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[1667258.914323] CR2: ffffb731b3fbcd40 CR3: 0000000b09e3c005 CR4: 00000000007706f0
[1667258.914329] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[1667258.914334] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[1667258.914339] PKRU: 55555554
[1667258.914342] Call Trace:
[1667258.914346] <TASK>
[1667258.914350] ? show_regs+0x6d/0x80
[1667258.914358] ? __die+0x24/0x80
[1667258.914364] ? page_fault_oops+0x99/0x1b0
[1667258.914372] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[1667258.914380] ? __bad_area_nosemaphore+0x19e/0x2c0
[1667258.914388] ? bad_area_nosemaphore+0x16/0x30
[1667258.914394] ? do_kern_addr_fault+0x7b/0xa0
[1667258.914400] ? exc_page_fault+0x1a4/0x1b0
[1667258.914407] ? asm_exc_page_fault+0x27/0x30
[1667258.914417] ? memcpy_orig+0x105/0x130
[1667258.914425] ? lib_sha256_base_do_update.isra.0+0x5d/0x1d0 [sha256_ssse3]
[1667258.914433] ? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]
[1667258.914440] sha256_finup+0xf5/0x150 [sha256_ssse3]
[1667258.914447] sha256_avx2_digest+0x55/0x70 [sha256_ssse3]
[1667258.914453] crypto_shash_digest+0x2a/0x60
[1667258.914460] fw_log_firmware_info+0x113/0x1b0
[1667258.914469] _request_firmware+0x19d/0x4b0
[1667258.914476] firmware_request_nowarn+0x36/0x60
[1667258.914482] sahara_processing+0x399/0x710 [qaic]
[1667258.914501] process_one_work+0x181/0x3a0
[1667258.914508] worker_thread+0x306/0x440
[1667258.914514] ? _raw_spin_lock_irqsave+0xe/0x20
[1667258.914521] ? __pfx_worker_thread+0x10/0x10
[1667258.914526] kthread+0xef/0x120
[1667258.914533] ? __pfx_kthread+0x10/0x10
[1667258.914540] ret_from_fork+0x44/0x70
[1667258.914546] ? __pfx_kthread+0x10/0x10
[1667258.914552] ret_from_fork_asm+0x1b/0x30
[1667258.914561] </TASK>
[1667258.914564] Modules linked in: tls nfsv3 rpcsec_gss_krb5 nfsv4 nfs netfs snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore qrtr_mhi(OE) qrtr(OE) xt_conntrack xt_MASQUERADE bridge stp llc xt_set ip_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nf_tables xfrm_user xfrm_algo openafs(POE-) overlay cfg80211 binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common isst_if_common skx_edac skx_edac_common nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm cmdlinepart spi_nor irqbypass mtd qaic(OE) mei_me rapl intel_cstate i2c_i801 mhi(OE) spi_intel_pci mei switchtec(OE) ioatdma spi_intel i2c_smbus intel_pch_thermal dca ipmi_si acpi_power_meter acpi_ipmi ipmi_devintf ipmi_msghandler acpi_pad mac_hid sch_fq_codel dm_multipath nfsd msr parport_pc auth_rpcgss nfs_acl lockd ppdev grace lp parport sunrpc efi_pstore nfnetlink dmi_sysfs
[1667258.914665] ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel sha256_ssse3 bnxt_en sha1_ssse3 nvme_core xhci_pci nvme_auth xhci_pci_renesas wmi aesni_intel crypto_simd cryptd
[1667258.914741] CR2: ffffb731b3fbcd40
[1667258.914746] ---[ end trace 0000000000000000 ]---
[Fix]
Cherry-pick upstream commit:
70165dc3ec8c ("crypto: sha256 - fix crash at kexec")
[Test Plan]
* An x86_64 system with Ubuntu 24.04.4 LTS, Linux 6.8.0-101-generic x86_64 and Qualcomm AIC100 PCIe card installed
* Create a dummy file with size larger than 2GB and not divisible by 64, compress it using zstd, then replace it with any of the firmware files in /lib/firmware/qcom/aic100/
* Reset the AIC100 device to force reloading the firmware files by writing 1 to /sys/bus/mhi/devices/mhi0/soc_reset
[Where Problems Could Occur]
Any <v6.16 kernel entity that makes use of sha256_update()
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146472
Title:
Fix potential page fault caused by sha256 calculation
Status in linux package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
Calculating the SHA-256 of a buffer with a size larger than 2GB and is
not divisible by 64 will lead to a page fault.
More specifically, this was seen in the firmware loader on Ubuntu
24.04.4 LTS, where CONFIG_FW_LOADER_DEBUG is enabled. Loading a
firmware file that is 3619035928 bytes fails with the following splat:
[1667258.914177] BUG: unable to handle page fault for address: ffffb731b3fbcd40
[1667258.914188] #PF: supervisor read access in kernel mode
[1667258.914193] #PF: error_code(0x0000) - not-present page
[1667258.914198] PGD 100000067 P4D 100000067 PUD 1002d4067 PMD 529eec067 PTE 0
[1667258.914208] Oops: 0000 [#3] PREEMPT SMP PTI
[1667258.914214] CPU: 11 PID: 1252644 Comm: kworker/11:1 Tainted: P D W OE 6.8.0-62-generic #65-Ubuntu
[1667258.914223] Hardware name: Wiwynn Twin Lakes MP/Twin Lakes Passive MP, BIOS YMGPE07 12/23/2019
[1667258.914229] Workqueue: events sahara_processing [qaic]
[1667258.914257] RIP: 0010:memcpy_orig+0x105/0x130
[1667258.914267] Code: 0f 1f 44 00 00 83 fa 04 72 1b 8b 0e 44 8b 44 16 fc 89 0f 44 89 44 17 fc c3 cc cc cc cc 0f 1f 84 00 00 00 00 00 83 ea 01 72 19 <0f> b6 0e 74 12 4c 0f b6 46 01 4c 0f b6 0c 16 44 88 47 01 44 88 0c
[1667258.914278] RSP: 0018:ffffb731a3c57c78 EFLAGS: 00010202
[1667258.914284] RAX: ffffa0ac564f41b0 RBX: ffffa0ac564f41b0 RCX: 00000000d7af7212
[1667258.914290] RDX: 0000000000000001 RSI: ffffb731b3fbcd40 RDI: ffffa0ac564f41b0
[1667258.914295] RBP: ffffb731a3c57ca8 R08: 000000005ab6c582 R09: 0000000072a12f7b
[1667258.914301] R10: 0000000064f65b73 R11: 000000001cb47ae9 R12: ffffffff93d71d40
[1667258.914306] R13: ffffb731b3fbcd40 R14: 0000000000000002 R15: ffffb7322024b000
[1667258.914311] FS: 0000000000000000(0000) GS:ffffa0bb7f580000(0000) knlGS:0000000000000000
[1667258.914318] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[1667258.914323] CR2: ffffb731b3fbcd40 CR3: 0000000b09e3c005 CR4: 00000000007706f0
[1667258.914329] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[1667258.914334] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[1667258.914339] PKRU: 55555554
[1667258.914342] Call Trace:
[1667258.914346] <TASK>
[1667258.914350] ? show_regs+0x6d/0x80
[1667258.914358] ? __die+0x24/0x80
[1667258.914364] ? page_fault_oops+0x99/0x1b0
[1667258.914372] ? kernelmode_fixup_or_oops.isra.0+0x69/0x90
[1667258.914380] ? __bad_area_nosemaphore+0x19e/0x2c0
[1667258.914388] ? bad_area_nosemaphore+0x16/0x30
[1667258.914394] ? do_kern_addr_fault+0x7b/0xa0
[1667258.914400] ? exc_page_fault+0x1a4/0x1b0
[1667258.914407] ? asm_exc_page_fault+0x27/0x30
[1667258.914417] ? memcpy_orig+0x105/0x130
[1667258.914425] ? lib_sha256_base_do_update.isra.0+0x5d/0x1d0 [sha256_ssse3]
[1667258.914433] ? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]
[1667258.914440] sha256_finup+0xf5/0x150 [sha256_ssse3]
[1667258.914447] sha256_avx2_digest+0x55/0x70 [sha256_ssse3]
[1667258.914453] crypto_shash_digest+0x2a/0x60
[1667258.914460] fw_log_firmware_info+0x113/0x1b0
[1667258.914469] _request_firmware+0x19d/0x4b0
[1667258.914476] firmware_request_nowarn+0x36/0x60
[1667258.914482] sahara_processing+0x399/0x710 [qaic]
[1667258.914501] process_one_work+0x181/0x3a0
[1667258.914508] worker_thread+0x306/0x440
[1667258.914514] ? _raw_spin_lock_irqsave+0xe/0x20
[1667258.914521] ? __pfx_worker_thread+0x10/0x10
[1667258.914526] kthread+0xef/0x120
[1667258.914533] ? __pfx_kthread+0x10/0x10
[1667258.914540] ret_from_fork+0x44/0x70
[1667258.914546] ? __pfx_kthread+0x10/0x10
[1667258.914552] ret_from_fork_asm+0x1b/0x30
[1667258.914561] </TASK>
[1667258.914564] Modules linked in: tls nfsv3 rpcsec_gss_krb5 nfsv4 nfs netfs snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore qrtr_mhi(OE) qrtr(OE) xt_conntrack xt_MASQUERADE bridge stp llc xt_set ip_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nf_tables xfrm_user xfrm_algo openafs(POE-) overlay cfg80211 binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common isst_if_common skx_edac skx_edac_common nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm cmdlinepart spi_nor irqbypass mtd qaic(OE) mei_me rapl intel_cstate i2c_i801 mhi(OE) spi_intel_pci mei switchtec(OE) ioatdma spi_intel i2c_smbus intel_pch_thermal dca ipmi_si acpi_power_meter acpi_ipmi ipmi_devintf ipmi_msghandler acpi_pad mac_hid sch_fq_codel dm_multipath nfsd msr parport_pc auth_rpcgss nfs_acl lockd ppdev grace lp parport sunrpc efi_pstore nfnetlink dmi_sysfs
[1667258.914665] ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel sha256_ssse3 bnxt_en sha1_ssse3 nvme_core xhci_pci nvme_auth xhci_pci_renesas wmi aesni_intel crypto_simd cryptd
[1667258.914741] CR2: ffffb731b3fbcd40
[1667258.914746] ---[ end trace 0000000000000000 ]---
[Fix]
Cherry-pick upstream commit:
70165dc3ec8c ("crypto: sha256 - fix crash at kexec")
[Test Plan]
* An x86_64 system with Ubuntu 24.04.4 LTS, Linux 6.8.0-101-generic x86_64 and Qualcomm AIC100 PCIe card installed
* Create a dummy file with size larger than 2GB and not divisible by 64, compress it using zstd, then replace it with any of the firmware files in /lib/firmware/qcom/aic100/
* Reset the AIC100 device to force reloading the firmware files by writing 1 to /sys/bus/mhi/devices/mhi0/soc_reset
[Where Problems Could Occur]
Any <v6.16 kernel entity that makes use of sha256_update()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146472/+subscriptions
[Bug 2138192] Re: Got call trace when plug in device/AC in type-c port(both TBT5/TBT4)
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138192
Title:
Got call trace when plug in device/AC in type-c port(both TBT5/TBT4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.17 source package in Questing:
Invalid
Bug description:
[Impact]
On systems with UCSI (USB Type-C Connector System Software Interface) version earlier than 2.1, the kernel generates warnings when handling USB Type-C connector changes. The kernel attempts to read power-related status bits that don't exist in older UCSI versions.
Error log:
[ 8.767836] Access to unsupported field at offset 0x59 (need version 0210)
[ 8.767891] WARNING: CPU: 10 PID: 133 at drivers/usb/typec/ucsi/ucsi.c:1419 ucsi_handle_connector_change+0x402/0x490 [typec_ucsi]
The code unconditionally checks the PWR_READING_READY_V2_1 bit in
connector status without verifying the UCSI version, leading to
accessing undefined bits on systems with UCSI versions older than 2.1.
This triggers a kernel warning every time a USB Type-C device is
connected or disconnected.
Affected hardware: Dell systems with USB Type-C ports using UCSI version < 2.1
Failure rate: 100% on affected hardware when USB Type-C devices are connected/disconnected
[Fix]
Add UCSI version check before reading power-related status bits. The "Power Reading" bit and associated fields were introduced in UCSI specification v2.1, so the code now limits the check for these bits only if the supported version is 2.1 or above.
Both patches are upstream in mainline kernel v6.18 and reviewed by
Intel maintainers.
Commit c851b71fd6cd ("usb: typec: ucsi: Add support for READ_POWER_LEVEL command")
- Adds support for UCSI v2.1 READ_POWER_LEVEL command to debugfs
- Exposes peak_current, avg_current, and vbus_voltage in debugfs
- Updates power values when READ_POWER_LEVEL command is sent or when device is connected
Commit 1bc28f015a19 ("usb: typec: ucsi: Add check for UCSI version")
- Fixes the above commit by adding version check
- Prevents accessing v2.1-specific bits on older UCSI versions
Links:
https://lore.kernel.org/r/20250814163028.18058-1-venkat.jayaraman@intel.com
https://lore.kernel.org/r/20250905184401.3222530-1-venkat.jayaraman@intel.com
[Test Plan]
On a system with UCSI version < 2.1:
1. Connect a USB Type-C device (e.g., USB-C to USB-A adapter, USB-C charger, or USB-C dock)
2. Check dmesg for kernel warnings related to UCSI:
$ dmesg | grep -E "Access to unsupported field|ucsi_handle_connector_change"
Without the patch: Kernel warning appears showing "Access to unsupported field at offset 0x59 (need version 0210)"
With the patch: No warnings, UCSI operates correctly on both v2.1 and earlier versions
[Where problems could occur]
The changes affect the USB Type-C UCSI driver, specifically the power reading functionality.
If the version check logic is incorrect, systems with UCSI v2.1 might
not read power levels even though they support the feature. This would
manifest as empty or stale values in the debugfs power reading files
(peak_current, avg_current, vbus_voltage) even when USB Type-C devices
are connected.
Conversely, if the version comparison is too strict, some systems with
v2.1 support might be incorrectly identified as older versions and
miss out on power reading capabilities.
The debugfs file creation could fail if there are issues with the file
operations structures, preventing users from accessing power readings
through debugfs, though this would only affect debugging functionality
and not normal USB Type-C operation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2138192/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138192
Title:
Got call trace when plug in device/AC in type-c port(both TBT5/TBT4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.17 source package in Questing:
Invalid
Bug description:
[Impact]
On systems with UCSI (USB Type-C Connector System Software Interface) version earlier than 2.1, the kernel generates warnings when handling USB Type-C connector changes. The kernel attempts to read power-related status bits that don't exist in older UCSI versions.
Error log:
[ 8.767836] Access to unsupported field at offset 0x59 (need version 0210)
[ 8.767891] WARNING: CPU: 10 PID: 133 at drivers/usb/typec/ucsi/ucsi.c:1419 ucsi_handle_connector_change+0x402/0x490 [typec_ucsi]
The code unconditionally checks the PWR_READING_READY_V2_1 bit in
connector status without verifying the UCSI version, leading to
accessing undefined bits on systems with UCSI versions older than 2.1.
This triggers a kernel warning every time a USB Type-C device is
connected or disconnected.
Affected hardware: Dell systems with USB Type-C ports using UCSI version < 2.1
Failure rate: 100% on affected hardware when USB Type-C devices are connected/disconnected
[Fix]
Add UCSI version check before reading power-related status bits. The "Power Reading" bit and associated fields were introduced in UCSI specification v2.1, so the code now limits the check for these bits only if the supported version is 2.1 or above.
Both patches are upstream in mainline kernel v6.18 and reviewed by
Intel maintainers.
Commit c851b71fd6cd ("usb: typec: ucsi: Add support for READ_POWER_LEVEL command")
- Adds support for UCSI v2.1 READ_POWER_LEVEL command to debugfs
- Exposes peak_current, avg_current, and vbus_voltage in debugfs
- Updates power values when READ_POWER_LEVEL command is sent or when device is connected
Commit 1bc28f015a19 ("usb: typec: ucsi: Add check for UCSI version")
- Fixes the above commit by adding version check
- Prevents accessing v2.1-specific bits on older UCSI versions
Links:
https://lore.kernel.org/r/20250814163028.18058-1-venkat.jayaraman@intel.com
https://lore.kernel.org/r/20250905184401.3222530-1-venkat.jayaraman@intel.com
[Test Plan]
On a system with UCSI version < 2.1:
1. Connect a USB Type-C device (e.g., USB-C to USB-A adapter, USB-C charger, or USB-C dock)
2. Check dmesg for kernel warnings related to UCSI:
$ dmesg | grep -E "Access to unsupported field|ucsi_handle_connector_change"
Without the patch: Kernel warning appears showing "Access to unsupported field at offset 0x59 (need version 0210)"
With the patch: No warnings, UCSI operates correctly on both v2.1 and earlier versions
[Where problems could occur]
The changes affect the USB Type-C UCSI driver, specifically the power reading functionality.
If the version check logic is incorrect, systems with UCSI v2.1 might
not read power levels even though they support the feature. This would
manifest as empty or stale values in the debugfs power reading files
(peak_current, avg_current, vbus_voltage) even when USB Type-C devices
are connected.
Conversely, if the version comparison is too strict, some systems with
v2.1 support might be incorrectly identified as older versions and
miss out on power reading capabilities.
The debugfs file creation could fail if there are issues with the file
operations structures, preventing users from accessing power readings
through debugfs, though this would only affect debugging functionality
and not normal USB Type-C operation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2138192/+subscriptions
[Bug 2138423] Re: [SRU] Fix the error during suspend on cs42l43
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138423
Title:
[SRU] Fix the error during suspend on cs42l43
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
The system fails to read IRQ status after suspend/resume on Lenovo systems, resulting in error -16 (EBUSY) in kernel logs:
cs42l43 sdw:0:0:01fa:4243:01: Failed to read IRQ status: -16
This error occurs during system suspend/resume cycles when IRQ
handlers attempt to access volatile registers on suspended hardware.
The race condition happens because the MFD driver disables IRQs upon
entering suspend, but IRQ handlers can run, claim a PM runtime
reference, get scheduled, and then try to access registers after the
device has been force suspended.
Affected hardware: Lenovo systems with Cirrus Logic cs42l43 audio codec
Failure rate: Occurs on every suspend/resume cycle
[Fix]
This series of 6 patches fixes the IRQ handling race condition during system suspend/resume by properly coordinating IRQ masking between the MFD driver and child drivers.
The patches are upstream in mainline kernel v6.18:
1. mfd: cs42l43: Move IRQ enable/disable to encompass force suspend (62aec8a0a5b6)
- Moves IRQ disabling to cover the whole forced suspend state to avoid race conditions
2. mfd: cs42l43: Remove IRQ masking in suspend (afe0f94992db)
- Removes IRQ masking from MFD code since individual child drivers now mask their own IRQs
3. ASoC: cs42l43: Rename system suspend callback and fix debug print (638ca7601f41)
- Clarifies that the function is a system suspend callback, not runtime suspend
4. ASoC: cs42l43: Store IRQ domain in codec private data (149dda5f42a8)
- Prepares for refactoring by storing IRQ domain pointer in private data
5. ASoC: cs42l43: Disable IRQs in system suspend (a69b4ba19a07)
- Masks IRQs and syncs work queues in the codec driver during system suspend
6. ASoC: cs42l43: Shutdown jack detection on suspend (dd7ae5b8b3c2)
- Fully powers down jack detection during system suspend
Already in questing :
- mfd: cs42l43: Move IRQ enable/disable to encompass force suspend (commit 62aec8a0a5b6)
Patches:
https://lore.kernel.org/lkml/20250903094549.271068-1-ckeepax@opensource.cirrus.com/
[Test Plan]
Suspend and resume the system 30 times using the command:
$ sudo rtcwake -m mem -s 20
Without the patches:
- The error "cs42l43 sdw:0:0:01fa:4243:01: Failed to read IRQ status: -16" appears in dmesg after each resume
- Check with: $ dmesg | grep "cs42l43.*IRQ.*-16"
With the patches:
- No IRQ status read errors in dmesg
- Verify with: $ dmesg | grep "cs42l43.*IRQ.*-16" (should return no results)
[Where problems could occur]
It may break the Cirrus Logic cs42l43 audio codec driver.
The patches are merged upstream in kernel v6.18.
The hardware is not supported by noble 6.8 kernel.
So SRU for questing and oem-6.17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2138423/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138423
Title:
[SRU] Fix the error during suspend on cs42l43
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
The system fails to read IRQ status after suspend/resume on Lenovo systems, resulting in error -16 (EBUSY) in kernel logs:
cs42l43 sdw:0:0:01fa:4243:01: Failed to read IRQ status: -16
This error occurs during system suspend/resume cycles when IRQ
handlers attempt to access volatile registers on suspended hardware.
The race condition happens because the MFD driver disables IRQs upon
entering suspend, but IRQ handlers can run, claim a PM runtime
reference, get scheduled, and then try to access registers after the
device has been force suspended.
Affected hardware: Lenovo systems with Cirrus Logic cs42l43 audio codec
Failure rate: Occurs on every suspend/resume cycle
[Fix]
This series of 6 patches fixes the IRQ handling race condition during system suspend/resume by properly coordinating IRQ masking between the MFD driver and child drivers.
The patches are upstream in mainline kernel v6.18:
1. mfd: cs42l43: Move IRQ enable/disable to encompass force suspend (62aec8a0a5b6)
- Moves IRQ disabling to cover the whole forced suspend state to avoid race conditions
2. mfd: cs42l43: Remove IRQ masking in suspend (afe0f94992db)
- Removes IRQ masking from MFD code since individual child drivers now mask their own IRQs
3. ASoC: cs42l43: Rename system suspend callback and fix debug print (638ca7601f41)
- Clarifies that the function is a system suspend callback, not runtime suspend
4. ASoC: cs42l43: Store IRQ domain in codec private data (149dda5f42a8)
- Prepares for refactoring by storing IRQ domain pointer in private data
5. ASoC: cs42l43: Disable IRQs in system suspend (a69b4ba19a07)
- Masks IRQs and syncs work queues in the codec driver during system suspend
6. ASoC: cs42l43: Shutdown jack detection on suspend (dd7ae5b8b3c2)
- Fully powers down jack detection during system suspend
Already in questing :
- mfd: cs42l43: Move IRQ enable/disable to encompass force suspend (commit 62aec8a0a5b6)
Patches:
https://lore.kernel.org/lkml/20250903094549.271068-1-ckeepax@opensource.cirrus.com/
[Test Plan]
Suspend and resume the system 30 times using the command:
$ sudo rtcwake -m mem -s 20
Without the patches:
- The error "cs42l43 sdw:0:0:01fa:4243:01: Failed to read IRQ status: -16" appears in dmesg after each resume
- Check with: $ dmesg | grep "cs42l43.*IRQ.*-16"
With the patches:
- No IRQ status read errors in dmesg
- Verify with: $ dmesg | grep "cs42l43.*IRQ.*-16" (should return no results)
[Where problems could occur]
It may break the Cirrus Logic cs42l43 audio codec driver.
The patches are merged upstream in kernel v6.18.
The hardware is not supported by noble 6.8 kernel.
So SRU for questing and oem-6.17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2138423/+subscriptions
[Bug 2141276] Re: efi: Fix swapped arguments to bsearch() in efi_status_to_*() SAUCE patch
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141276
Title:
efi: Fix swapped arguments to bsearch() in efi_status_to_*() SAUCE
patch
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Committed
Status in linux source package in Resolute:
Fix Released
Bug description:
[Impact]
The swapped bsearch() arguments cause the function to calculate incorrect
element offsets when searching the efi_error_codes array:
- Buggy behavior: bsearch thinks there are 24 elements of 12 bytes each
- Correct behavior: 12 elements of 24 bytes each (on 64-bit systems)
This causes efi_status_to_err() and efi_status_to_str() to read at wrong
memory offsets (every 12 bytes instead of every 24 bytes), potentially:
- Returning incorrect errno values for EFI status codes
- Returning wrong error description strings
- Failing to find valid status codes and returning default error values
These functions are used to translate EFI firmware error codes to Linux
errno values and human-readable strings, affecting error reporting for
EFI-related operations including secure boot and firmware variable access.
[Test Plan]
1. Build kernel with the fix applied
2. Boot system with UEFI firmware
3. Trigger EFI error conditions that exercise efi_status_to_err() and
efi_status_to_str(), such as:
- Secure boot signature verification failures
- EFI variable access errors
- MOK (Machine Owner Key) operations
4. Verify dmesg shows correct EFI error messages
5. Compare error messages before and after the fix to confirm correct
status code translation
Alternatively, a unit test can verify the bsearch returns correct results:
- Call efi_status_to_err() with known EFI status codes (e.g., EFI_SUCCESS,
EFI_INVALID_PARAMETER, EFI_SECURITY_VIOLATION)
- Verify correct errno values are returned (-EINVAL, -EACCES, etc.)
[Where problems could occur]
The fix swaps two adjacent function arguments. Potential issues:
1. The fix changes the search behavior, which could theoretically expose
latent bugs in code that was accidentally working due to the incorrect
search. For example, if code was relying on the -EINVAL fallback when
bsearch failed to find a match, it might now receive a different (correct)
errno value.
2. Since this affects EFI error reporting, any issues would manifest as
incorrect error messages in dmesg or wrong return values from EFI
operations. This could affect debugging but should not cause system
instability.
[Other Info]
- Root cause: The bug was introduced in the SAUCE patch cherry-picked from
kernel-ark commit 2ae9082db0b5:
https://gitlab.com/cki-project/kernel-ark/-/commit/2ae9082db0b5
- Upstream fix: https://gitlab.com/cki-project/kernel-ark/-/commit/49bcc48074ba
- bsearch(3) man page: https://man7.org/linux/man-pages/man3/bsearch.3.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141276/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141276
Title:
efi: Fix swapped arguments to bsearch() in efi_status_to_*() SAUCE
patch
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Committed
Status in linux source package in Resolute:
Fix Released
Bug description:
[Impact]
The swapped bsearch() arguments cause the function to calculate incorrect
element offsets when searching the efi_error_codes array:
- Buggy behavior: bsearch thinks there are 24 elements of 12 bytes each
- Correct behavior: 12 elements of 24 bytes each (on 64-bit systems)
This causes efi_status_to_err() and efi_status_to_str() to read at wrong
memory offsets (every 12 bytes instead of every 24 bytes), potentially:
- Returning incorrect errno values for EFI status codes
- Returning wrong error description strings
- Failing to find valid status codes and returning default error values
These functions are used to translate EFI firmware error codes to Linux
errno values and human-readable strings, affecting error reporting for
EFI-related operations including secure boot and firmware variable access.
[Test Plan]
1. Build kernel with the fix applied
2. Boot system with UEFI firmware
3. Trigger EFI error conditions that exercise efi_status_to_err() and
efi_status_to_str(), such as:
- Secure boot signature verification failures
- EFI variable access errors
- MOK (Machine Owner Key) operations
4. Verify dmesg shows correct EFI error messages
5. Compare error messages before and after the fix to confirm correct
status code translation
Alternatively, a unit test can verify the bsearch returns correct results:
- Call efi_status_to_err() with known EFI status codes (e.g., EFI_SUCCESS,
EFI_INVALID_PARAMETER, EFI_SECURITY_VIOLATION)
- Verify correct errno values are returned (-EINVAL, -EACCES, etc.)
[Where problems could occur]
The fix swaps two adjacent function arguments. Potential issues:
1. The fix changes the search behavior, which could theoretically expose
latent bugs in code that was accidentally working due to the incorrect
search. For example, if code was relying on the -EINVAL fallback when
bsearch failed to find a match, it might now receive a different (correct)
errno value.
2. Since this affects EFI error reporting, any issues would manifest as
incorrect error messages in dmesg or wrong return values from EFI
operations. This could affect debugging but should not cause system
instability.
[Other Info]
- Root cause: The bug was introduced in the SAUCE patch cherry-picked from
kernel-ark commit 2ae9082db0b5:
https://gitlab.com/cki-project/kernel-ark/-/commit/2ae9082db0b5
- Upstream fix: https://gitlab.com/cki-project/kernel-ark/-/commit/49bcc48074ba
- bsearch(3) man page: https://man7.org/linux/man-pages/man3/bsearch.3.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141276/+subscriptions
[Bug 2141377] Re: [SRU]Fix xe GPU suspend/resume crash on Battlemage
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141377
Title:
[SRU]Fix xe GPU suspend/resume crash on Battlemage
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[ Impact ]
Intel Battlemage xe GPU (8086:e212) crashes during system resume with
NULL pointer dereference in xe_guc_ads_populate_post_load(), making
suspend/resume non-functional on affected systems.
Root cause: Noble 6.17 kernels have commit 59cebf0bdff48 but are missing
its prerequisite commit 1313351e71181. Without proper forcewake handling,
MMIO register access causes hardware corruption.
[ Fix ]
Cherry-pick upstream commit from v6.18-rc1:
- 1313351e71181 ("drm/xe: make xe_gt_idle_disable_c6() handle the forcewake internally")
[ Test Plan ]
1. System: Lenovo ThinkStation P3 Ultra G2 with Battlemage dGPU (8086:e212)
2. Reproduce: rtcwake -m mem -s 10
3. Verify: System resumes successfully without crashes
[ Where problems could occur ]
It may break xe driver GT idle/power management, affects suspend/resume path. Commit is from mainline v6.18-rc1.
The dGPU is not fully certified on v6.8 kernel, so SRU for questing
and oem-6.17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2141377/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141377
Title:
[SRU]Fix xe GPU suspend/resume crash on Battlemage
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[ Impact ]
Intel Battlemage xe GPU (8086:e212) crashes during system resume with
NULL pointer dereference in xe_guc_ads_populate_post_load(), making
suspend/resume non-functional on affected systems.
Root cause: Noble 6.17 kernels have commit 59cebf0bdff48 but are missing
its prerequisite commit 1313351e71181. Without proper forcewake handling,
MMIO register access causes hardware corruption.
[ Fix ]
Cherry-pick upstream commit from v6.18-rc1:
- 1313351e71181 ("drm/xe: make xe_gt_idle_disable_c6() handle the forcewake internally")
[ Test Plan ]
1. System: Lenovo ThinkStation P3 Ultra G2 with Battlemage dGPU (8086:e212)
2. Reproduce: rtcwake -m mem -s 10
3. Verify: System resumes successfully without crashes
[ Where problems could occur ]
It may break xe driver GT idle/power management, affects suspend/resume path. Commit is from mainline v6.18-rc1.
The dGPU is not fully certified on v6.8 kernel, so SRU for questing
and oem-6.17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2141377/+subscriptions
[Bug 2143480] Re: Questing: Failed to query NVIDIA devices
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143480
Title:
Questing: Failed to query NVIDIA devices
Status in linux package in Ubuntu:
Fix Released
Bug description:
Nova modules are enabled for questing with the following patchset.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139960
Because of this we nvidia cards are not being recognized. We need to
disable nove_core module.
nvidia-persistenced[9541]: Started (9541)
nvidia-persistenced[9537]: nvidia-persistenced failed to initialize. Check syslog for more details.
nvidia-persistenced[9541]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 122 has read and write permissions for those files.
systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143480/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143480
Title:
Questing: Failed to query NVIDIA devices
Status in linux package in Ubuntu:
Fix Released
Bug description:
Nova modules are enabled for questing with the following patchset.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139960
Because of this we nvidia cards are not being recognized. We need to
disable nove_core module.
nvidia-persistenced[9541]: Started (9541)
nvidia-persistenced[9537]: nvidia-persistenced failed to initialize. Check syslog for more details.
nvidia-persistenced[9541]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 122 has read and write permissions for those files.
systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143480/+subscriptions
[Bug 2137613] Re: TBT call trace while connecting TBT4 monitor on TBT5 port
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137613
Title:
TBT call trace while connecting TBT4 monitor on TBT5 port
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
When connecting Thunderbolt devices (especially monitors like Dell
U2725QE), users see alarming kernel backtraces in dmesg during device
enumeration. While the devices eventually work after automatic
reconnection, the call traces cause user concern and can trigger
automated bug reporting tools.
Error log example:
```
[ 36.031530] thunderbolt 0000:c7:00.6: PCIe Down path activation failed
[ 36.031531] WARNING: drivers/thunderbolt/path.c:589 at 0x0, CPU#12: pool-/usr/libex/3145
[ 36.031605] CPU: 12 UID: 0 PID: 3145 Comm: pool-/usr/libex Tainted: G D W 6.18.0+ #8
[ 36.031610] RIP: 0010:tb_path_activate+0x126/0x530 [thunderbolt]
[ 36.031637] Call Trace:
[ 36.031638] <TASK>
...
```
The issue occurs when:
- Type-C connections have transient electrical issues
- During lane bonding transitions (single lane to dual lane)
- The Thunderbolt port's control channel is temporarily unavailable
The devices typically recover automatically within a few seconds and
work normally, but the kernel backtrace (tb_WARN) is generated
unnecessarily for these expected transient conditions.
Affected hardware:
- Dell U2725QE Thunderbolt monitor (USB4 device 8087:b26)
- Other Thunderbolt/USB4 devices experiencing similar transient connection issues
- AMD and Intel Thunderbolt controllers
[Fix]
Modify tb_path_activate() in drivers/thunderbolt/path.c to
differentiate between expected transient failures and actual errors:
- For -ENOTCONN errors: Use tb_warn() to log the error without generating a kernel backtrace
- For all other errors: Keep tb_WARN() to generate the full call trace for debugging
This approach aligns with the existing comment in
drivers/thunderbolt/ctl.c which states that
TB_CFG_ERROR_PORT_NOT_CONNECTED "can happen during surprise removal"
and we should "not warn" about it.
The fix does not suppress the warning message itself - users and
developers can still see the path activation failure in dmesg. It only
removes the unnecessary kernel backtrace (stack dump, register dump,
etc.) for this specific expected transient condition.
Patch:
https://lore.kernel.org/lkml/20260102031905.27416-1-acelan.kao@canonical.com/T/#u
("thunderbolt: Suppress call trace for transient -ENOTCONN errors
during path activation")
[Test Plan]
Hardware needed:
- Dell U2725QE Thunderbolt monitor or similar Thunderbolt device that exhibits transient connection issues
- System with Thunderbolt 3/4 or USB4 controller
Test steps:
```bash
# Clear dmesg
sudo dmesg -C
# Connect Dell U2725QE or similar Thunderbolt device
# Wait 10 seconds
# Check for call traces
dmesg | grep -A 30 "path activation failed"
```
Without the patch: A full kernel backtrace appears with WARNING, RIP,
Call Trace, register dump, etc.
With the patch: Only a simple warning message appears without the backtrace:
```
thunderbolt 0000:c7:00.6: PCIe Down path activation failed (port not connected)
```
[Where problems could occur]
The patch modifies error reporting in the Thunderbolt path activation
code, which could affect debugging and error handling:
1. **Thunderbolt subsystem**: If there are genuine bugs that manifest
as -ENOTCONN errors (not just transient issues), developers might miss
important debugging information because the full backtrace won't be
generated. This would make it harder to diagnose actual Thunderbolt
controller bugs or firmware issues.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2137613/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137613
Title:
TBT call trace while connecting TBT4 monitor on TBT5 port
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
When connecting Thunderbolt devices (especially monitors like Dell
U2725QE), users see alarming kernel backtraces in dmesg during device
enumeration. While the devices eventually work after automatic
reconnection, the call traces cause user concern and can trigger
automated bug reporting tools.
Error log example:
```
[ 36.031530] thunderbolt 0000:c7:00.6: PCIe Down path activation failed
[ 36.031531] WARNING: drivers/thunderbolt/path.c:589 at 0x0, CPU#12: pool-/usr/libex/3145
[ 36.031605] CPU: 12 UID: 0 PID: 3145 Comm: pool-/usr/libex Tainted: G D W 6.18.0+ #8
[ 36.031610] RIP: 0010:tb_path_activate+0x126/0x530 [thunderbolt]
[ 36.031637] Call Trace:
[ 36.031638] <TASK>
...
```
The issue occurs when:
- Type-C connections have transient electrical issues
- During lane bonding transitions (single lane to dual lane)
- The Thunderbolt port's control channel is temporarily unavailable
The devices typically recover automatically within a few seconds and
work normally, but the kernel backtrace (tb_WARN) is generated
unnecessarily for these expected transient conditions.
Affected hardware:
- Dell U2725QE Thunderbolt monitor (USB4 device 8087:b26)
- Other Thunderbolt/USB4 devices experiencing similar transient connection issues
- AMD and Intel Thunderbolt controllers
[Fix]
Modify tb_path_activate() in drivers/thunderbolt/path.c to
differentiate between expected transient failures and actual errors:
- For -ENOTCONN errors: Use tb_warn() to log the error without generating a kernel backtrace
- For all other errors: Keep tb_WARN() to generate the full call trace for debugging
This approach aligns with the existing comment in
drivers/thunderbolt/ctl.c which states that
TB_CFG_ERROR_PORT_NOT_CONNECTED "can happen during surprise removal"
and we should "not warn" about it.
The fix does not suppress the warning message itself - users and
developers can still see the path activation failure in dmesg. It only
removes the unnecessary kernel backtrace (stack dump, register dump,
etc.) for this specific expected transient condition.
Patch:
https://lore.kernel.org/lkml/20260102031905.27416-1-acelan.kao@canonical.com/T/#u
("thunderbolt: Suppress call trace for transient -ENOTCONN errors
during path activation")
[Test Plan]
Hardware needed:
- Dell U2725QE Thunderbolt monitor or similar Thunderbolt device that exhibits transient connection issues
- System with Thunderbolt 3/4 or USB4 controller
Test steps:
```bash
# Clear dmesg
sudo dmesg -C
# Connect Dell U2725QE or similar Thunderbolt device
# Wait 10 seconds
# Check for call traces
dmesg | grep -A 30 "path activation failed"
```
Without the patch: A full kernel backtrace appears with WARNING, RIP,
Call Trace, register dump, etc.
With the patch: Only a simple warning message appears without the backtrace:
```
thunderbolt 0000:c7:00.6: PCIe Down path activation failed (port not connected)
```
[Where problems could occur]
The patch modifies error reporting in the Thunderbolt path activation
code, which could affect debugging and error handling:
1. **Thunderbolt subsystem**: If there are genuine bugs that manifest
as -ENOTCONN errors (not just transient issues), developers might miss
important debugging information because the full backtrace won't be
generated. This would make it harder to diagnose actual Thunderbolt
controller bugs or firmware issues.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2137613/+subscriptions
[Bug 2137615] Re: [SRU] add pmc c6 support of Arrow Lake
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137615
Title:
[SRU] add pmc c6 support of Arrow Lake
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
The error is shown in dmesg:
kernel: intel_pmc_core INT33A1:00: pmc_core: couldn't get DMU telem endpoint -6
c6 status is not shown in debugfs.
[Fix]
Add Arrow Lake PMU GUIDs in pmc_core:
a32f7d76e3cd7 platform/x86:intel/pmc: Add DMU GUID to Arrow Lake U/H
3b603955f2423 platform/x86:intel/pmc: Add support for multiple DMU GUIDs
644ab3bc98ee3 platform/x86:intel/pmc: Update Arrow Lake telemetry GUID
[Test]
The pmc error is not shown in dmesg.
# cat /sys/kernel/debug/pmc_core/die_c6_us_show
16476381
[Where problems could occur]
It may break intel pmc support.
Noble 6.8 kernel got some conflicts and need many commits and revert.
So SRU for questing, oem-6.17 and resolute.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2137615/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137615
Title:
[SRU] add pmc c6 support of Arrow Lake
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
The error is shown in dmesg:
kernel: intel_pmc_core INT33A1:00: pmc_core: couldn't get DMU telem endpoint -6
c6 status is not shown in debugfs.
[Fix]
Add Arrow Lake PMU GUIDs in pmc_core:
a32f7d76e3cd7 platform/x86:intel/pmc: Add DMU GUID to Arrow Lake U/H
3b603955f2423 platform/x86:intel/pmc: Add support for multiple DMU GUIDs
644ab3bc98ee3 platform/x86:intel/pmc: Update Arrow Lake telemetry GUID
[Test]
The pmc error is not shown in dmesg.
# cat /sys/kernel/debug/pmc_core/die_c6_us_show
16476381
[Where problems could occur]
It may break intel pmc support.
Noble 6.8 kernel got some conflicts and need many commits and revert.
So SRU for questing, oem-6.17 and resolute.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2137615/+subscriptions
[Bug 2067642] Re: net:tap in ubuntu_kselftests_net fails on Noble (buffer overflow detected)
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2067642
Title:
net:tap in ubuntu_kselftests_net fails on Noble (buffer overflow
detected)
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Bug description:
The following issue has been found in net:tap in ubuntu_kselftests_net
on multiple noble kernels (including generic, realtime, and ibm):
8819 14:42:24 DEBUG| [stdout] TAP version 13
8820 14:42:24 DEBUG| [stdout] 1..1
8821 14:42:24 DEBUG| [stdout] # timeout set to 0
8822 14:42:24 DEBUG| [stdout] # selftests: net: tap
8823 14:42:24 DEBUG| [stdout] # TAP version 13
8824 14:42:24 DEBUG| [stdout] # 1..3
8825 14:42:24 DEBUG| [stdout] # # Starting 3 tests from 1 test cases.
8826 14:42:24 DEBUG| [stdout] # # RUN tap.test_packet_valid_udp_gso ...
8827 14:42:24 DEBUG| [stdout] # *** buffer overflow detected ***: terminated
8828 14:42:24 DEBUG| [stdout] # # test_packet_valid_udp_gso: Test terminated by assertion
8829 14:42:24 DEBUG| [stdout] # # FAIL tap.test_packet_valid_udp_gso
8830 14:42:24 DEBUG| [stdout] # not ok 1 tap.test_packet_valid_udp_gso
8831 14:42:24 DEBUG| [stdout] # # RUN tap.test_packet_valid_udp_csum ...
8832 14:42:24 DEBUG| [stdout] # *** buffer overflow detected ***: terminated
8833 14:42:25 DEBUG| [stdout] # # test_packet_valid_udp_csum: Test terminated by assertion
8834 14:42:25 DEBUG| [stdout] # # FAIL tap.test_packet_valid_udp_csum
8835 14:42:25 DEBUG| [stdout] # not ok 2 tap.test_packet_valid_udp_csum
8836 14:42:25 DEBUG| [stdout] # # RUN tap.test_packet_crash_tap_invalid_eth_proto ...
8837 14:42:25 DEBUG| [stdout] # *** buffer overflow detected ***: terminated
8838 14:42:25 DEBUG| [stdout] # # test_packet_crash_tap_invalid_eth_proto: Test terminated by assertion
8839 14:42:25 DEBUG| [stdout] # # FAIL tap.test_packet_crash_tap_invalid_eth_proto
8840 14:42:25 DEBUG| [stdout] # not ok 3 tap.test_packet_crash_tap_invalid_eth_proto
8841 14:42:25 DEBUG| [stdout] # # FAILED: 0 / 3 tests passed.
8842 14:42:25 DEBUG| [stdout] # # Totals: pass:0 fail:3 xfail:0 xpass:0 skip:0 error:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2067642/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2067642
Title:
net:tap in ubuntu_kselftests_net fails on Noble (buffer overflow
detected)
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Bug description:
The following issue has been found in net:tap in ubuntu_kselftests_net
on multiple noble kernels (including generic, realtime, and ibm):
8819 14:42:24 DEBUG| [stdout] TAP version 13
8820 14:42:24 DEBUG| [stdout] 1..1
8821 14:42:24 DEBUG| [stdout] # timeout set to 0
8822 14:42:24 DEBUG| [stdout] # selftests: net: tap
8823 14:42:24 DEBUG| [stdout] # TAP version 13
8824 14:42:24 DEBUG| [stdout] # 1..3
8825 14:42:24 DEBUG| [stdout] # # Starting 3 tests from 1 test cases.
8826 14:42:24 DEBUG| [stdout] # # RUN tap.test_packet_valid_udp_gso ...
8827 14:42:24 DEBUG| [stdout] # *** buffer overflow detected ***: terminated
8828 14:42:24 DEBUG| [stdout] # # test_packet_valid_udp_gso: Test terminated by assertion
8829 14:42:24 DEBUG| [stdout] # # FAIL tap.test_packet_valid_udp_gso
8830 14:42:24 DEBUG| [stdout] # not ok 1 tap.test_packet_valid_udp_gso
8831 14:42:24 DEBUG| [stdout] # # RUN tap.test_packet_valid_udp_csum ...
8832 14:42:24 DEBUG| [stdout] # *** buffer overflow detected ***: terminated
8833 14:42:25 DEBUG| [stdout] # # test_packet_valid_udp_csum: Test terminated by assertion
8834 14:42:25 DEBUG| [stdout] # # FAIL tap.test_packet_valid_udp_csum
8835 14:42:25 DEBUG| [stdout] # not ok 2 tap.test_packet_valid_udp_csum
8836 14:42:25 DEBUG| [stdout] # # RUN tap.test_packet_crash_tap_invalid_eth_proto ...
8837 14:42:25 DEBUG| [stdout] # *** buffer overflow detected ***: terminated
8838 14:42:25 DEBUG| [stdout] # # test_packet_crash_tap_invalid_eth_proto: Test terminated by assertion
8839 14:42:25 DEBUG| [stdout] # # FAIL tap.test_packet_crash_tap_invalid_eth_proto
8840 14:42:25 DEBUG| [stdout] # not ok 3 tap.test_packet_crash_tap_invalid_eth_proto
8841 14:42:25 DEBUG| [stdout] # # FAILED: 0 / 3 tests passed.
8842 14:42:25 DEBUG| [stdout] # # Totals: pass:0 fail:3 xfail:0 xpass:0 skip:0 error:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2067642/+subscriptions
[Bug 2116169] Re: Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel Panther Lake platforms
This bug is awaiting verification that the linux-intel/6.17.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116169
Title:
Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel
Panther Lake platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
Incomplete
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
Incomplete
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-firmware source package in Resolute:
Incomplete
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[ SRU Justification: kernel ]
[ Impact ]
Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.
Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.
[ Test Plan ]
1. Install kernels from proposed pocket:
```
$ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
```
At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.
2. Check dmesg for successful firmware loading:
```
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 438953 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 32278 usecs
Bluetooth: hci0: Waiting for device transition to d0
Bluetooth: hci0: Device moved to D0 in 47 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
Bluetooth: hci0: Fseq status: Success (0x00)
Bluetooth: hci0: Fseq executed: 00.98.00.08
Bluetooth: hci0: Fseq BT Top: 00.98.00.08
```
3. Check device availability:
```
$ btmgmt info
Index list with 1 item
hci0: Primary controller
addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
...
```
[ Where problems could occur ]
New hardware support on new platforms. No regression, but might have
stability problems.
[ Other Info ]
Intel Panther Lake is to be supported by 6.17+ kernels. Nominate
linux-oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.
========== original bug report ==========
* WhP2/SpP2 (ES2)
* Beta
* WiFi:
- iwlwifi-sc-a0-wh-a0.pnvm
- iwlwifi-sc-a0-wh-a0-99.ucode
* BT (IOSF):
- ibt-00a0-00a1-iml.sfi
- ibt-00a0-00a1-pci.ddc
- ibt-00a0-00a1-pci.sfi
* PV
* BT (IOSF):
- ibt-00a0-00a1-iml.sfi
- ibt-00a0-00a1-pci.ddc
- ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
* Beta
* WiFi:
- iwlwifi-sc-a0-wh-b0.pnvm
- iwlwifi-sc-a0-wh-b0-99.ucode
* PV
* WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
- iwlwifi-sc-a0-wh-b0.pnvm
- iwlwifi-sc-a0-wh-b0-101.ucode
* BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
- ibt-00a0-01a1-iml.sfi
- ibt-00a0-01a1-pci.ddc
- ibt-00a0-01a1-pci.sfi
* GfP2
* Beta
* WiFi:
- iwlwifi-sc-a0-gf-a0.pnvm
- iwlwifi-sc-a0-gf-a0-99.ucode
* BT (IOSF):
- ibt-00a0-0041-iml.sfi
- ibt-00a0-0041-pci.ddc
- ibt-00a0-0041-pci.sfi
* PV
* WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
- iwlwifi-sc-a0-gf-a0.pnvm
- iwlwifi-sc-a0-gf-a0-100.ucode
* BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
- ibt-00a0-0041-iml.sfi
- ibt-00a0-0041-pci.ddc
- ibt-00a0-0041-pci.sfi
* FmP2
* WiFi:
- iwlwifi-gl-c0-fm-c0-c102.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7, bug 2140975
- iwlwifi-sc-a0-fm-c0-c101.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c1564a6acf6d2b9ab7cbc64474a2c323, bug 2140975
* BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
- ibt-00a0-0291-iml.sfi
- ibt-00a0-0291-pci.sfi
- ibt-00a0-0291-pci.ddc
Device IDs
* BE211 (WhP2)
* PTL-P/U (H12X/H404)
* Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
* BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
* PTL-H (H484)
* Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
* BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
* PTL-P/U (H12X/H404)
* Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
* BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
* PTL-H (H484)
* Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
* BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
* PTL-P/U (H12X/H404)
* Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
* BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
* PTL-H (H484)
* Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
* BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
* BE201 (FmP2)
[Panther Lake]
* Whale Peak2
- WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
- BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}
* Scorpius Peak2
- WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
- BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}
* GfP2
- WiFi: iwlwifi-sc-a0-gf-a0
- BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116169/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116169
Title:
Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel
Panther Lake platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
Incomplete
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
Incomplete
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-firmware source package in Resolute:
Incomplete
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[ SRU Justification: kernel ]
[ Impact ]
Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.
Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.
[ Test Plan ]
1. Install kernels from proposed pocket:
```
$ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
```
At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.
2. Check dmesg for successful firmware loading:
```
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 438953 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 32278 usecs
Bluetooth: hci0: Waiting for device transition to d0
Bluetooth: hci0: Device moved to D0 in 47 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
Bluetooth: hci0: Fseq status: Success (0x00)
Bluetooth: hci0: Fseq executed: 00.98.00.08
Bluetooth: hci0: Fseq BT Top: 00.98.00.08
```
3. Check device availability:
```
$ btmgmt info
Index list with 1 item
hci0: Primary controller
addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
...
```
[ Where problems could occur ]
New hardware support on new platforms. No regression, but might have
stability problems.
[ Other Info ]
Intel Panther Lake is to be supported by 6.17+ kernels. Nominate
linux-oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.
========== original bug report ==========
* WhP2/SpP2 (ES2)
* Beta
* WiFi:
- iwlwifi-sc-a0-wh-a0.pnvm
- iwlwifi-sc-a0-wh-a0-99.ucode
* BT (IOSF):
- ibt-00a0-00a1-iml.sfi
- ibt-00a0-00a1-pci.ddc
- ibt-00a0-00a1-pci.sfi
* PV
* BT (IOSF):
- ibt-00a0-00a1-iml.sfi
- ibt-00a0-00a1-pci.ddc
- ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
* Beta
* WiFi:
- iwlwifi-sc-a0-wh-b0.pnvm
- iwlwifi-sc-a0-wh-b0-99.ucode
* PV
* WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
- iwlwifi-sc-a0-wh-b0.pnvm
- iwlwifi-sc-a0-wh-b0-101.ucode
* BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
- ibt-00a0-01a1-iml.sfi
- ibt-00a0-01a1-pci.ddc
- ibt-00a0-01a1-pci.sfi
* GfP2
* Beta
* WiFi:
- iwlwifi-sc-a0-gf-a0.pnvm
- iwlwifi-sc-a0-gf-a0-99.ucode
* BT (IOSF):
- ibt-00a0-0041-iml.sfi
- ibt-00a0-0041-pci.ddc
- ibt-00a0-0041-pci.sfi
* PV
* WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
- iwlwifi-sc-a0-gf-a0.pnvm
- iwlwifi-sc-a0-gf-a0-100.ucode
* BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
- ibt-00a0-0041-iml.sfi
- ibt-00a0-0041-pci.ddc
- ibt-00a0-0041-pci.sfi
* FmP2
* WiFi:
- iwlwifi-gl-c0-fm-c0-c102.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7, bug 2140975
- iwlwifi-sc-a0-fm-c0-c101.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c1564a6acf6d2b9ab7cbc64474a2c323, bug 2140975
* BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
- ibt-00a0-0291-iml.sfi
- ibt-00a0-0291-pci.sfi
- ibt-00a0-0291-pci.ddc
Device IDs
* BE211 (WhP2)
* PTL-P/U (H12X/H404)
* Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
* BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
* PTL-H (H484)
* Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
* BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
* PTL-P/U (H12X/H404)
* Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
* BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
* PTL-H (H484)
* Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
* BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
* PTL-P/U (H12X/H404)
* Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
* BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
* PTL-H (H484)
* Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
* BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
* BE201 (FmP2)
[Panther Lake]
* Whale Peak2
- WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
- BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}
* Scorpius Peak2
- WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
- BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}
* GfP2
- WiFi: iwlwifi-sc-a0-gf-a0
- BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116169/+subscriptions
Подписаться на:
Комментарии (Atom)