** Package changed: linux (Ubuntu) => opencryptoki (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: opencryptoki (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160205 Title: [26.10 FEAT] [SEC2560] openCryptoki CCA token: support PKCS #11 V3.2 ML-DSA Status in Ubuntu on IBM z Systems: New Status in opencryptoki package in Ubuntu: New Bug description: PKCS #11 v3.2 introduces mechanisms for ML-DSA. CCA token support for these mechanisms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2160205/+subscriptions
четверг
[Bug 2160200] [NEW] Fix no audio input/output device on Dell WCLSlate platform with CirrusLogic audio solution
Public bug reported: [Impact] Dell Slate WCL platform with CirrusLogic audio solution fail to register audio input/output device. [Fix] Fix the backport commits for IPC4 and SDCA functions from upstream [Test Case] 1. Boot up the machine of new Dell Slate WCL platforms with CirrusLogic audio solution 2. Go to g-s-d and select sound 3. Make sure the output and input device are not Dummy 4. Make sure audio input/output function works OK. [Where problems could occur] The new SDCA and IPC4 function needs to be backported for the Intel WCL platform. The risk of regression has to be addressed on Intel WCL platforms ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Resolute) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160200 Title: Fix no audio input/output device on Dell WCLSlate platform with CirrusLogic audio solution Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Dell Slate WCL platform with CirrusLogic audio solution fail to register audio input/output device. [Fix] Fix the backport commits for IPC4 and SDCA functions from upstream [Test Case] 1. Boot up the machine of new Dell Slate WCL platforms with CirrusLogic audio solution 2. Go to g-s-d and select sound 3. Make sure the output and input device are not Dummy 4. Make sure audio input/output function works OK. [Where problems could occur] The new SDCA and IPC4 function needs to be backported for the Intel WCL platform. The risk of regression has to be addressed on Intel WCL platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160200/+subscriptions
[Bug 2150769] Re: There is a conflict between the pc-kernel snap and additional firmware packages
To address the second half of the bug report, it seems that boot- managed-by-snapd should conflict with all linux-firmware-* packages or have some other mechanism to prevent users from inadvertently breaking their system, similarly to LP: #2096979 and LP: #2157702. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150769 Title: There is a conflict between the pc-kernel snap and additional firmware packages Status in canonical-kernel-snaps: Confirmed Status in boot-managed-by-snapd package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-firmware-intel-wireless package in Ubuntu: Invalid Bug description: I described in detail here, in case I miss anything in this description: https://discourse.ubuntu.com/t/the-pc-kernel-snap- on-26-04-prevents-users-from-installing-additional-firmware/81404 This bug report is pretty wordy so here's a top-line summary: 1. The pc-kernel snap uses an unfortunately unreliable method of including firmware, which means some firmware gets missed 2. The apt dependencies of `boot-managed-by-snapd` preclude installing `linux-firmware` but do not preclude installing any other firmware packages making it possible to break your system in a pretty dramatic way that many users might have a very difficult time figuring out or resolving. Reproduction steps: 1. Install Ubuntu using the `pc-kernel` snap rather than apt kernel packages 2. Install the `linux-firmware-intel-wireless` package Okay, now on to the verbose part of the bug report which I hope is at least partially understandable. Circumstance: 1. I'm running Ubuntu 26.04 using the pc-kernel snapo (because of hardware FDE I guess) 2. My laptop has a pretty new Arrow Lake chipset with an Intel wifi adapter 3. My wifi doesn't work What I discovered while debugging: the `iwlwifi` module won't load properly because it can't find the firmware file it wants, as it is not present in the `pc-kernel` snap, so wifi doesn't work. This took me in a few different directions and this is what I found: * Unspecified incompatibility between pc-kernel and additional firmware packages First, the pc-kernel snap creates symlinks to everything in its 'firmware' directory into the filesystem that gets mounted at /usr/lib/firmware, but it links everything at the top-level. That means firmware can be added to e.g. /usr/lib/firmware/somefile.fw, because that's a directory, but not /usr/lib/firmware/intel/somefile.fw because /usr/lib/firmware/intel is a symlink to a directory on the squashfs filesystem. This means that installing the `linux-firmware-intel-wireless` package, which has the firmware I need: 1. Breaks when trying to install because it tries to write some files to /usr/lib/firmware/intel/ 2. Refuses to uninstall until it's installed correctly, because dpkg recognizes it as being in an extremely broken state. I say 'unspecified' because `boot-managed-by-snapd` explicitly conflicts with `linux-firmware` (showing the intention to not allow both at once), but it does not conflict with any additional firmware packages. * Incomplete firmware inventory in the pc-kernel snap I dug into it a bit and found that the pc-kernel snap builds using the following steps: 1. Get the kernel and the modules together 2. Ask each module what firmware it wants (via `modinfo`) 3. Bundle those firmwares into the pc-kernel snap Unfortunately, for whatever reason, the `iwlwifi` firmware does not specify the firmware that my system seems to insist on, which is `bz-b0-fm-c0-c101.ucode`, so it does not get included into the pc- kernel snap. The `linux-firmware-intel-wireless` debian package *does* include this firmware, presumably because it just includes all available Intel wireless firmware unconditionally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dan 6392 F.... wireplumber /dev/snd/controlC1: dan 6392 F.... wireplumber /dev/snd/controlC0: dan 6392 F.... wireplumber /dev/snd/seq: dan 6354 F.... pipewire CasperMD5CheckMismatches: ./EFI/boot/bootx64.efi ./EFI/boot/grubx64.efi ./EFI/boot/mmx64.efi CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 10:29:41 2026 MachineType: Dell Inc. Dell Pro Max 14 Premium MA14250 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="us,pc105,," RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2025 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06XRHN dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/11/2025:br1.7:efr1.6:svnDellInc.:pnDellProMax14PremiumMA14250:pvr:rvnDellInc.:rn06XRHN:rvrA02:cvnDellInc.:ct10:cvr:sku0D32:pfaDellProMaxLaptops: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 Premium MA14250 dmi.product.sku: 0D32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2150769/+subscriptions
[Bug 2150769] Re: There is a conflict between the pc-kernel snap and additional firmware packages
** Also affects: boot-managed-by-snapd (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/2150769 Title: There is a conflict between the pc-kernel snap and additional firmware packages Status in canonical-kernel-snaps: Confirmed Status in boot-managed-by-snapd package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-firmware-intel-wireless package in Ubuntu: Invalid Bug description: I described in detail here, in case I miss anything in this description: https://discourse.ubuntu.com/t/the-pc-kernel-snap- on-26-04-prevents-users-from-installing-additional-firmware/81404 This bug report is pretty wordy so here's a top-line summary: 1. The pc-kernel snap uses an unfortunately unreliable method of including firmware, which means some firmware gets missed 2. The apt dependencies of `boot-managed-by-snapd` preclude installing `linux-firmware` but do not preclude installing any other firmware packages making it possible to break your system in a pretty dramatic way that many users might have a very difficult time figuring out or resolving. Reproduction steps: 1. Install Ubuntu using the `pc-kernel` snap rather than apt kernel packages 2. Install the `linux-firmware-intel-wireless` package Okay, now on to the verbose part of the bug report which I hope is at least partially understandable. Circumstance: 1. I'm running Ubuntu 26.04 using the pc-kernel snapo (because of hardware FDE I guess) 2. My laptop has a pretty new Arrow Lake chipset with an Intel wifi adapter 3. My wifi doesn't work What I discovered while debugging: the `iwlwifi` module won't load properly because it can't find the firmware file it wants, as it is not present in the `pc-kernel` snap, so wifi doesn't work. This took me in a few different directions and this is what I found: * Unspecified incompatibility between pc-kernel and additional firmware packages First, the pc-kernel snap creates symlinks to everything in its 'firmware' directory into the filesystem that gets mounted at /usr/lib/firmware, but it links everything at the top-level. That means firmware can be added to e.g. /usr/lib/firmware/somefile.fw, because that's a directory, but not /usr/lib/firmware/intel/somefile.fw because /usr/lib/firmware/intel is a symlink to a directory on the squashfs filesystem. This means that installing the `linux-firmware-intel-wireless` package, which has the firmware I need: 1. Breaks when trying to install because it tries to write some files to /usr/lib/firmware/intel/ 2. Refuses to uninstall until it's installed correctly, because dpkg recognizes it as being in an extremely broken state. I say 'unspecified' because `boot-managed-by-snapd` explicitly conflicts with `linux-firmware` (showing the intention to not allow both at once), but it does not conflict with any additional firmware packages. * Incomplete firmware inventory in the pc-kernel snap I dug into it a bit and found that the pc-kernel snap builds using the following steps: 1. Get the kernel and the modules together 2. Ask each module what firmware it wants (via `modinfo`) 3. Bundle those firmwares into the pc-kernel snap Unfortunately, for whatever reason, the `iwlwifi` firmware does not specify the firmware that my system seems to insist on, which is `bz-b0-fm-c0-c101.ucode`, so it does not get included into the pc- kernel snap. The `linux-firmware-intel-wireless` debian package *does* include this firmware, presumably because it just includes all available Intel wireless firmware unconditionally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dan 6392 F.... wireplumber /dev/snd/controlC1: dan 6392 F.... wireplumber /dev/snd/controlC0: dan 6392 F.... wireplumber /dev/snd/seq: dan 6354 F.... pipewire CasperMD5CheckMismatches: ./EFI/boot/bootx64.efi ./EFI/boot/grubx64.efi ./EFI/boot/mmx64.efi CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 10:29:41 2026 MachineType: Dell Inc. Dell Pro Max 14 Premium MA14250 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="us,pc105,," RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2025 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06XRHN dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/11/2025:br1.7:efr1.6:svnDellInc.:pnDellProMax14PremiumMA14250:pvr:rvnDellInc.:rn06XRHN:rvrA02:cvnDellInc.:ct10:cvr:sku0D32:pfaDellProMaxLaptops: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 Premium MA14250 dmi.product.sku: 0D32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2150769/+subscriptions
среда
[Bug 2150071] Re: ubuntu_bpf failed to build on Resolute (error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’)
Hints removed. Thanks! ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150071 Title: ubuntu_bpf failed to build on Resolute (error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Bug description: [Impact] ubuntu_bpf selftest fail to setup: '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: In file included from test_tag.c:18: /usr/include/linux/if_alg.h:45:22: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’ 45 | __u8 iv[] __counted_by(ivlen); | ^~~~~~~~~~~~ make[1]: *** [Makefile:244: [Fix] Apply the upstream fix present in v7.1-rc2: commit 0c7ae130698e70107430254e79fbe996b4d37ab5 Author: Paul Chaignon <paul.chaignon@gmail.com> Date: Sat May 2 12:12:40 2026 +0200 tools/headers: Regenerate stddef.h to fix BPF selftests With commit dacbfc167808 ("crypto: af_alg - Annotate struct af_alg_iv with __counted_by"), two selftests, test_tag and crypto_sanity, now indirectly rely on the __counted_by macro. On systems with commit dacbfc167808 in the installed UAPI headers, the selftests build fails with: In file included from tools/testing/selftests/bpf/prog_tests/crypto_sanity.c:7: /usr/include/linux/if_alg.h:45:22: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’ 45 | __u8 iv[] __counted_by(ivlen); | ^~~~~~~~~~~~ This patch fixes it by regenerating stddef.h in tools/include using the instructions from commit a778f5d46b62 ("tools/headers: Pull in stddef.h to uapi to fix BPF selftests build in CI"). [How to reproduce] Run the ubuntu_bpf test again after applying the patch. [Regression potential] Low: clean upstream cherry-pick for a known problem. --- Issue found on Openstack AMD64 instance with R/linux 7.0.0-14.14 Test build failed with: INSTALL /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helper_defs.h INSTALL libbpf_headers TEST-HDR [test_progs] tests.h EXT-OBJ [test_progs] testing_helpers.o EXT-OBJ [test_progs] cap_helpers.o EXT-OBJ [test_progs] unpriv_helpers.o BINARY test_verifier BINARY test_tag make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: In file included from test_tag.c:18: /usr/include/linux/if_alg.h:45:22: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’ 45 | __u8 iv[] __counted_by(ivlen); | ^~~~~~~~~~~~ make[1]: *** [Makefile:244: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_tag] Error 1 make: *** [Makefile:212: all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2150071/+subscriptions
[Bug 2154343] Re: ubuntu_bpf: FTBFS with clang 23 / gcc 15
Verified on a s390x Openstack VM with r/linux 7.0.0-28.28, I can see this issue does not exist anymore. Hint does not exist in our database. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: New => Invalid ** Tags removed: verification-needed-resolute-linux ** Tags added: verification-done-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154343 Title: ubuntu_bpf: FTBFS with clang 23 / gcc 15 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Bug description: [Impact] tools/testing/selftests/bpf/prog_tests/fexit_bpf2bpf.c:117:12: error: assigning to 'char *' from 'const char *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] [Fix] Apply the upstream fix: ``` commit ca0f39a369c5f927c3d004e63a5a778b08a9df94 Author: Varun R Mallya <varunrmallya@gmail.com> Date: Fri Mar 6 03:51:32 2026 +0530 selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c Building selftests with clang 23.0.0 (6fae863eba8a72cdd82f37e7111a46a70be525e0) triggers the following error: tools/testing/selftests/bpf/prog_tests/fexit_bpf2bpf.c:117:12: error: assigning to 'char *' from 'const char *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] The variable `tgt_name` is declared as `char *`, but it stores the result of strstr(prog_name[i], "/"). Since `prog_name[i]` is a `const char *`, the returned pointer should also be treated as const-qualified. Update `tgt_name` to `const char *` to match the type of the underlying string and silence the compiler warning. ``` [How to reproduce] Run test again after applying the patch [Regression potential] Low: clean upstream cherry-pick for a known issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2154343/+subscriptions
[Bug 2150071] Re: ubuntu_bpf failed to build on Resolute (error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’)
I can confirm with r/linux 7.0.0-28.28 the bpf build is not failing with this issue. ** Tags removed: verification-needed-resolute-linux ** Tags added: verification-done-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150071 Title: ubuntu_bpf failed to build on Resolute (error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: New Status in linux source package in Resolute: Fix Committed Bug description: [Impact] ubuntu_bpf selftest fail to setup: '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: In file included from test_tag.c:18: /usr/include/linux/if_alg.h:45:22: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’ 45 | __u8 iv[] __counted_by(ivlen); | ^~~~~~~~~~~~ make[1]: *** [Makefile:244: [Fix] Apply the upstream fix present in v7.1-rc2: commit 0c7ae130698e70107430254e79fbe996b4d37ab5 Author: Paul Chaignon <paul.chaignon@gmail.com> Date: Sat May 2 12:12:40 2026 +0200 tools/headers: Regenerate stddef.h to fix BPF selftests With commit dacbfc167808 ("crypto: af_alg - Annotate struct af_alg_iv with __counted_by"), two selftests, test_tag and crypto_sanity, now indirectly rely on the __counted_by macro. On systems with commit dacbfc167808 in the installed UAPI headers, the selftests build fails with: In file included from tools/testing/selftests/bpf/prog_tests/crypto_sanity.c:7: /usr/include/linux/if_alg.h:45:22: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’ 45 | __u8 iv[] __counted_by(ivlen); | ^~~~~~~~~~~~ This patch fixes it by regenerating stddef.h in tools/include using the instructions from commit a778f5d46b62 ("tools/headers: Pull in stddef.h to uapi to fix BPF selftests build in CI"). [How to reproduce] Run the ubuntu_bpf test again after applying the patch. [Regression potential] Low: clean upstream cherry-pick for a known problem. --- Issue found on Openstack AMD64 instance with R/linux 7.0.0-14.14 Test build failed with: INSTALL /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helper_defs.h INSTALL libbpf_headers TEST-HDR [test_progs] tests.h EXT-OBJ [test_progs] testing_helpers.o EXT-OBJ [test_progs] cap_helpers.o EXT-OBJ [test_progs] unpriv_helpers.o BINARY test_verifier BINARY test_tag make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: In file included from test_tag.c:18: /usr/include/linux/if_alg.h:45:22: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’ 45 | __u8 iv[] __counted_by(ivlen); | ^~~~~~~~~~~~ make[1]: *** [Makefile:244: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_tag] Error 1 make: *** [Makefile:212: all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2150071/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-vmware-6.17/6.17.0-1004.4)
All autopkgtests for the newly accepted linux-meta-vmware-6.17 (6.17.0-1004.4) for noble have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:5.0.3-2ubuntu7.2 (amd64) zfs-linux/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-meta-vmware-6.17 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2160114] Re: Intel IPU7 camera fails to initialize on Lunar Lake ThinkPad (SONY471A, -EEXIST, no /dev/video0)
Hi, for all the linux-main-modules-* packages, you have only linux-main-modules-zfs-7.0.0-27-generic. Please also install following packages and try again: * linux-main-modules-ipu6-7.0.0-27-generic * linux-main-modules-ipu7-7.0.0-27-generic * linux-main-modules-usbio-7.0.0-27-generic * linux-main-modules-vision-7.0.0-27-generic * linux-main-modules-v4l2loopback-7.0.0-27-generic And, you should also need HAL stack from https://launchpad.net/~oem-solutions-group/+archive/ubuntu/intel-ipu6 and https://launchpad.net/~oem-solutions-group/+archive/ubuntu/intel-ipu7 PPA: * gstreamer1.0-icamera * libcamhal-ipu7x * v4l2-relayd ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160114 Title: Intel IPU7 camera fails to initialize on Lunar Lake ThinkPad (SONY471A, -EEXIST, no /dev/video0) Status in linux package in Ubuntu: Incomplete Bug description: The integrated webcam is not detected on Ubuntu 26.04 LTS. Hardware: - Lenovo ThinkPad (Machine Type: 21Q6001FMX) - Intel Lunar Lake - Intel IPU7 - BIOS N4CET44W (1.20) Kernel: 7.0.0-27-generic Symptoms: - No /dev/video* devices are created. - Firefox and Microsoft Teams cannot detect a camera. Relevant kernel messages: Found supported sensor SONY471A:00 kobject_add_internal failed for SONY471A-0 with -EEXIST intel-ipu7: error -EEXIST: IPU bridge init failed intel-ipu7: probe with driver intel-ipu7 failed with error -17 refcount_t: addition on 0; use-after-free The IPU7 firmware loads successfully and the sensor is detected, but driver initialization fails before any video device is created. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: markuserlach 5209 F.... pipewire markuserlach 5231 F.... wireplumber /dev/snd/seq: markuserlach 5209 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 09:48:28 2026 InstallationDate: Installed on 2026-07-07 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21Q6001FMX ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux StagingDrivers: intel_ipu7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2026 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: N4CET44W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 21Q6001FMX dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN4CET44W(1.20):bd04/27/2026:br1.20:efr1.15:svnLENOVO:pn21Q6001FMX:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q6001FMX:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q6_BU_Think_FM_ThinkPadX9-15Gen1:pfaThinkPadX9-15Gen1: dmi.product.family: ThinkPad X9-15 Gen 1 dmi.product.name: 21Q6001FMX dmi.product.sku: LENOVO_MT_21Q6_BU_Think_FM_ThinkPad X9-15 Gen 1 dmi.product.version: ThinkPad X9-15 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160114/+subscriptions
[Bug 2160126] Re: Include the support for CX9 in Ubuntu 26.04.1
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160126 Title: Include the support for CX9 in Ubuntu 26.04.1 Status in linux package in Ubuntu: New Bug description: Include the support for CX9 Network controller in Ubuntu Server 26.04.1. In Dell 18G Intel and AMD platforms, CX9 is soldered on the motherboard itself. Here are the Device and Vendor ID details: VID DID SSVID SSID 0x15B3 0x1025 0x15B3 0x2788 CX9 Embedded 0x15B3 0x1025 0x15B3 0x3788 CX9 Switch Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160126/+subscriptions
[Bug 2159015] Re: HWE kernel 6.17: kauditd bypasses systemd-journald and floods virtual console with AppArmor denial records from snap-confined services, rendering virtual console unusable
Yes Michael, during the installation if we select these snap packages we are facing the issue. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159015 Title: HWE kernel 6.17: kauditd bypasses systemd-journald and floods virtual console with AppArmor denial records from snap-confined services, rendering virtual console unusable Status in linux package in Ubuntu: New Bug description: On Ubuntu 24.04.4 LTS with HWE kernel 6.17.0-35-generic, the kernel audit daemon (kauditd) bypasses systemd-journald and writes AppArmor denial records directly to the virtual console. This floods the console and makes it completely unusable. Steps to Reproduce: 1. Install Ubuntu 24.04.4 HWE on 17G platform with Nextcloud and Rocketchat-server snap packages installed. 2. Reboot the system. 3. Open the virtual console. Actual Result: Virtual console is flooded with continuous AppArmor denial messages from snap.rocketchat-server.rocketchat-mongo and snap.nextcloud.nextcloud-fixer. Login is not possible. Expected Result: Virtual console should be accessible and usable after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159015/+subscriptions
вторник
[Bug 2158236] Re: Fix amdgpu hang in amdgpu_ctx_mgr_entity_flush during exec
** Also 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/2158236 Title: Fix amdgpu hang in amdgpu_ctx_mgr_entity_flush during exec Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Fix Released Status in linux source package in Stonking: New Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Impact] System hangs on amdgpu during exec. systemd blocked for 368s in D state in amdgpu_ctx_mgr_entity_flush (mutex_lock) via filp_close -> amdgpu_flush during do_close_on_exec -> load_elf_binary. Reproduces on 6.17.0-1020-oem. kernel: INFO: task systemd:16426 blocked for more than 368 seconds. kernel: Tainted: G O 6.17.0-1020-oem #20-Ubuntu kernel: task:systemd state:D pid:16426 kernel: mutex_lock kernel: amdgpu_ctx_mgr_entity_flush+0x46/0x1f0 [amdgpu] kernel: amdgpu_flush+0x26/0x50 [amdgpu] kernel: filp_flush+0x6f/0xb0 kernel: filp_close+0x14/0x30 kernel: do_close_on_exec+0xe7/0x140 kernel: begin_new_exec+0x1ab/0x420 kernel: load_elf_binary+0x32d/0xf40 [Fix] Cherry-pick upstream commits: - b18fc0ab837381 "drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify" - 930595df251c "drm/amdgpu: remove check for BO reservation add assert instead" Pass NULL ticket to amdgpu_vm_handle_moved in move_notify so the clear=true path is used, avoiding a PT update while another process's job is still running — the contention that blocks amdgpu_ctx_mgr_entity_flush. [Test Plan] Boot oem-6.17 on dual-GPU AMD system without P2P PCI; glxgears on GPU0, Xorg on GPU1 sharing a dmabuf. Without fix: systemd hung >368s in amdgpu_ctx_mgr_entity_flush. With fix: no hang. [Where problems could occur] changes only the ticket arg in amdgpu_dma_buf_move_notify; normal VM update path untouched. Risk limited to dmabuf move-notify sync on multi-GPU shared-BO setups. It may break amdgpu driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2158236/+subscriptions
[Bug 2156858] Re: [SRU] Fix GPU throttling limits on Strix Halo
With 6.17.0-1029 OEM kernel, we’ve verified that under the same workload, Strix Halo systems no longer reboot unexpectedly. Mark this as verified. ** Tags removed: verification-needed-noble-linux-oem-6.17 ** Tags added: verification-done-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156858 Title: [SRU] Fix GPU throttling limits on Strix Halo Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2156858 [ Impact ] We found that setting power_dpm_force_performance_level to high and running heavy workload on Strix Halo platforms somehow makes it reboot. This is due to the throttling limits in amdgpu don't aligned with the power management firmware properly. [ Fix ] Cherry-pick the following commit: - 03b70e0d8aa26bab (drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range) which has been accepted since mainline v7.1 [ Test ] 1. Boot the kernel 2. Run the same compute workload on a Strix Halo system, and it shouldn't reboot. [ Where problems could occur ] If the driver throttles to aggressively this may impact performance, but this is safer than letting Strix Halo burn. [ Additional Information ] https://github.com/torvalds/linux/commit/03b70e0d8aa26bab89a0f1394c1c80a871925e42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156858/+subscriptions