понедельник

[Bug 2147400] Re: Remount ext4 to readonly with data=journal mode may dump call trace

** Summary changed: - Remount ext4 to readonly with data=journal mode could dump call trace + Remount ext4 to readonly with data=journal mode may dump call trace ** Description changed: [Impact] When journal is filled with some data and remount the filesystem to read-only in data=journal mode it may dump the following call trace: [ 71.629350] CPU: 0 UID: 0 PID: 177 Comm: kworker/u96:5 Tainted: G E 6.19.0-rc7 #1 PREEMPT(voluntary) [ 71.629352] Tainted: [E]=UNSIGNED_MODULE [ 71.629353] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022 [ 71.629354] Workqueue: writeback wb_workfn (flush-7:4) [ 71.629359] RIP: 0010:ext4_journal_check_start+0x8b/0xd0 [ 71.629360] Code: 31 ff 45 31 c0 45 31 c9 e9 42 ad c4 00 48 8b 5d f8 b8 fb ff ff ff c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 c3 cc cc cc cc <0f> 0b b8 e2 ff ff ff eb c2 0f 0b eb - a9 44 8b 42 08 68 c7 53 ce b8 +  a9 44 8b 42 08 68 c7 53 ce b8 [ 71.629361] RSP: 0018:ffffcf32c0fdf6a8 EFLAGS: 00010202 [ 71.629364] RAX: ffff8f08c8505000 RBX: ffff8f08c67ee800 RCX: 0000000000000000 [ 71.629366] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 71.629367] RBP: ffffcf32c0fdf6b0 R08: 0000000000000001 R09: 0000000000000000 [ 71.629368] R10: ffff8f08db18b3a8 R11: 0000000000000000 R12: 0000000000000000 [ 71.629368] R13: 0000000000000002 R14: 0000000000000a48 R15: ffff8f08c67ee800 [ 71.629369] FS: 0000000000000000(0000) GS:ffff8f0a7d273000(0000) knlGS:0000000000000000 [ 71.629370] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 71.629371] CR2: 00007b66825905cc CR3: 000000011053d004 CR4: 0000000000772ef0 [ 71.629374] PKRU: 55555554 [ 71.629374] Call Trace: [ 71.629378] <TASK> [ 71.629382] __ext4_journal_start_sb+0x38/0x1c0 [ 71.629383] mpage_prepare_extent_to_map+0x4af/0x580 [ 71.629389] ? sbitmap_get+0x73/0x180 [ 71.629399] ext4_do_writepages+0x3cc/0x10a0 [ 71.629400] ? kvm_sched_clock_read+0x11/0x20 [ 71.629409] ext4_writepages+0xc8/0x1b0 [ 71.629410] ? ext4_writepages+0xc8/0x1b0 [ 71.629411] do_writepages+0xc4/0x180 [ 71.629416] __writeback_single_inode+0x45/0x350 [ 71.629419] ? _raw_spin_unlock+0xe/0x40 [ 71.629423] writeback_sb_inodes+0x260/0x5c0 [ 71.629425] ? __schedule+0x4d1/0x1870 [ 71.629429] __writeback_inodes_wb+0x54/0x100 [ 71.629431] ? queue_io+0x82/0x140 [ 71.629433] wb_writeback+0x1ab/0x330 [ 71.629448] wb_workfn+0x31d/0x410 [ 71.629450] process_one_work+0x191/0x3e0 [ 71.629455] worker_thread+0x2e3/0x420 [Fix] This upstream commit fixes the issue: https://github.com/torvalds/linux/commit/f4a2b42e78914ff15630e71289adc589c3a8eb45 All the discussions are in this thread: https://lore.kernel.org/all/20260128074515.2028982-1-gerald.yang@canonical.com/ [Test Plan] This can be easily reproduced by the following script: mkdir -p mnt dd if=/dev/zero of=ext4disk bs=1G count=2 oflag=direct mkfs.ext4 ext4disk tune2fs -o journal_data ext4disk mount ext4disk mnt fio --name=fiotest --rw=randwrite --bs=4k --runtime=3 --ioengine=libaio --iodepth=128 --numjobs=4 --filename=mnt/fiotest --filesize=1G --group_reporting mount -o remount,ro ext4disk mnt sync [Where problems could occur] When the call trace happens, there is no data lost, all the dirty data has been flushed to file system before remounting. The fix is to make sure folio state is correct and update the xarray, so the writeback thread won't be trigger if there is no dirty data. - So if there is something really goes wrong, there still won't be data lost, even remount it to read-write mode. + So if there is something really goes wrong, there still won't be data lost, even remount it to read-write mode again. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147400 Title: Remount ext4 to readonly with data=journal mode may dump call trace Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux source package in Resolute: In Progress Bug description: [Impact] When journal is filled with some data and remount the filesystem to read-only in data=journal mode it may dump the following call trace: [ 71.629350] CPU: 0 UID: 0 PID: 177 Comm: kworker/u96:5 Tainted: G E 6.19.0-rc7 #1 PREEMPT(voluntary) [ 71.629352] Tainted: [E]=UNSIGNED_MODULE [ 71.629353] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022 [ 71.629354] Workqueue: writeback wb_workfn (flush-7:4) [ 71.629359] RIP: 0010:ext4_journal_check_start+0x8b/0xd0 [ 71.629360] Code: 31 ff 45 31 c0 45 31 c9 e9 42 ad c4 00 48 8b 5d f8 b8 fb ff ff ff c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 c3 cc cc cc cc <0f> 0b b8 e2 ff ff ff eb c2 0f 0b eb  a9 44 8b 42 08 68 c7 53 ce b8 [ 71.629361] RSP: 0018:ffffcf32c0fdf6a8 EFLAGS: 00010202 [ 71.629364] RAX: ffff8f08c8505000 RBX: ffff8f08c67ee800 RCX: 0000000000000000 [ 71.629366] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 71.629367] RBP: ffffcf32c0fdf6b0 R08: 0000000000000001 R09: 0000000000000000 [ 71.629368] R10: ffff8f08db18b3a8 R11: 0000000000000000 R12: 0000000000000000 [ 71.629368] R13: 0000000000000002 R14: 0000000000000a48 R15: ffff8f08c67ee800 [ 71.629369] FS: 0000000000000000(0000) GS:ffff8f0a7d273000(0000) knlGS:0000000000000000 [ 71.629370] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 71.629371] CR2: 00007b66825905cc CR3: 000000011053d004 CR4: 0000000000772ef0 [ 71.629374] PKRU: 55555554 [ 71.629374] Call Trace: [ 71.629378] <TASK> [ 71.629382] __ext4_journal_start_sb+0x38/0x1c0 [ 71.629383] mpage_prepare_extent_to_map+0x4af/0x580 [ 71.629389] ? sbitmap_get+0x73/0x180 [ 71.629399] ext4_do_writepages+0x3cc/0x10a0 [ 71.629400] ? kvm_sched_clock_read+0x11/0x20 [ 71.629409] ext4_writepages+0xc8/0x1b0 [ 71.629410] ? ext4_writepages+0xc8/0x1b0 [ 71.629411] do_writepages+0xc4/0x180 [ 71.629416] __writeback_single_inode+0x45/0x350 [ 71.629419] ? _raw_spin_unlock+0xe/0x40 [ 71.629423] writeback_sb_inodes+0x260/0x5c0 [ 71.629425] ? __schedule+0x4d1/0x1870 [ 71.629429] __writeback_inodes_wb+0x54/0x100 [ 71.629431] ? queue_io+0x82/0x140 [ 71.629433] wb_writeback+0x1ab/0x330 [ 71.629448] wb_workfn+0x31d/0x410 [ 71.629450] process_one_work+0x191/0x3e0 [ 71.629455] worker_thread+0x2e3/0x420 [Fix] This upstream commit fixes the issue: https://github.com/torvalds/linux/commit/f4a2b42e78914ff15630e71289adc589c3a8eb45 All the discussions are in this thread: https://lore.kernel.org/all/20260128074515.2028982-1-gerald.yang@canonical.com/ [Test Plan] This can be easily reproduced by the following script: mkdir -p mnt dd if=/dev/zero of=ext4disk bs=1G count=2 oflag=direct mkfs.ext4 ext4disk tune2fs -o journal_data ext4disk mount ext4disk mnt fio --name=fiotest --rw=randwrite --bs=4k --runtime=3 --ioengine=libaio --iodepth=128 --numjobs=4 --filename=mnt/fiotest --filesize=1G --group_reporting mount -o remount,ro ext4disk mnt sync [Where problems could occur] When the call trace happens, there is no data lost, all the dirty data has been flushed to file system before remounting. The fix is to make sure folio state is correct and update the xarray, so the writeback thread won't be trigger if there is no dirty data. So if there is something really goes wrong, there still won't be data lost, even remount it to read-write mode again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147400/+subscriptions

[Bug 2143301] Re: Enable new Intel WCL soundwire support

This bug was fixed in the package linux - 7.0.0-12.12 --------------- linux (7.0.0-12.12) resolute; urgency=medium * resolute/linux: 7.0.0-12.12 -proposed tracker (LP: #2146778) * Packaging resync (LP: #1786013) - [Packaging] update variants * linux-generic does not run scripts in /usr/share/kernel/*.d (LP: #2147005) - [Packaging] templates: Use consistent indentation - [Packaging] templates: Run scripts in /usr/share/kernel/*.d too * RISC-V kernel config is out of sync with other archs (LP: #1981437) - [Config] riscv64: Enable COUNTER=m - [Config] riscv64: Use GENDWARFKSYMS like other architectures * unconfined profile denies userns_create for chromium based processes (LP: #1990064) - [Config] disable CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS * FFe: add network interface mediation to 26.04 (LP: #2144679) - SAUCE: apparmor5.0.0 [57/57]: apparmor: add the ability to use interface in network mediation. * Jellyfin Desktop Flatpak doesn't work with the current AppArmor profile (LP: #2142956) - SAUCE: apparmor5.0.0 [29/57]: apparmor: fix fine grained inet mediation sock_file_perm - SAUCE: apparmor5.0.0 [30/57]: apparmor-next 7.1: aapparmor: use target task's context in apparmor_getprocattr() - SAUCE: apparmor5.0.0 [31/57]: apparmor-next 7.1: apparmor: return error on namespace mismatch in verify_header - SAUCE: apparmor5.0.0 [32/57]: apparmor-next 7.1: apparmor: enable differential encoding - SAUCE: apparmor5.0.0 [33/57]: apparmor-next 7.1: apparmor: propagate -ENOMEM correctly in unpack_table - SAUCE: apparmor5.0.0 [34/57]: apparmor-next 7.1: apparmor: Replace memcpy + NUL termination with kmemdup_nul in do_setattr - SAUCE: apparmor5.0.0 [35/57]: apparmor-next 7.1: apparmor: Remove redundant if check in sk_peer_get_label - SAUCE: apparmor5.0.0 [36/57]: apparmor-next 7.1: apparmor: use __label_make_stale in __aa_proxy_redirect - SAUCE: apparmor5.0.0 [37/57]: apparmor-next 7.1: apparmor: fix net.h and policy.h circular include pattern - SAUCE: apparmor5.0.0 [39/57]: apparmor-next 7.1: apparmor: make include headers self-contained - SAUCE: apparmor5.0.0 [40/57]: apparmor-next 7.1: apparmor: Use sysfs_emit in param_get_{audit,mode} - SAUCE: apparmor5.0.0 [41/57]: apparmor-next 7.1: apparmor: fix rawdata_f_data implicit flex array - SAUCE: apparmor5.0.0 [42/57]: apparmor-next 7.1: apparmor: free rawdata as soon as possible - SAUCE: apparmor5.0.0 [43/57]: apparmor-next 7.1: apparmor: Initial support for compressed policies - SAUCE: apparmor5.0.0 [44/57]: apparmor-next 7.1: apparmor: fix potential UAF in aa_replace_profiles - SAUCE: apparmor5.0.0 [45/57]: apparmor-next 7.1: apparmor: hide unused get_loaddata_common_ref() function - SAUCE: apparmor5.0.0 [46/57]: apparmor-next 7.1: apparmor: Fix string overrun due to missing termination - SAUCE: apparmor5.0.0 [47/57]: apparmor: fix packed tag on v5 header struct - SAUCE: apparmor5.0.0 [48/57]: apparmor: add temporal caching to audit responses. - SAUCE: apparmor5.0.0 [49/57]: apparmor: change fn_label_build() call to not return NULL - SAUCE: apparmor5.0.0 [50/57]: apparmor: make fn_label_build() capable of handling not supported - SAUCE: apparmor5.0.0 [51/57]: apparmor: move netfilter functions next to the LSM network operations - SAUCE: apparmor5.0.0 [52/57]: apparmor: move sock_rvc_skb() next to inet_conn_request - SAUCE: apparmor5.0.0 [53/57]: apparmor: fix af_unix local addr mediation binding - SAUCE: apparmor5.0.0 [54/57]: cleanups of apparmor af_unix mediation - SAUCE: apparmor5.0.0 [55/57]: apparmor: fix apparmor_secmark_check() when !inet and secmark defined. - SAUCE: apparmor5.0.0 [56/57]: apparmor: fix auditing of non-mediation falures * snap service cannot change apparmor hat (LP: #2139664) // Jellyfin Desktop Flatpak doesn't work with the current AppArmor profile (LP: #2142956) - SAUCE: apparmor5.0.0 [38/57]: apparmor-next 7.1: apparmor: grab ns lock and refresh when looking up changehat child profiles * AppArmor blocks write(2) to network sockets with Linux 6.19 (LP: #2141298) - SAUCE: apparmor5.0.0 [28/57]: apparmor: fix aa_label_sk_perm to check for RULE_MEDIATES_NET * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor5.0.0 [1/57]: Stacking: LSM: Single calls in secid hooks - SAUCE: apparmor5.0.0 [2/57]: Stacking: LSM: Exclusive secmark usage - SAUCE: apparmor5.0.0 [3/57]: Stacking: AppArmor: Remove the exclusive flag - SAUCE: apparmor5.0.0 [4/57]: Revert "apparmor: fix dbus permission queries to v9 ABI" - SAUCE: apparmor5.0.0 [5/57]: Revert "apparmor: gate make fine grained unix mediation behind v9 abi" - SAUCE: apparmor5.0.0 [6/57]: apparmor: net: patch to provide compatibility with v2.x net rules - SAUCE: apparmor5.0.0 [7/57]: apparmor: net: add fine grained ipv4/ipv6 mediation - SAUCE: apparmor5.0.0 [8/57]: apparmor: lift compatibility check out of profile_af_perm - SAUCE: apparmor5.0.0 [9/57]: apparmor: userns: add unprivileged user ns mediation - SAUCE: apparmor5.0.0 [10/57]: apparmor: userns: Add sysctls for additional controls of unpriv userns restrictions - SAUCE: apparmor5.0.0 [12/57]: apparmor: userns: open userns related sysctl so lxc can check if restriction are in place - SAUCE: apparmor5.0.0 [13/57]: apparmor: userns: allow profile to be transitioned when a userns is created - SAUCE: apparmor5.0.0 [14/57]: apparmor: mqueue: call security_inode_init_security on inode creation - SAUCE: apparmor5.0.0 [15/57]: apparmor: mqueue: add fine grained mediation of posix mqueues - SAUCE: apparmor5.0.0 [16/57]: apparmor: uring: add io_uring mediation - SAUCE: apparmor5.0.0 [19/57]: apparmor: prompt: setup slab cache for audit data - SAUCE: apparmor5.0.0 [20/57]: apparmor: prompt: add the ability for profiles to have a learning cache - SAUCE: apparmor5.0.0 [21/57]: apparmor: prompt: enable userspace upcall for mediation - SAUCE: apparmor5.0.0 [22/57]: apparmor: prompt: pass prompt boolean through into path_name as well - SAUCE: apparmor5.0.0 [23/57]: apparmor: check for supported version in notification messages. - SAUCE: apparmor5.0.0 [24/57]: apparmor: refactor building notice so it is easier to extend - SAUCE: apparmor5.0.0 [25/57]: apparmor: switch from ENOTSUPP to EPROTONOSUPPORT - SAUCE: apparmor5.0.0 [26/57]: apparmor: add support for meta data tags - SAUCE: apparmor5.0.0 [27/57]: apparmor: prevent profile->disconnected double free in aa_free_profile * update apparmor and LSM stacking patch set (LP: #2028253) // Installation of AppArmor on a 6.14 kernel produces error message "Illegal number: yes" (LP: #2102680) - SAUCE: apparmor5.0.0 [17/57]: apparmor: create an AA_SFS_TYPE_BOOLEAN_INTPRINT sysctl variant - SAUCE: apparmor5.0.0 [18/57]: apparmor: Use AA_SFS_FILE_BOOLEAN_INTPRINT for userns and io_uring sysctls * update apparmor and LSM stacking patch set (LP: #2028253) // [FFe] apparmor-4.0.0-alpha2 for unprivileged user namespace restrictions in mantic (LP: #2032602) - SAUCE: apparmor5.0.0 [11/57]: apparmor: userns - make it so special unconfined profiles can mediate user namespaces * Enable new Intel WCL soundwire support (LP: #2143301) - ASoC: sdw_utils: Add CS42L43B codec info - ASoC: dt-bindings: cirrus, cs42l43: Add CS42L43B variant - mfd: cs42l43: Add support for the B variant - ASoC: cs42l43: Add support for the B variant * Enable audio functions on Dell Huracan/Renegade platforms w/o built-in microphone (LP: #2143902) - ASoC: SDCA: Add default value for mipi-sdca-function-reset-max-delay - ASoC: SDCA: Update counting of SU/GE DAPM routes - ASoC: SDCA: Improve mapping of Q7.8 SDCA volumes - ASoC: SDCA: Pull the Q7.8 volume helpers out of soc-ops - ASoC: add snd_soc_lookup_component_by_name helper - ASoC: soc_sdw_utils: partial match the codec name - ASoC: soc_sdw_utils: remove index from sdca codec name * [SRU] MIPI camera is not working after upgrading to 6.17-oem (LP: #2145171) - SAUCE: ACPI: respect items already in honor_dep before skipping * linux-tools: consider linking perf against LLVM (LP: #2138328) - [Packaging] Actually enable llvm for perf * Pull patch in qla2xxx to Resolute (LP: #2144856) - scsi: qla2xxx: Add support to report MPI FW state * Ubuntu Resolute Desktop image arm64 - Boot on SC8280XP stalls with gpi-dma errors (LP: #2142403) - Revert "arm64: dts: qcom: sc8280xp: Enable GPI DMA" * 26.04 Snapdragon X Elite: Sync concept kernel changes (LP: #2144643) - SAUCE: arm64: dts: add missing denali-oled.dtb to Makefile - SAUCE: dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema - SAUCE: phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add simple-mfd compatible - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add optional PHY handle definitions - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add support for combo- mode endpoints - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Describe iommu entries - SAUCE: media: qcom: camss: Add legacy_phy flag to SoC definition structures - SAUCE: media: qcom: camss: Add support for PHY API devices - SAUCE: media: qcom: camss: Drop legacy PHY descriptions from x1e - SAUCE: arm64: dts: qcom: x1e80100: Add CAMCC block definition - SAUCE: arm64: dts: qcom: x1e80100: Add CCI definitions - SAUCE: arm64: dts: qcom: x1e80100: Add CAMSS block definition - SAUCE: arm64: dts: qcom: x1e80100-crd: Add pm8010 CRD pmic,id=m regulators - SAUCE: arm64: dts: qcom: x1e80100-crd: Add ov08x40 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add pm8010 camera PMIC with voltage levels for IR and RGB camera - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add on ov02c10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add pm8010 camera PMIC with voltage levels for IR and RGB camera - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add l7b_2p8 voltage regulator for RGB camera - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add ov02c10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-dell-inspiron14-7441: Switch on CAMSS RGB sensor - SAUCE: arm64: dts: qcom: x1-asus-zenbook-a14: Add on OV02C10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: add camera support - SAUCE: arm64: dts: qcom: x1e78100-t14s: enable camera privacy indicator - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: enable camera privacy indicator - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: enable camera privacy indicator - SAUCE: dt-bindings: arm: qcom: Add ASUS Vivobook X1P42100 variant - SAUCE: arm64: dts: qcom: x1-vivobook-s15: create a common dtsi for Hamoa and Purwa variants - SAUCE: arm64: dts: qcom: x1-vivobook-s15: add Purwa-compatible device tree - SAUCE: firmware: qcom: scm: allow QSEECOM on ASUS Vivobook X1P42100 variant - SAUCE: arm64: dts: qcom: hamoa: Move PCIe PERST and Wake GPIOs to port nodes - SAUCE: arm64: dts: qcom: x1e-acer-swift-14: Move PCIe PERST and Wake GPIOs to port nodes * 25.10 Snapdragon X Elite: Sync concept kernel changes (LP: #2121477) - SAUCE: wip: arm64: dts: qcom: x1e78100-t14s: enable bluetooth * Miscellaneous Ubuntu changes - SAUCE: dt-bindings: arm: qcom: Document HP EliteBook 6 G1q - SAUCE: firmware: qcom: scm: Allow QSEECOM for HP EliteBook 6 G1q - SAUCE: arm64: dts: qcom: x1p42100-hp-elitebook-6-g1q: DT for HP EliteBook 6 G1q - [Config] PHY_QCOM_MIPI_CSI2=m - SAUCE: arm64: dts: x1e80100-lenovo-yoga-slim7x: Fix RGB camera supplies - [Config] toolchain version update - Update Changes.md after v7.0-rc5 rebase - [Packaging] update Ubuntu.md - [Config] enable SECURITY_APPARMOR_PACKET_MEDIATION_ENABLED - [Packaging] Add linux-main-modules-zfs to linux-modules depends * Miscellaneous upstream changes - Revert "UBUNTU: SAUCE: Add Bluetooth support for the Lenovo Yoga Slim 7x" -- Timo Aaltonen <timo.aaltonen@canonical.com> Thu, 02 Apr 2026 11:50:22 +0300 ** Changed in: linux (Ubuntu Resolute) Status: New => 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/2143301 Title: Enable new Intel WCL soundwire support Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in firmware-sof source package in Noble: Fix Committed Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in firmware-sof source package in Questing: Fix Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: Invalid Status in firmware-sof source package in Resolute: Fix Released Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] New Dell Slate-1-Piece and Congo platform powered by Intel WildcatLake will have no basic audio functions w/o new firmware-sof which has the new DSP firmware and TPLG files ================ kernel ============================== Realtek on WCL: (Congo WCL) https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/sound/soc/codecs/rt722-sdca.c?id=a27539810e1e61efcfdeb51777ed875dc61e9d49 [git.kernel.org] CirrusLogic on WCL: (Slate-1-Piece WCL) https://lore.kernel.org/linux-sound/aYMpbnzi%2FUTO5Fqs@opensource.cirrus.com/T/#t <=============== firmware-sof ======================== [Fix] c78aea2df366275fed6c7b090bae3575951de57f Add 2.14.1 signed firmware binaries for Intel MTL+ targets f3e02da867b54e6061190d7ff1549e4f00bba17c Add 2.14.1 firmware binaries for Intel MTL and newer targets cdd3c8f9dd879a51dc8ed3c9aa0b7b0a49c108d8 Add 2.14 tools and topology binaries for Intel MTL and newer targets 11fc822288122b83296e634e8508f483c289d565 v2.14.x: add topologies for v2.14.2 e65a0d4f3ffceaf8a01df7f519707ffaf69746ef v2.14.x: add topologies for v2.14.3 [Test Case] 1. Boot up the machine of new Dell Intel WCL Congo and Slate-1-Piece platform powered by Intel WCL 2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices 3. Click test icon for basic audio output functions 4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions. 5. Test on machines of Intel ARL/LNL/MTL/PTL platforms for possible regression [Where problems could occur] Per comment from Intel, the primary requirement is that the topology file (sof-ptl-foo.tplg) and DSP firmware (sof-ptl.ri) are a pair and need to be from the same major version. If we upgrade of FW for only a single generation (e.g. only for WCL) This will be problematic. The main problem is that you may have two platforms (let’s say PTL and ARL) using same topology files. If you update FW for only PTL, you should also update the topology files used by PTL (FW+tplg always a pair!), but then if one of the topology files is used by some ARL products you may have problems (-> scenario 2 problem on ARL then). So we need to upgrade the DSP FW and the TPLG both for all MTL+ platforms (include ARL/LNL/MTL/PTL/WCL) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2143301/+subscriptions

[Bug 2144856] Re: Pull patch in qla2xxx to Resolute

This bug was fixed in the package linux - 7.0.0-12.12 --------------- linux (7.0.0-12.12) resolute; urgency=medium * resolute/linux: 7.0.0-12.12 -proposed tracker (LP: #2146778) * Packaging resync (LP: #1786013) - [Packaging] update variants * linux-generic does not run scripts in /usr/share/kernel/*.d (LP: #2147005) - [Packaging] templates: Use consistent indentation - [Packaging] templates: Run scripts in /usr/share/kernel/*.d too * RISC-V kernel config is out of sync with other archs (LP: #1981437) - [Config] riscv64: Enable COUNTER=m - [Config] riscv64: Use GENDWARFKSYMS like other architectures * unconfined profile denies userns_create for chromium based processes (LP: #1990064) - [Config] disable CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS * FFe: add network interface mediation to 26.04 (LP: #2144679) - SAUCE: apparmor5.0.0 [57/57]: apparmor: add the ability to use interface in network mediation. * Jellyfin Desktop Flatpak doesn't work with the current AppArmor profile (LP: #2142956) - SAUCE: apparmor5.0.0 [29/57]: apparmor: fix fine grained inet mediation sock_file_perm - SAUCE: apparmor5.0.0 [30/57]: apparmor-next 7.1: aapparmor: use target task's context in apparmor_getprocattr() - SAUCE: apparmor5.0.0 [31/57]: apparmor-next 7.1: apparmor: return error on namespace mismatch in verify_header - SAUCE: apparmor5.0.0 [32/57]: apparmor-next 7.1: apparmor: enable differential encoding - SAUCE: apparmor5.0.0 [33/57]: apparmor-next 7.1: apparmor: propagate -ENOMEM correctly in unpack_table - SAUCE: apparmor5.0.0 [34/57]: apparmor-next 7.1: apparmor: Replace memcpy + NUL termination with kmemdup_nul in do_setattr - SAUCE: apparmor5.0.0 [35/57]: apparmor-next 7.1: apparmor: Remove redundant if check in sk_peer_get_label - SAUCE: apparmor5.0.0 [36/57]: apparmor-next 7.1: apparmor: use __label_make_stale in __aa_proxy_redirect - SAUCE: apparmor5.0.0 [37/57]: apparmor-next 7.1: apparmor: fix net.h and policy.h circular include pattern - SAUCE: apparmor5.0.0 [39/57]: apparmor-next 7.1: apparmor: make include headers self-contained - SAUCE: apparmor5.0.0 [40/57]: apparmor-next 7.1: apparmor: Use sysfs_emit in param_get_{audit,mode} - SAUCE: apparmor5.0.0 [41/57]: apparmor-next 7.1: apparmor: fix rawdata_f_data implicit flex array - SAUCE: apparmor5.0.0 [42/57]: apparmor-next 7.1: apparmor: free rawdata as soon as possible - SAUCE: apparmor5.0.0 [43/57]: apparmor-next 7.1: apparmor: Initial support for compressed policies - SAUCE: apparmor5.0.0 [44/57]: apparmor-next 7.1: apparmor: fix potential UAF in aa_replace_profiles - SAUCE: apparmor5.0.0 [45/57]: apparmor-next 7.1: apparmor: hide unused get_loaddata_common_ref() function - SAUCE: apparmor5.0.0 [46/57]: apparmor-next 7.1: apparmor: Fix string overrun due to missing termination - SAUCE: apparmor5.0.0 [47/57]: apparmor: fix packed tag on v5 header struct - SAUCE: apparmor5.0.0 [48/57]: apparmor: add temporal caching to audit responses. - SAUCE: apparmor5.0.0 [49/57]: apparmor: change fn_label_build() call to not return NULL - SAUCE: apparmor5.0.0 [50/57]: apparmor: make fn_label_build() capable of handling not supported - SAUCE: apparmor5.0.0 [51/57]: apparmor: move netfilter functions next to the LSM network operations - SAUCE: apparmor5.0.0 [52/57]: apparmor: move sock_rvc_skb() next to inet_conn_request - SAUCE: apparmor5.0.0 [53/57]: apparmor: fix af_unix local addr mediation binding - SAUCE: apparmor5.0.0 [54/57]: cleanups of apparmor af_unix mediation - SAUCE: apparmor5.0.0 [55/57]: apparmor: fix apparmor_secmark_check() when !inet and secmark defined. - SAUCE: apparmor5.0.0 [56/57]: apparmor: fix auditing of non-mediation falures * snap service cannot change apparmor hat (LP: #2139664) // Jellyfin Desktop Flatpak doesn't work with the current AppArmor profile (LP: #2142956) - SAUCE: apparmor5.0.0 [38/57]: apparmor-next 7.1: apparmor: grab ns lock and refresh when looking up changehat child profiles * AppArmor blocks write(2) to network sockets with Linux 6.19 (LP: #2141298) - SAUCE: apparmor5.0.0 [28/57]: apparmor: fix aa_label_sk_perm to check for RULE_MEDIATES_NET * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor5.0.0 [1/57]: Stacking: LSM: Single calls in secid hooks - SAUCE: apparmor5.0.0 [2/57]: Stacking: LSM: Exclusive secmark usage - SAUCE: apparmor5.0.0 [3/57]: Stacking: AppArmor: Remove the exclusive flag - SAUCE: apparmor5.0.0 [4/57]: Revert "apparmor: fix dbus permission queries to v9 ABI" - SAUCE: apparmor5.0.0 [5/57]: Revert "apparmor: gate make fine grained unix mediation behind v9 abi" - SAUCE: apparmor5.0.0 [6/57]: apparmor: net: patch to provide compatibility with v2.x net rules - SAUCE: apparmor5.0.0 [7/57]: apparmor: net: add fine grained ipv4/ipv6 mediation - SAUCE: apparmor5.0.0 [8/57]: apparmor: lift compatibility check out of profile_af_perm - SAUCE: apparmor5.0.0 [9/57]: apparmor: userns: add unprivileged user ns mediation - SAUCE: apparmor5.0.0 [10/57]: apparmor: userns: Add sysctls for additional controls of unpriv userns restrictions - SAUCE: apparmor5.0.0 [12/57]: apparmor: userns: open userns related sysctl so lxc can check if restriction are in place - SAUCE: apparmor5.0.0 [13/57]: apparmor: userns: allow profile to be transitioned when a userns is created - SAUCE: apparmor5.0.0 [14/57]: apparmor: mqueue: call security_inode_init_security on inode creation - SAUCE: apparmor5.0.0 [15/57]: apparmor: mqueue: add fine grained mediation of posix mqueues - SAUCE: apparmor5.0.0 [16/57]: apparmor: uring: add io_uring mediation - SAUCE: apparmor5.0.0 [19/57]: apparmor: prompt: setup slab cache for audit data - SAUCE: apparmor5.0.0 [20/57]: apparmor: prompt: add the ability for profiles to have a learning cache - SAUCE: apparmor5.0.0 [21/57]: apparmor: prompt: enable userspace upcall for mediation - SAUCE: apparmor5.0.0 [22/57]: apparmor: prompt: pass prompt boolean through into path_name as well - SAUCE: apparmor5.0.0 [23/57]: apparmor: check for supported version in notification messages. - SAUCE: apparmor5.0.0 [24/57]: apparmor: refactor building notice so it is easier to extend - SAUCE: apparmor5.0.0 [25/57]: apparmor: switch from ENOTSUPP to EPROTONOSUPPORT - SAUCE: apparmor5.0.0 [26/57]: apparmor: add support for meta data tags - SAUCE: apparmor5.0.0 [27/57]: apparmor: prevent profile->disconnected double free in aa_free_profile * update apparmor and LSM stacking patch set (LP: #2028253) // Installation of AppArmor on a 6.14 kernel produces error message "Illegal number: yes" (LP: #2102680) - SAUCE: apparmor5.0.0 [17/57]: apparmor: create an AA_SFS_TYPE_BOOLEAN_INTPRINT sysctl variant - SAUCE: apparmor5.0.0 [18/57]: apparmor: Use AA_SFS_FILE_BOOLEAN_INTPRINT for userns and io_uring sysctls * update apparmor and LSM stacking patch set (LP: #2028253) // [FFe] apparmor-4.0.0-alpha2 for unprivileged user namespace restrictions in mantic (LP: #2032602) - SAUCE: apparmor5.0.0 [11/57]: apparmor: userns - make it so special unconfined profiles can mediate user namespaces * Enable new Intel WCL soundwire support (LP: #2143301) - ASoC: sdw_utils: Add CS42L43B codec info - ASoC: dt-bindings: cirrus, cs42l43: Add CS42L43B variant - mfd: cs42l43: Add support for the B variant - ASoC: cs42l43: Add support for the B variant * Enable audio functions on Dell Huracan/Renegade platforms w/o built-in microphone (LP: #2143902) - ASoC: SDCA: Add default value for mipi-sdca-function-reset-max-delay - ASoC: SDCA: Update counting of SU/GE DAPM routes - ASoC: SDCA: Improve mapping of Q7.8 SDCA volumes - ASoC: SDCA: Pull the Q7.8 volume helpers out of soc-ops - ASoC: add snd_soc_lookup_component_by_name helper - ASoC: soc_sdw_utils: partial match the codec name - ASoC: soc_sdw_utils: remove index from sdca codec name * [SRU] MIPI camera is not working after upgrading to 6.17-oem (LP: #2145171) - SAUCE: ACPI: respect items already in honor_dep before skipping * linux-tools: consider linking perf against LLVM (LP: #2138328) - [Packaging] Actually enable llvm for perf * Pull patch in qla2xxx to Resolute (LP: #2144856) - scsi: qla2xxx: Add support to report MPI FW state * Ubuntu Resolute Desktop image arm64 - Boot on SC8280XP stalls with gpi-dma errors (LP: #2142403) - Revert "arm64: dts: qcom: sc8280xp: Enable GPI DMA" * 26.04 Snapdragon X Elite: Sync concept kernel changes (LP: #2144643) - SAUCE: arm64: dts: add missing denali-oled.dtb to Makefile - SAUCE: dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema - SAUCE: phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add simple-mfd compatible - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add optional PHY handle definitions - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add support for combo- mode endpoints - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Describe iommu entries - SAUCE: media: qcom: camss: Add legacy_phy flag to SoC definition structures - SAUCE: media: qcom: camss: Add support for PHY API devices - SAUCE: media: qcom: camss: Drop legacy PHY descriptions from x1e - SAUCE: arm64: dts: qcom: x1e80100: Add CAMCC block definition - SAUCE: arm64: dts: qcom: x1e80100: Add CCI definitions - SAUCE: arm64: dts: qcom: x1e80100: Add CAMSS block definition - SAUCE: arm64: dts: qcom: x1e80100-crd: Add pm8010 CRD pmic,id=m regulators - SAUCE: arm64: dts: qcom: x1e80100-crd: Add ov08x40 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add pm8010 camera PMIC with voltage levels for IR and RGB camera - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add on ov02c10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add pm8010 camera PMIC with voltage levels for IR and RGB camera - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add l7b_2p8 voltage regulator for RGB camera - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add ov02c10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-dell-inspiron14-7441: Switch on CAMSS RGB sensor - SAUCE: arm64: dts: qcom: x1-asus-zenbook-a14: Add on OV02C10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: add camera support - SAUCE: arm64: dts: qcom: x1e78100-t14s: enable camera privacy indicator - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: enable camera privacy indicator - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: enable camera privacy indicator - SAUCE: dt-bindings: arm: qcom: Add ASUS Vivobook X1P42100 variant - SAUCE: arm64: dts: qcom: x1-vivobook-s15: create a common dtsi for Hamoa and Purwa variants - SAUCE: arm64: dts: qcom: x1-vivobook-s15: add Purwa-compatible device tree - SAUCE: firmware: qcom: scm: allow QSEECOM on ASUS Vivobook X1P42100 variant - SAUCE: arm64: dts: qcom: hamoa: Move PCIe PERST and Wake GPIOs to port nodes - SAUCE: arm64: dts: qcom: x1e-acer-swift-14: Move PCIe PERST and Wake GPIOs to port nodes * 25.10 Snapdragon X Elite: Sync concept kernel changes (LP: #2121477) - SAUCE: wip: arm64: dts: qcom: x1e78100-t14s: enable bluetooth * Miscellaneous Ubuntu changes - SAUCE: dt-bindings: arm: qcom: Document HP EliteBook 6 G1q - SAUCE: firmware: qcom: scm: Allow QSEECOM for HP EliteBook 6 G1q - SAUCE: arm64: dts: qcom: x1p42100-hp-elitebook-6-g1q: DT for HP EliteBook 6 G1q - [Config] PHY_QCOM_MIPI_CSI2=m - SAUCE: arm64: dts: x1e80100-lenovo-yoga-slim7x: Fix RGB camera supplies - [Config] toolchain version update - Update Changes.md after v7.0-rc5 rebase - [Packaging] update Ubuntu.md - [Config] enable SECURITY_APPARMOR_PACKET_MEDIATION_ENABLED - [Packaging] Add linux-main-modules-zfs to linux-modules depends * Miscellaneous upstream changes - Revert "UBUNTU: SAUCE: Add Bluetooth support for the Lenovo Yoga Slim 7x" -- Timo Aaltonen <timo.aaltonen@canonical.com> Thu, 02 Apr 2026 11:50:22 +0300 ** Changed in: linux (Ubuntu Resolute) Status: Fix Committed => 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/2144856 Title: Pull patch in qla2xxx to Resolute Status in linux package in Ubuntu: Fix Released Status in linux source package in Resolute: Fix Released Bug description: A silicon partner has asked to have the following patch pulled into Resolute: commit 0e124af675ebabddacfeb0958abd443265dddf13 Author: Nilesh Javali <njavali@marvell.com> Date: Thu Mar 5 15:03:37 2026 +0530 scsi: qla2xxx: Add support to report MPI FW state MPI firmware state was returned as 0. Get MPI FW state to proceed with flash image validation. A new sysfs node 'mpi_fw_state' is added to report MPI firmware state: /sys/class/scsi_host/hostXX/mpi_fw_state Fixes: d74181ca110e ("scsi: qla2xxx: Add bsg interface to support firmware img validation") Signed-off-by: Nilesh Javali <njavali@marvell.com> Link: https://patch.msgid.link/20260305093337.2007205-1-njavali@marvell.com Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> MKP has accepted this upstream in 7.1/scsi-staging (https://marc.info/?l=linux-scsi&m=177362836812818&w=2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144856/+subscriptions

[Bug 2139584] Re: mpi3mr: Features and Bug Fixes

Hi Timo, can we get the Git repo access for 26.04? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2139584 Title: mpi3mr: Features and Bug Fixes Status in linux package in Ubuntu: Fix Released Status in linux source package in Resolute: Fix Released Bug description: mpi3mr driver Upstream commits which should we included in Ubuntu 26.04 - 943e9049e84a scsi: mpi3mr: Driver version update to 8.17.0.3.50 - 8612d94348f4 scsi: mpi3mr: Fixed the W=1 compilation warning - ec54b348f274 scsi: mpi3mr: Record and report controller firmware faults - d0654335d900 scsi: mpi3mr: Update MPI Headers to revision 39 - c273c14b0294 scsi: mpi3mr: Use negotiated link rate from DevicePage0 - 7a67d9262288 scsi: mpi3mr: Avoid redundant diag-fault resets - d0d19250ed81 scsi: mpi3mr: Rename log data save helper to reflect threaded/BH context - 24de8b1d243b scsi: mpi3mr: Add module parameter to control threaded IRQ polling - 0db3f51839fe scsi: Change the return type of the .queuecommand() callback - 8d0aecdebc0f scsi: mpi3mr: Simplify the workqueue allocation code- - - 4588e65cfd66 scsi: mpi3mr: Prevent duplicate SAS/SATA device entries in channel 1 Below Test cases I have covered: - Driver load/unload - Virtual drives creation (R0, R1) and Deletion - Running FIO + Controller Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139584/+subscriptions

[Bug 2147342] Re: No audio on ASUS Zenbook S14 UX5406AA (Panther Lake) — sof_sdw fails to create DAI links for cs35l56

** Description changed: - I have no audio output (aside from Bluetooth) on my ASUS Zenbook S14 - UX5406AA with Intel Core Ultra 9 386H (Panther Lake), running + I have no audio output (aside from Bluetooth) on my ASUS Zenbook S14 + UX5406AA with Intel Core Ultra 9 386H (Panther Lake), running Ubuntu 26.04 LTS Beta with kernel 7.0.0-10-generic. All the audio hardware appears to enumerate correctly over SoundWire: - cs42l43 codec on link 3 (probed, devid 0x042a43 rev a1) - 4x cs35l56 SmartAmp on links 1+2 (all probed, fw 3.4.4) - rt722 on link 3 - SOF firmware boots successfully (v2.13.0.1) - However, when the topology file loads + However, when the topology file loads (sof-ptl-cs42l43-agg-l3-cs35l56-l2.tplg), it fails: - sof-audio-pci-intel-ptl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1 - sof-audio-pci-intel-ptl 0000:00:1f.3: error: can't find BE for DAI alh-copier.Playback-SmartAmp.1 - sof-audio-pci-intel-ptl 0000:00:1f.3: tplg sof-ptl-cs42l43-agg-l3-cs35l56-l2.tplg component load failed -22 - sof_sdw sof_sdw: probe with driver sof_sdw failed with error -22 +   sof-audio-pci-intel-ptl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1 +   sof-audio-pci-intel-ptl 0000:00:1f.3: error: can't find BE for DAI alh-copier.Playback-SmartAmp.1 +   sof-audio-pci-intel-ptl 0000:00:1f.3: tplg sof-ptl-cs42l43-agg-l3-cs35l56-l2.tplg component load failed -22 +   sof_sdw sof_sdw: probe with driver sof_sdw failed with error -22 cat /proc/asound/cards shows: --- no soundcards --- - I'm not sure whether this is caused by the topology ABI mismatch - (3:29 vs 3:23) or by the sof_sdw machine driver missing DAI link - definitions for this Panther Lake codec configuration. I tried - downgrading SOF firmware to v2.13 and v2.12 releases but all - available PTL topology files have ABI 3:29:1, so I couldn't test + I'm not sure whether this is caused by the topology ABI mismatch + (3:29 vs 3:23) or by the sof_sdw machine driver missing DAI link + definitions for this Panther Lake codec configuration. I tried + downgrading SOF firmware to v2.13 and v2.12 releases but all + available PTL topology files have ABI 3:29:1, so I couldn't test with a matching ABI. SoundWire devices visible: - sdw:0:1:01fa:3556:01:2 (cs35l56) - sdw:0:1:01fa:3556:01:3 (cs35l56) - sdw:0:2:01fa:3556:01:0 (cs35l56) - sdw:0:2:01fa:3556:01:1 (cs35l56) - sdw:0:3:01fa:4243:01 (cs42l43) - sdw:0:3:025d:0722:01 (rt722) +   sdw:0:1:01fa:3556:01:2 (cs35l56) +   sdw:0:1:01fa:3556:01:3 (cs35l56) +   sdw:0:2:01fa:3556:01:0 (cs35l56) +   sdw:0:2:01fa:3556:01:1 (cs35l56) +   sdw:0:3:01fa:4243:01 (cs42l43) +   sdw:0:3:025d:0722:01 (rt722) System info: - Laptop: ASUS Zenbook S14 UX5406AA - CPU: Intel Core Ultra 9 386H (Panther Lake) - OS: Ubuntu 26.04 LTS Beta - Kernel: 7.0.0-10-generic - firmware-sof-signed: 2025.12.2-1 - BIOS: UX5406AA.300 12/18/2025 - Hardware probe: https://linux-hardware.org/?probe=34cbba0446 +   Laptop: ASUS Zenbook S14 UX5406AA +   CPU: Intel Core Ultra 9 386H (Panther Lake) +   OS: Ubuntu 26.04 LTS Beta +   Kernel: 7.0.0-10-generic +   firmware-sof-signed: 2025.12.2-1 +   BIOS: UX5406AA.300 12/18/2025 +   Hardware probe: https://linux-hardware.org/?probe=34cbba0446 + + Also filed at sof: https://github.com/thesofproject/linux/issues/5721 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147342 Title: No audio on ASUS Zenbook S14 UX5406AA (Panther Lake) — sof_sdw fails to create DAI links for cs35l56 Status in linux package in Ubuntu: New Bug description: I have no audio output (aside from Bluetooth) on my ASUS Zenbook S14 UX5406AA with Intel Core Ultra 9 386H (Panther Lake), running Ubuntu 26.04 LTS Beta with kernel 7.0.0-10-generic. All the audio hardware appears to enumerate correctly over SoundWire: - cs42l43 codec on link 3 (probed, devid 0x042a43 rev a1) - 4x cs35l56 SmartAmp on links 1+2 (all probed, fw 3.4.4) - rt722 on link 3 - SOF firmware boots successfully (v2.13.0.1) However, when the topology file loads (sof-ptl-cs42l43-agg-l3-cs35l56-l2.tplg), it fails:   sof-audio-pci-intel-ptl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1   sof-audio-pci-intel-ptl 0000:00:1f.3: error: can't find BE for DAI alh-copier.Playback-SmartAmp.1   sof-audio-pci-intel-ptl 0000:00:1f.3: tplg sof-ptl-cs42l43-agg-l3-cs35l56-l2.tplg component load failed -22   sof_sdw sof_sdw: probe with driver sof_sdw failed with error -22 cat /proc/asound/cards shows: --- no soundcards --- I'm not sure whether this is caused by the topology ABI mismatch (3:29 vs 3:23) or by the sof_sdw machine driver missing DAI link definitions for this Panther Lake codec configuration. I tried downgrading SOF firmware to v2.13 and v2.12 releases but all available PTL topology files have ABI 3:29:1, so I couldn't test with a matching ABI. SoundWire devices visible:   sdw:0:1:01fa:3556:01:2 (cs35l56)   sdw:0:1:01fa:3556:01:3 (cs35l56)   sdw:0:2:01fa:3556:01:0 (cs35l56)   sdw:0:2:01fa:3556:01:1 (cs35l56)   sdw:0:3:01fa:4243:01 (cs42l43)   sdw:0:3:025d:0722:01 (rt722) System info:   Laptop: ASUS Zenbook S14 UX5406AA   CPU: Intel Core Ultra 9 386H (Panther Lake)   OS: Ubuntu 26.04 LTS Beta   Kernel: 7.0.0-10-generic   firmware-sof-signed: 2025.12.2-1   BIOS: UX5406AA.300 12/18/2025   Hardware probe: https://linux-hardware.org/?probe=34cbba0446 Also filed at sof: https://github.com/thesofproject/linux/issues/5721 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147342/+subscriptions

[Bug 2147374] [NEW] BUG: kernel NULL pointer dereference when starting VM inside a container

Public bug reported: With a 24.04 machine (physical or VM), it's possible to trigger a kernel NULL pointer dereference when running with the 6.17 HWE kernel. Here is the PoC: ``` cat << EOF > poc.sh #!/bin/bash set -eux # VM inside container causes a kernel NULL pointer dereference on 6.17 if [[ "$(uname -r)" =~ ^6\.17\.0 ]]; then   echo "::warning:: 6.17 kernel detected, expect failure then check 'dmesg'" else   echo "::info:: 6.17 kernel NOT detected, expect success and consider switching to 'linux-image-generic-hwe-24.04'" fi snap install lxd --channel latest/edge lxd init --auto # prepare ctn to be used for nested VM testing lxc init ubuntu-minimal-daily:24.04 ctn -c security.devlxd.images=true -c security.nesting=true -s default lxc config device add ctn kvm unix-char source=/dev/kvm lxc config device add ctn vhost-net unix-char source=/dev/vhost-net lxc config device add ctn vhost-vsock unix-char source=/dev/vhost-vsock lxc config device add ctn vsock unix-char source=/dev/vsock lxc start ctn sleep 30 lxc exec ctn -- snap wait system seed.loaded lxc exec ctn -- snap install lxd --channel latest/edge lxc exec ctn -- lxd init --auto # launch small nested VM lxc exec ctn -- lxc launch ubuntu-minimal-daily:24.04 nested-vm --vm -c limits.memory=512MiB -d root,size=3584MiB # cleanup lxc delete -f ctn EOF ``` Running the PoC will look like this: ``` # bash ./poc.sh ... + lxc exec ctn -- lxd init --auto + lxc exec ctn -- lxc launch ubuntu-minimal-daily:24.04 nested-vm --vm -c limits.memory=512MiB -d root,size=3584MiB Launching nested-vm Error: Failed instance creation: Failed running: forklimits fd=3 fd=4 fd=5 -- /snap/lxd/38854/bin/qemu-system-x86_64 -S -name nested-vm -uuid 44280c7e-ddfe-4c74-9101-e861139cad41 -daemonize -cpu host,hv_passthrough -nographic -serial chardev:console -nodefaults -no-user-config -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=allow,resourcecontrol=deny -readconfig /var/snap/lxd/common/lxd/logs/nested-vm/qemu.conf -spice unix=on,disable-ticketing=on,addr=/var/snap/lxd/common/lxd/logs/nested-vm/qemu.spice -pidfile /var/snap/lxd/common/lxd/logs/nested-vm/qemu.pid -D /var/snap/lxd/common/lxd/logs/nested-vm/qemu.log -smbios type=2,manufacturer=Canonical Ltd.,product=LXD -run-with user=lxd: : signal: killed ``` ``` # dmesg ... [ 1284.623266] audit: type=1400 audit(1775505789.403:672): apparmor="STATUS" operation="profile_load" label="lxd-ctn_</var/snap/lxd/common/lxd>//&:lxd-ctn_<var-snap-lxd-common-lxd>:unconfined" name="lxd-nested-vm_</var/snap/lxd/common/lxd>" pid=7635 comm="apparmor_parser" [ 1284.759224] workqueue: drm_fb_helper_damage_work hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [ 1285.251153] workqueue: drm_fb_helper_damage_work hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [ 1285.431391] BUG: kernel NULL pointer dereference, address: 0000000000000018 [ 1285.448025] #PF: supervisor read access in kernel mode [ 1285.449951] #PF: error_code(0x0000) - not-present page [ 1285.452811] PGD 0 P4D 0 [ 1285.454155] Oops: Oops: 0000 [#4] SMP NOPTI [ 1285.455950] CPU: 3 UID: 1000000 PID: 7636 Comm: aa-exec Tainted: P D O 6.17.0-20-generic #20~24.04.1-Ubuntu PREEMPT(voluntary) [ 1285.460690] Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE [ 1285.462968] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 2025.11-3ubuntu6 03/17/2026 [ 1285.466160] RIP: 0010:aa_file_perm+0xb9/0x3b0 [ 1285.467982] Code: ff 45 31 c0 45 31 c9 e9 90 4c 68 ff 49 8b 47 20 49 8b 4f 18 0f b7 00 66 25 00 f0 66 3d 00 c0 75 18 41 f7 c4 46 00 10 00 75 0f <48> 8b 41 18 66 83 78 10 01 0f 84 44 01 00 00 f7 d2 44 21 e2 89 55 [ 1285.474719] RSP: 0018:ffffccd888edb8b8 EFLAGS: 00010246 [ 1285.476824] RAX: 000000000000c000 RBX: ffff8b29c3655900 RCX: 0000000000000000 [ 1285.479640] RDX: 0000000000000000 RSI: ffff8b29e0a25900 RDI: ffffffffa1bc6817 [ 1285.482118] RBP: ffffccd888edb910 R08: 0000000000000000 R09: 0000000000000001 [ 1285.485600] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 1285.488328] R13: ffff8b2a26aada10 R14: ffff8b29c3655e00 R15: ffff8b2a367ff600 [ 1285.491553] FS: 0000000000000000(0000) GS:ffff8b2d8cbe2000(0000) knlGS:0000000000000000 [ 1285.495022] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1285.497152] CR2: 0000000000000018 CR3: 00000001767c9000 CR4: 0000000000750ef0 [ 1285.499746] PKRU: 55555554 [ 1285.501910] Call Trace: [ 1285.503323] <TASK> [ 1285.504533] ? __pfx_match_file+0x10/0x10 [ 1285.506124] match_file+0x7b/0xa0 [ 1285.507839] iterate_fd+0x6b/0xb0 [ 1285.509416] aa_inherit_files+0x101/0x280 [ 1285.511796] apparmor_bprm_committing_creds+0x6f/0xa0 [ 1285.514681] security_bprm_committing_creds+0x27/0x40 [ 1285.517415] begin_new_exec+0x2ac/0x420 [ 1285.518990] load_elf_binary+0x32d/0xf40 [ 1285.520707] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.522687] ? ima_bprm_check+0x71/0xa0 [ 1285.524556] exec_binprm+0x138/0x310 [ 1285.526049] bprm_execve.part.0+0x166/0x220 [ 1285.528406] bprm_execve+0x45/0x80 [ 1285.530753] do_execveat_common.isra.0+0x194/0x1f0 [ 1285.532636] __x64_sys_execve+0x39/0x60 [ 1285.534164] x64_sys_call+0x1c28/0x2680 [ 1285.536381] do_syscall_64+0x80/0xa40 [ 1285.537896] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.540575] ? filp_flush+0x91/0xb0 [ 1285.541999] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.544368] ? filp_close+0x1f/0x30 [ 1285.546371] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.548126] ? do_dup2+0xc2/0x160 [ 1285.549630] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.555534] ? ksys_dup3+0x9d/0x120 [ 1285.556865] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.623421] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.625736] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.628448] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.671728] ? do_syscall_64+0xb6/0xa40 [ 1285.677888] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.846163] ? ksys_dup3+0x9d/0x120 [ 1285.850353] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.852366] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.853980] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.855886] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.858582] ? do_syscall_64+0xb6/0xa40 [ 1285.860923] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.863547] ? __x64_sys_rt_sigprocmask+0x7d/0xe0 [ 1285.865343] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.866890] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.870395] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.871990] ? do_syscall_64+0xb6/0xa40 [ 1285.873879] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.878556] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.880740] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.882436] ? do_syscall_64+0xb6/0xa40 [ 1285.883790] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.886428] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 1285.888210] RIP: 0033:0x4272ce [ 1285.889680] Code: Unable to access opcode bytes at 0x4272a4. [ 1285.893743] RSP: 002b:000025a3d044c278 EFLAGS: 00000202 ORIG_RAX: 000000000000003b [ 1285.896482] RAX: ffffffffffffffda RBX: 000025a3d11749f0 RCX: 00000000004272ce [ 1285.901072] RDX: 000025a3d064b500 RSI: 000025a3d12a6280 RDI: 000025a3d11749f0 [ 1285.903353] RBP: 000025a3d044c2b8 R08: 0000000000000000 R09: 0000000000000000 [ 1285.905720] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000026 [ 1285.910249] R13: 0000000000000006 R14: 000025a3d098c5a0 R15: 0000000000000006 [ 1285.915743] </TASK> [ 1285.921980] Modules linked in: veth nft_masq nft_chain_nat bridge stp llc zfs(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter nf_tables vhost_vsock vhost vhost_iotlb cfg80211 intel_rapl_msr intel_rapl_common binfmt_misc kvm_amd ccp nls_iso8859_1 joydev kvm irqbypass polyval_clmulni 9pnet_virtio ghash_clmulni_intel aesni_intel 9pnet psmouse i2c_i801 i2c_smbus lpc_ich vmw_vsock_virtio_transport ahci i2c_mux netfs virtiofs libahci vmw_vsock_virtio_transport_common virtio_gpu vsock vmgenid virtio_dma_buf virtio_input input_leds mac_hid serio_raw sch_fq_codel efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg virtio_rng ip_tables x_tables autofs4 [ 1286.010588] CR2: 0000000000000018 [ 1286.012064] ---[ end trace 0000000000000000 ]--- [ 1289.457331] RIP: 0010:aa_file_perm+0xb9/0x3b0 [ 1289.461328] Code: ff 45 31 c0 45 31 c9 e9 90 4c 68 ff 49 8b 47 20 49 8b 4f 18 0f b7 00 66 25 00 f0 66 3d 00 c0 75 18 41 f7 c4 46 00 10 00 75 0f <48> 8b 41 18 66 83 78 10 01 0f 84 44 01 00 00 f7 d2 44 21 e2 89 55 [ 1289.465382] RSP: 0018:ffffccd882fb3b78 EFLAGS: 00010246 [ 1289.466585] RAX: 000000000000c000 RBX: ffff8b29c3655580 RCX: 0000000000000000 [ 1289.468081] RDX: 0000000000000000 RSI: ffff8b29ceb97b40 RDI: ffffffffa1bc6817 [ 1289.469567] RBP: ffffccd882fb3bd0 R08: 0000000000000000 R09: 0000000000000001 [ 1289.471018] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 1289.472454] R13: ffff8b29c3d35bc8 R14: ffff8b29c0927080 R15: ffff8b29e0a1d240 [ 1289.473856] FS: 0000000000000000(0000) GS:ffff8b2d8cbe2000(0000) knlGS:0000000000000000 [ 1289.475626] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1289.476946] CR2: 00000000004272a4 CR3: 00000001767c9000 CR4: 0000000000750ef0 [ 1289.478331] PKRU: 55555554 [ 1289.479036] note: aa-exec[7636] exited with irqs disabled [ 1289.480253] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 2968251915 wd_nsec: 2968254099 [ 1289.482291] note: aa-exec[7636] exited with preempt_count 1 [ 1289.519692] tap6e10c87b: left allmulticast mode [ 1289.520854] tap6e10c87b: left promiscuous mode [ 1289.522179] lxdbr0: port 1(tap6e10c87b) entered disabled state ``` Using older kernels like 6.8, 6.11 or 6.14 shows no problem. The issue was initially noticed on GitHub Action runners when images switched from 6.14 to 6.17. https://github.com/canonical/lxd- ci/actions/runs/24022621190/job/70054463342#step:15:1028 is one recent failed run. Additional information: # lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.4 LTS Release: 24.04 # uname -a Linux v2 6.17.0-20-generic #20~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 19 01:28:37 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: With a 24.04 machine (physical or VM), it's possible to trigger a kernel NULL pointer dereference when running with the 6.17 HWE kernel. - Here is the PoC: ``` cat << EOF > poc.sh #!/bin/bash set -eux # VM inside container causes a kernel NULL pointer dereference on 6.17 if [[ "$(uname -r)" =~ ^6\.17\.0 ]]; then - echo "::warning:: 6.17 kernel detected, expect failure then check 'dmesg'" +   echo "::warning:: 6.17 kernel detected, expect failure then check 'dmesg'" else - echo "::info:: 6.17 kernel NOT detected, expect success and consider switching to 'linux-image-generic-hwe-24.04'" +   echo "::info:: 6.17 kernel NOT detected, expect success and consider switching to 'linux-image-generic-hwe-24.04'" fi snap install lxd --channel latest/edge lxd init --auto # prepare ctn to be used for nested VM testing lxc init ubuntu-minimal-daily:24.04 ctn -c security.devlxd.images=true -c security.nesting=true -s default lxc config device add ctn kvm unix-char source=/dev/kvm lxc config device add ctn vhost-net unix-char source=/dev/vhost-net lxc config device add ctn vhost-vsock unix-char source=/dev/vhost-vsock lxc config device add ctn vsock unix-char source=/dev/vsock lxc start ctn sleep 30 lxc exec ctn -- snap wait system seed.loaded lxc exec ctn -- snap install lxd --channel latest/edge lxc exec ctn -- lxd init --auto # launch small nested VM lxc exec ctn -- lxc launch ubuntu-minimal-daily:24.04 nested-vm --vm -c limits.memory=512MiB -d root,size=3584MiB # cleanup lxc delete -f ctn EOF ``` - Running the PoC will look like this: ``` # bash ./poc.sh ... + lxc exec ctn -- lxd init --auto + lxc exec ctn -- lxc launch ubuntu-minimal-daily:24.04 nested-vm --vm -c limits.memory=512MiB -d root,size=3584MiB Launching nested-vm Error: Failed instance creation: Failed running: forklimits fd=3 fd=4 fd=5 -- /snap/lxd/38854/bin/qemu-system-x86_64 -S -name nested-vm -uuid 44280c7e-ddfe-4c74-9101-e861139cad41 -daemonize -cpu host,hv_passthrough -nographic -serial chardev:console -nodefaults -no-user-config -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=allow,resourcecontrol=deny -readconfig /var/snap/lxd/common/lxd/logs/nested-vm/qemu.conf -spice unix=on,disable-ticketing=on,addr=/var/snap/lxd/common/lxd/logs/nested-vm/qemu.spice -pidfile /var/snap/lxd/common/lxd/logs/nested-vm/qemu.pid -D /var/snap/lxd/common/lxd/logs/nested-vm/qemu.log -smbios type=2,manufacturer=Canonical Ltd.,product=LXD -run-with user=lxd: : signal: killed ``` ``` # dmesg ... [ 1284.623266] audit: type=1400 audit(1775505789.403:672): apparmor="STATUS" operation="profile_load" label="lxd-ctn_</var/snap/lxd/common/lxd>//&:lxd-ctn_<var-snap-lxd-common-lxd>:unconfined" name="lxd-nested-vm_</var/snap/lxd/common/lxd>" pid=7635 comm="apparmor_parser" [ 1284.759224] workqueue: drm_fb_helper_damage_work hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [ 1285.251153] workqueue: drm_fb_helper_damage_work hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [ 1285.431391] BUG: kernel NULL pointer dereference, address: 0000000000000018 [ 1285.448025] #PF: supervisor read access in kernel mode [ 1285.449951] #PF: error_code(0x0000) - not-present page - [ 1285.452811] PGD 0 P4D 0 + [ 1285.452811] PGD 0 P4D 0 [ 1285.454155] Oops: Oops: 0000 [#4] SMP NOPTI - [ 1285.455950] CPU: 3 UID: 1000000 PID: 7636 Comm: aa-exec Tainted: P D O 6.17.0-20-generic #20~24.04.1-Ubuntu PREEMPT(voluntary) + [ 1285.455950] CPU: 3 UID: 1000000 PID: 7636 Comm: aa-exec Tainted: P D O 6.17.0-20-generic #20~24.04.1-Ubuntu PREEMPT(voluntary) [ 1285.460690] Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE [ 1285.462968] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 2025.11-3ubuntu6 03/17/2026 [ 1285.466160] RIP: 0010:aa_file_perm+0xb9/0x3b0 [ 1285.467982] Code: ff 45 31 c0 45 31 c9 e9 90 4c 68 ff 49 8b 47 20 49 8b 4f 18 0f b7 00 66 25 00 f0 66 3d 00 c0 75 18 41 f7 c4 46 00 10 00 75 0f <48> 8b 41 18 66 83 78 10 01 0f 84 44 01 00 00 f7 d2 44 21 e2 89 55 [ 1285.474719] RSP: 0018:ffffccd888edb8b8 EFLAGS: 00010246 [ 1285.476824] RAX: 000000000000c000 RBX: ffff8b29c3655900 RCX: 0000000000000000 [ 1285.479640] RDX: 0000000000000000 RSI: ffff8b29e0a25900 RDI: ffffffffa1bc6817 [ 1285.482118] RBP: ffffccd888edb910 R08: 0000000000000000 R09: 0000000000000001 [ 1285.485600] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 1285.488328] R13: ffff8b2a26aada10 R14: ffff8b29c3655e00 R15: ffff8b2a367ff600 [ 1285.491553] FS: 0000000000000000(0000) GS:ffff8b2d8cbe2000(0000) knlGS:0000000000000000 [ 1285.495022] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1285.497152] CR2: 0000000000000018 CR3: 00000001767c9000 CR4: 0000000000750ef0 [ 1285.499746] PKRU: 55555554 [ 1285.501910] Call Trace: [ 1285.503323] <TASK> [ 1285.504533] ? __pfx_match_file+0x10/0x10 [ 1285.506124] match_file+0x7b/0xa0 [ 1285.507839] iterate_fd+0x6b/0xb0 [ 1285.509416] aa_inherit_files+0x101/0x280 [ 1285.511796] apparmor_bprm_committing_creds+0x6f/0xa0 [ 1285.514681] security_bprm_committing_creds+0x27/0x40 [ 1285.517415] begin_new_exec+0x2ac/0x420 [ 1285.518990] load_elf_binary+0x32d/0xf40 [ 1285.520707] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.522687] ? ima_bprm_check+0x71/0xa0 [ 1285.524556] exec_binprm+0x138/0x310 [ 1285.526049] bprm_execve.part.0+0x166/0x220 [ 1285.528406] bprm_execve+0x45/0x80 [ 1285.530753] do_execveat_common.isra.0+0x194/0x1f0 [ 1285.532636] __x64_sys_execve+0x39/0x60 [ 1285.534164] x64_sys_call+0x1c28/0x2680 [ 1285.536381] do_syscall_64+0x80/0xa40 [ 1285.537896] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.540575] ? filp_flush+0x91/0xb0 [ 1285.541999] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.544368] ? filp_close+0x1f/0x30 [ 1285.546371] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.548126] ? do_dup2+0xc2/0x160 [ 1285.549630] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.555534] ? ksys_dup3+0x9d/0x120 [ 1285.556865] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.623421] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.625736] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.628448] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.671728] ? do_syscall_64+0xb6/0xa40 [ 1285.677888] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.846163] ? ksys_dup3+0x9d/0x120 [ 1285.850353] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.852366] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.853980] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.855886] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.858582] ? do_syscall_64+0xb6/0xa40 [ 1285.860923] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.863547] ? __x64_sys_rt_sigprocmask+0x7d/0xe0 [ 1285.865343] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.866890] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.870395] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.871990] ? do_syscall_64+0xb6/0xa40 [ 1285.873879] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.878556] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.880740] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.882436] ? do_syscall_64+0xb6/0xa40 [ 1285.883790] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.886428] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 1285.888210] RIP: 0033:0x4272ce [ 1285.889680] Code: Unable to access opcode bytes at 0x4272a4. [ 1285.893743] RSP: 002b:000025a3d044c278 EFLAGS: 00000202 ORIG_RAX: 000000000000003b [ 1285.896482] RAX: ffffffffffffffda RBX: 000025a3d11749f0 RCX: 00000000004272ce [ 1285.901072] RDX: 000025a3d064b500 RSI: 000025a3d12a6280 RDI: 000025a3d11749f0 [ 1285.903353] RBP: 000025a3d044c2b8 R08: 0000000000000000 R09: 0000000000000000 [ 1285.905720] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000026 [ 1285.910249] R13: 0000000000000006 R14: 000025a3d098c5a0 R15: 0000000000000006 [ 1285.915743] </TASK> [ 1285.921980] Modules linked in: veth nft_masq nft_chain_nat bridge stp llc zfs(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter nf_tables vhost_vsock vhost vhost_iotlb cfg80211 intel_rapl_msr intel_rapl_common binfmt_misc kvm_amd ccp nls_iso8859_1 joydev kvm irqbypass polyval_clmulni 9pnet_virtio ghash_clmulni_intel aesni_intel 9pnet psmouse i2c_i801 i2c_smbus lpc_ich vmw_vsock_virtio_transport ahci i2c_mux netfs virtiofs libahci vmw_vsock_virtio_transport_common virtio_gpu vsock vmgenid virtio_dma_buf virtio_input input_leds mac_hid serio_raw sch_fq_codel efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg virtio_rng ip_tables x_tables autofs4 [ 1286.010588] CR2: 0000000000000018 [ 1286.012064] ---[ end trace 0000000000000000 ]--- [ 1289.457331] RIP: 0010:aa_file_perm+0xb9/0x3b0 [ 1289.461328] Code: ff 45 31 c0 45 31 c9 e9 90 4c 68 ff 49 8b 47 20 49 8b 4f 18 0f b7 00 66 25 00 f0 66 3d 00 c0 75 18 41 f7 c4 46 00 10 00 75 0f <48> 8b 41 18 66 83 78 10 01 0f 84 44 01 00 00 f7 d2 44 21 e2 89 55 [ 1289.465382] RSP: 0018:ffffccd882fb3b78 EFLAGS: 00010246 [ 1289.466585] RAX: 000000000000c000 RBX: ffff8b29c3655580 RCX: 0000000000000000 [ 1289.468081] RDX: 0000000000000000 RSI: ffff8b29ceb97b40 RDI: ffffffffa1bc6817 [ 1289.469567] RBP: ffffccd882fb3bd0 R08: 0000000000000000 R09: 0000000000000001 [ 1289.471018] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 1289.472454] R13: ffff8b29c3d35bc8 R14: ffff8b29c0927080 R15: ffff8b29e0a1d240 [ 1289.473856] FS: 0000000000000000(0000) GS:ffff8b2d8cbe2000(0000) knlGS:0000000000000000 [ 1289.475626] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1289.476946] CR2: 00000000004272a4 CR3: 00000001767c9000 CR4: 0000000000750ef0 [ 1289.478331] PKRU: 55555554 [ 1289.479036] note: aa-exec[7636] exited with irqs disabled [ 1289.480253] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 2968251915 wd_nsec: 2968254099 [ 1289.482291] note: aa-exec[7636] exited with preempt_count 1 [ 1289.519692] tap6e10c87b: left allmulticast mode [ 1289.520854] tap6e10c87b: left promiscuous mode [ 1289.522179] lxdbr0: port 1(tap6e10c87b) entered disabled state ``` - Using older kernels like 6.8, 6.11 or 6.14 shows no problem. + Using older kernels like 6.8, 6.11 or 6.14 shows no problem. The issue + was initially noticed on GitHub Action runners when images switched from + 6.14 to 6.17. https://github.com/canonical/lxd- + ci/actions/runs/24022621190/job/70054463342#step:15:1028 is one recent + failed run. Additional information: # lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.4 LTS Release: 24.04 # uname -a Linux v2 6.17.0-20-generic #20~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 19 01:28:37 UTC 2 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147374 Title: BUG: kernel NULL pointer dereference when starting VM inside a container Status in linux package in Ubuntu: New Bug description: With a 24.04 machine (physical or VM), it's possible to trigger a kernel NULL pointer dereference when running with the 6.17 HWE kernel. Here is the PoC: ``` cat << EOF > poc.sh #!/bin/bash set -eux # VM inside container causes a kernel NULL pointer dereference on 6.17 if [[ "$(uname -r)" =~ ^6\.17\.0 ]]; then   echo "::warning:: 6.17 kernel detected, expect failure then check 'dmesg'" else   echo "::info:: 6.17 kernel NOT detected, expect success and consider switching to 'linux-image-generic-hwe-24.04'" fi snap install lxd --channel latest/edge lxd init --auto # prepare ctn to be used for nested VM testing lxc init ubuntu-minimal-daily:24.04 ctn -c security.devlxd.images=true -c security.nesting=true -s default lxc config device add ctn kvm unix-char source=/dev/kvm lxc config device add ctn vhost-net unix-char source=/dev/vhost-net lxc config device add ctn vhost-vsock unix-char source=/dev/vhost-vsock lxc config device add ctn vsock unix-char source=/dev/vsock lxc start ctn sleep 30 lxc exec ctn -- snap wait system seed.loaded lxc exec ctn -- snap install lxd --channel latest/edge lxc exec ctn -- lxd init --auto # launch small nested VM lxc exec ctn -- lxc launch ubuntu-minimal-daily:24.04 nested-vm --vm -c limits.memory=512MiB -d root,size=3584MiB # cleanup lxc delete -f ctn EOF ``` Running the PoC will look like this: ``` # bash ./poc.sh ... + lxc exec ctn -- lxd init --auto + lxc exec ctn -- lxc launch ubuntu-minimal-daily:24.04 nested-vm --vm -c limits.memory=512MiB -d root,size=3584MiB Launching nested-vm Error: Failed instance creation: Failed running: forklimits fd=3 fd=4 fd=5 -- /snap/lxd/38854/bin/qemu-system-x86_64 -S -name nested-vm -uuid 44280c7e-ddfe-4c74-9101-e861139cad41 -daemonize -cpu host,hv_passthrough -nographic -serial chardev:console -nodefaults -no-user-config -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=allow,resourcecontrol=deny -readconfig /var/snap/lxd/common/lxd/logs/nested-vm/qemu.conf -spice unix=on,disable-ticketing=on,addr=/var/snap/lxd/common/lxd/logs/nested-vm/qemu.spice -pidfile /var/snap/lxd/common/lxd/logs/nested-vm/qemu.pid -D /var/snap/lxd/common/lxd/logs/nested-vm/qemu.log -smbios type=2,manufacturer=Canonical Ltd.,product=LXD -run-with user=lxd: : signal: killed ``` ``` # dmesg ... [ 1284.623266] audit: type=1400 audit(1775505789.403:672): apparmor="STATUS" operation="profile_load" label="lxd-ctn_</var/snap/lxd/common/lxd>//&:lxd-ctn_<var-snap-lxd-common-lxd>:unconfined" name="lxd-nested-vm_</var/snap/lxd/common/lxd>" pid=7635 comm="apparmor_parser" [ 1284.759224] workqueue: drm_fb_helper_damage_work hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [ 1285.251153] workqueue: drm_fb_helper_damage_work hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [ 1285.431391] BUG: kernel NULL pointer dereference, address: 0000000000000018 [ 1285.448025] #PF: supervisor read access in kernel mode [ 1285.449951] #PF: error_code(0x0000) - not-present page [ 1285.452811] PGD 0 P4D 0 [ 1285.454155] Oops: Oops: 0000 [#4] SMP NOPTI [ 1285.455950] CPU: 3 UID: 1000000 PID: 7636 Comm: aa-exec Tainted: P D O 6.17.0-20-generic #20~24.04.1-Ubuntu PREEMPT(voluntary) [ 1285.460690] Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE [ 1285.462968] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 2025.11-3ubuntu6 03/17/2026 [ 1285.466160] RIP: 0010:aa_file_perm+0xb9/0x3b0 [ 1285.467982] Code: ff 45 31 c0 45 31 c9 e9 90 4c 68 ff 49 8b 47 20 49 8b 4f 18 0f b7 00 66 25 00 f0 66 3d 00 c0 75 18 41 f7 c4 46 00 10 00 75 0f <48> 8b 41 18 66 83 78 10 01 0f 84 44 01 00 00 f7 d2 44 21 e2 89 55 [ 1285.474719] RSP: 0018:ffffccd888edb8b8 EFLAGS: 00010246 [ 1285.476824] RAX: 000000000000c000 RBX: ffff8b29c3655900 RCX: 0000000000000000 [ 1285.479640] RDX: 0000000000000000 RSI: ffff8b29e0a25900 RDI: ffffffffa1bc6817 [ 1285.482118] RBP: ffffccd888edb910 R08: 0000000000000000 R09: 0000000000000001 [ 1285.485600] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 1285.488328] R13: ffff8b2a26aada10 R14: ffff8b29c3655e00 R15: ffff8b2a367ff600 [ 1285.491553] FS: 0000000000000000(0000) GS:ffff8b2d8cbe2000(0000) knlGS:0000000000000000 [ 1285.495022] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1285.497152] CR2: 0000000000000018 CR3: 00000001767c9000 CR4: 0000000000750ef0 [ 1285.499746] PKRU: 55555554 [ 1285.501910] Call Trace: [ 1285.503323] <TASK> [ 1285.504533] ? __pfx_match_file+0x10/0x10 [ 1285.506124] match_file+0x7b/0xa0 [ 1285.507839] iterate_fd+0x6b/0xb0 [ 1285.509416] aa_inherit_files+0x101/0x280 [ 1285.511796] apparmor_bprm_committing_creds+0x6f/0xa0 [ 1285.514681] security_bprm_committing_creds+0x27/0x40 [ 1285.517415] begin_new_exec+0x2ac/0x420 [ 1285.518990] load_elf_binary+0x32d/0xf40 [ 1285.520707] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.522687] ? ima_bprm_check+0x71/0xa0 [ 1285.524556] exec_binprm+0x138/0x310 [ 1285.526049] bprm_execve.part.0+0x166/0x220 [ 1285.528406] bprm_execve+0x45/0x80 [ 1285.530753] do_execveat_common.isra.0+0x194/0x1f0 [ 1285.532636] __x64_sys_execve+0x39/0x60 [ 1285.534164] x64_sys_call+0x1c28/0x2680 [ 1285.536381] do_syscall_64+0x80/0xa40 [ 1285.537896] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.540575] ? filp_flush+0x91/0xb0 [ 1285.541999] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.544368] ? filp_close+0x1f/0x30 [ 1285.546371] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.548126] ? do_dup2+0xc2/0x160 [ 1285.549630] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.555534] ? ksys_dup3+0x9d/0x120 [ 1285.556865] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.623421] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.625736] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.628448] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.671728] ? do_syscall_64+0xb6/0xa40 [ 1285.677888] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.846163] ? ksys_dup3+0x9d/0x120 [ 1285.850353] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.852366] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.853980] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.855886] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.858582] ? do_syscall_64+0xb6/0xa40 [ 1285.860923] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.863547] ? __x64_sys_rt_sigprocmask+0x7d/0xe0 [ 1285.865343] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.866890] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.870395] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.871990] ? do_syscall_64+0xb6/0xa40 [ 1285.873879] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.878556] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 1285.880740] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.882436] ? do_syscall_64+0xb6/0xa40 [ 1285.883790] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1285.886428] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 1285.888210] RIP: 0033:0x4272ce [ 1285.889680] Code: Unable to access opcode bytes at 0x4272a4. [ 1285.893743] RSP: 002b:000025a3d044c278 EFLAGS: 00000202 ORIG_RAX: 000000000000003b [ 1285.896482] RAX: ffffffffffffffda RBX: 000025a3d11749f0 RCX: 00000000004272ce [ 1285.901072] RDX: 000025a3d064b500 RSI: 000025a3d12a6280 RDI: 000025a3d11749f0 [ 1285.903353] RBP: 000025a3d044c2b8 R08: 0000000000000000 R09: 0000000000000000 [ 1285.905720] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000026 [ 1285.910249] R13: 0000000000000006 R14: 000025a3d098c5a0 R15: 0000000000000006 [ 1285.915743] </TASK> [ 1285.921980] Modules linked in: veth nft_masq nft_chain_nat bridge stp llc zfs(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter nf_tables vhost_vsock vhost vhost_iotlb cfg80211 intel_rapl_msr intel_rapl_common binfmt_misc kvm_amd ccp nls_iso8859_1 joydev kvm irqbypass polyval_clmulni 9pnet_virtio ghash_clmulni_intel aesni_intel 9pnet psmouse i2c_i801 i2c_smbus lpc_ich vmw_vsock_virtio_transport ahci i2c_mux netfs virtiofs libahci vmw_vsock_virtio_transport_common virtio_gpu vsock vmgenid virtio_dma_buf virtio_input input_leds mac_hid serio_raw sch_fq_codel efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg virtio_rng ip_tables x_tables autofs4 [ 1286.010588] CR2: 0000000000000018 [ 1286.012064] ---[ end trace 0000000000000000 ]--- [ 1289.457331] RIP: 0010:aa_file_perm+0xb9/0x3b0 [ 1289.461328] Code: ff 45 31 c0 45 31 c9 e9 90 4c 68 ff 49 8b 47 20 49 8b 4f 18 0f b7 00 66 25 00 f0 66 3d 00 c0 75 18 41 f7 c4 46 00 10 00 75 0f <48> 8b 41 18 66 83 78 10 01 0f 84 44 01 00 00 f7 d2 44 21 e2 89 55 [ 1289.465382] RSP: 0018:ffffccd882fb3b78 EFLAGS: 00010246 [ 1289.466585] RAX: 000000000000c000 RBX: ffff8b29c3655580 RCX: 0000000000000000 [ 1289.468081] RDX: 0000000000000000 RSI: ffff8b29ceb97b40 RDI: ffffffffa1bc6817 [ 1289.469567] RBP: ffffccd882fb3bd0 R08: 0000000000000000 R09: 0000000000000001 [ 1289.471018] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 1289.472454] R13: ffff8b29c3d35bc8 R14: ffff8b29c0927080 R15: ffff8b29e0a1d240 [ 1289.473856] FS: 0000000000000000(0000) GS:ffff8b2d8cbe2000(0000) knlGS:0000000000000000 [ 1289.475626] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1289.476946] CR2: 00000000004272a4 CR3: 00000001767c9000 CR4: 0000000000750ef0 [ 1289.478331] PKRU: 55555554 [ 1289.479036] note: aa-exec[7636] exited with irqs disabled [ 1289.480253] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 2968251915 wd_nsec: 2968254099 [ 1289.482291] note: aa-exec[7636] exited with preempt_count 1 [ 1289.519692] tap6e10c87b: left allmulticast mode [ 1289.520854] tap6e10c87b: left promiscuous mode [ 1289.522179] lxdbr0: port 1(tap6e10c87b) entered disabled state ``` Using older kernels like 6.8, 6.11 or 6.14 shows no problem. The issue was initially noticed on GitHub Action runners when images switched from 6.14 to 6.17. https://github.com/canonical/lxd- ci/actions/runs/24022621190/job/70054463342#step:15:1028 is one recent failed run. Additional information: # lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.4 LTS Release: 24.04 # uname -a Linux v2 6.17.0-20-generic #20~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 19 01:28:37 UTC 2 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147374/+subscriptions

[Bug 2145171] Re: [SRU] MIPI camera is not working after upgrading to 6.17-oem

This bug was fixed in the package linux - 7.0.0-12.12 --------------- linux (7.0.0-12.12) resolute; urgency=medium * resolute/linux: 7.0.0-12.12 -proposed tracker (LP: #2146778) * Packaging resync (LP: #1786013) - [Packaging] update variants * linux-generic does not run scripts in /usr/share/kernel/*.d (LP: #2147005) - [Packaging] templates: Use consistent indentation - [Packaging] templates: Run scripts in /usr/share/kernel/*.d too * RISC-V kernel config is out of sync with other archs (LP: #1981437) - [Config] riscv64: Enable COUNTER=m - [Config] riscv64: Use GENDWARFKSYMS like other architectures * unconfined profile denies userns_create for chromium based processes (LP: #1990064) - [Config] disable CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS * FFe: add network interface mediation to 26.04 (LP: #2144679) - SAUCE: apparmor5.0.0 [57/57]: apparmor: add the ability to use interface in network mediation. * Jellyfin Desktop Flatpak doesn't work with the current AppArmor profile (LP: #2142956) - SAUCE: apparmor5.0.0 [29/57]: apparmor: fix fine grained inet mediation sock_file_perm - SAUCE: apparmor5.0.0 [30/57]: apparmor-next 7.1: aapparmor: use target task's context in apparmor_getprocattr() - SAUCE: apparmor5.0.0 [31/57]: apparmor-next 7.1: apparmor: return error on namespace mismatch in verify_header - SAUCE: apparmor5.0.0 [32/57]: apparmor-next 7.1: apparmor: enable differential encoding - SAUCE: apparmor5.0.0 [33/57]: apparmor-next 7.1: apparmor: propagate -ENOMEM correctly in unpack_table - SAUCE: apparmor5.0.0 [34/57]: apparmor-next 7.1: apparmor: Replace memcpy + NUL termination with kmemdup_nul in do_setattr - SAUCE: apparmor5.0.0 [35/57]: apparmor-next 7.1: apparmor: Remove redundant if check in sk_peer_get_label - SAUCE: apparmor5.0.0 [36/57]: apparmor-next 7.1: apparmor: use __label_make_stale in __aa_proxy_redirect - SAUCE: apparmor5.0.0 [37/57]: apparmor-next 7.1: apparmor: fix net.h and policy.h circular include pattern - SAUCE: apparmor5.0.0 [39/57]: apparmor-next 7.1: apparmor: make include headers self-contained - SAUCE: apparmor5.0.0 [40/57]: apparmor-next 7.1: apparmor: Use sysfs_emit in param_get_{audit,mode} - SAUCE: apparmor5.0.0 [41/57]: apparmor-next 7.1: apparmor: fix rawdata_f_data implicit flex array - SAUCE: apparmor5.0.0 [42/57]: apparmor-next 7.1: apparmor: free rawdata as soon as possible - SAUCE: apparmor5.0.0 [43/57]: apparmor-next 7.1: apparmor: Initial support for compressed policies - SAUCE: apparmor5.0.0 [44/57]: apparmor-next 7.1: apparmor: fix potential UAF in aa_replace_profiles - SAUCE: apparmor5.0.0 [45/57]: apparmor-next 7.1: apparmor: hide unused get_loaddata_common_ref() function - SAUCE: apparmor5.0.0 [46/57]: apparmor-next 7.1: apparmor: Fix string overrun due to missing termination - SAUCE: apparmor5.0.0 [47/57]: apparmor: fix packed tag on v5 header struct - SAUCE: apparmor5.0.0 [48/57]: apparmor: add temporal caching to audit responses. - SAUCE: apparmor5.0.0 [49/57]: apparmor: change fn_label_build() call to not return NULL - SAUCE: apparmor5.0.0 [50/57]: apparmor: make fn_label_build() capable of handling not supported - SAUCE: apparmor5.0.0 [51/57]: apparmor: move netfilter functions next to the LSM network operations - SAUCE: apparmor5.0.0 [52/57]: apparmor: move sock_rvc_skb() next to inet_conn_request - SAUCE: apparmor5.0.0 [53/57]: apparmor: fix af_unix local addr mediation binding - SAUCE: apparmor5.0.0 [54/57]: cleanups of apparmor af_unix mediation - SAUCE: apparmor5.0.0 [55/57]: apparmor: fix apparmor_secmark_check() when !inet and secmark defined. - SAUCE: apparmor5.0.0 [56/57]: apparmor: fix auditing of non-mediation falures * snap service cannot change apparmor hat (LP: #2139664) // Jellyfin Desktop Flatpak doesn't work with the current AppArmor profile (LP: #2142956) - SAUCE: apparmor5.0.0 [38/57]: apparmor-next 7.1: apparmor: grab ns lock and refresh when looking up changehat child profiles * AppArmor blocks write(2) to network sockets with Linux 6.19 (LP: #2141298) - SAUCE: apparmor5.0.0 [28/57]: apparmor: fix aa_label_sk_perm to check for RULE_MEDIATES_NET * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor5.0.0 [1/57]: Stacking: LSM: Single calls in secid hooks - SAUCE: apparmor5.0.0 [2/57]: Stacking: LSM: Exclusive secmark usage - SAUCE: apparmor5.0.0 [3/57]: Stacking: AppArmor: Remove the exclusive flag - SAUCE: apparmor5.0.0 [4/57]: Revert "apparmor: fix dbus permission queries to v9 ABI" - SAUCE: apparmor5.0.0 [5/57]: Revert "apparmor: gate make fine grained unix mediation behind v9 abi" - SAUCE: apparmor5.0.0 [6/57]: apparmor: net: patch to provide compatibility with v2.x net rules - SAUCE: apparmor5.0.0 [7/57]: apparmor: net: add fine grained ipv4/ipv6 mediation - SAUCE: apparmor5.0.0 [8/57]: apparmor: lift compatibility check out of profile_af_perm - SAUCE: apparmor5.0.0 [9/57]: apparmor: userns: add unprivileged user ns mediation - SAUCE: apparmor5.0.0 [10/57]: apparmor: userns: Add sysctls for additional controls of unpriv userns restrictions - SAUCE: apparmor5.0.0 [12/57]: apparmor: userns: open userns related sysctl so lxc can check if restriction are in place - SAUCE: apparmor5.0.0 [13/57]: apparmor: userns: allow profile to be transitioned when a userns is created - SAUCE: apparmor5.0.0 [14/57]: apparmor: mqueue: call security_inode_init_security on inode creation - SAUCE: apparmor5.0.0 [15/57]: apparmor: mqueue: add fine grained mediation of posix mqueues - SAUCE: apparmor5.0.0 [16/57]: apparmor: uring: add io_uring mediation - SAUCE: apparmor5.0.0 [19/57]: apparmor: prompt: setup slab cache for audit data - SAUCE: apparmor5.0.0 [20/57]: apparmor: prompt: add the ability for profiles to have a learning cache - SAUCE: apparmor5.0.0 [21/57]: apparmor: prompt: enable userspace upcall for mediation - SAUCE: apparmor5.0.0 [22/57]: apparmor: prompt: pass prompt boolean through into path_name as well - SAUCE: apparmor5.0.0 [23/57]: apparmor: check for supported version in notification messages. - SAUCE: apparmor5.0.0 [24/57]: apparmor: refactor building notice so it is easier to extend - SAUCE: apparmor5.0.0 [25/57]: apparmor: switch from ENOTSUPP to EPROTONOSUPPORT - SAUCE: apparmor5.0.0 [26/57]: apparmor: add support for meta data tags - SAUCE: apparmor5.0.0 [27/57]: apparmor: prevent profile->disconnected double free in aa_free_profile * update apparmor and LSM stacking patch set (LP: #2028253) // Installation of AppArmor on a 6.14 kernel produces error message "Illegal number: yes" (LP: #2102680) - SAUCE: apparmor5.0.0 [17/57]: apparmor: create an AA_SFS_TYPE_BOOLEAN_INTPRINT sysctl variant - SAUCE: apparmor5.0.0 [18/57]: apparmor: Use AA_SFS_FILE_BOOLEAN_INTPRINT for userns and io_uring sysctls * update apparmor and LSM stacking patch set (LP: #2028253) // [FFe] apparmor-4.0.0-alpha2 for unprivileged user namespace restrictions in mantic (LP: #2032602) - SAUCE: apparmor5.0.0 [11/57]: apparmor: userns - make it so special unconfined profiles can mediate user namespaces * Enable new Intel WCL soundwire support (LP: #2143301) - ASoC: sdw_utils: Add CS42L43B codec info - ASoC: dt-bindings: cirrus, cs42l43: Add CS42L43B variant - mfd: cs42l43: Add support for the B variant - ASoC: cs42l43: Add support for the B variant * Enable audio functions on Dell Huracan/Renegade platforms w/o built-in microphone (LP: #2143902) - ASoC: SDCA: Add default value for mipi-sdca-function-reset-max-delay - ASoC: SDCA: Update counting of SU/GE DAPM routes - ASoC: SDCA: Improve mapping of Q7.8 SDCA volumes - ASoC: SDCA: Pull the Q7.8 volume helpers out of soc-ops - ASoC: add snd_soc_lookup_component_by_name helper - ASoC: soc_sdw_utils: partial match the codec name - ASoC: soc_sdw_utils: remove index from sdca codec name * [SRU] MIPI camera is not working after upgrading to 6.17-oem (LP: #2145171) - SAUCE: ACPI: respect items already in honor_dep before skipping * linux-tools: consider linking perf against LLVM (LP: #2138328) - [Packaging] Actually enable llvm for perf * Pull patch in qla2xxx to Resolute (LP: #2144856) - scsi: qla2xxx: Add support to report MPI FW state * Ubuntu Resolute Desktop image arm64 - Boot on SC8280XP stalls with gpi-dma errors (LP: #2142403) - Revert "arm64: dts: qcom: sc8280xp: Enable GPI DMA" * 26.04 Snapdragon X Elite: Sync concept kernel changes (LP: #2144643) - SAUCE: arm64: dts: add missing denali-oled.dtb to Makefile - SAUCE: dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema - SAUCE: phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add simple-mfd compatible - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add optional PHY handle definitions - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add support for combo- mode endpoints - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Describe iommu entries - SAUCE: media: qcom: camss: Add legacy_phy flag to SoC definition structures - SAUCE: media: qcom: camss: Add support for PHY API devices - SAUCE: media: qcom: camss: Drop legacy PHY descriptions from x1e - SAUCE: arm64: dts: qcom: x1e80100: Add CAMCC block definition - SAUCE: arm64: dts: qcom: x1e80100: Add CCI definitions - SAUCE: arm64: dts: qcom: x1e80100: Add CAMSS block definition - SAUCE: arm64: dts: qcom: x1e80100-crd: Add pm8010 CRD pmic,id=m regulators - SAUCE: arm64: dts: qcom: x1e80100-crd: Add ov08x40 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add pm8010 camera PMIC with voltage levels for IR and RGB camera - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add on ov02c10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add pm8010 camera PMIC with voltage levels for IR and RGB camera - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add l7b_2p8 voltage regulator for RGB camera - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add ov02c10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-dell-inspiron14-7441: Switch on CAMSS RGB sensor - SAUCE: arm64: dts: qcom: x1-asus-zenbook-a14: Add on OV02C10 RGB sensor on CSIPHY4 - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: add camera support - SAUCE: arm64: dts: qcom: x1e78100-t14s: enable camera privacy indicator - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: enable camera privacy indicator - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: enable camera privacy indicator - SAUCE: dt-bindings: arm: qcom: Add ASUS Vivobook X1P42100 variant - SAUCE: arm64: dts: qcom: x1-vivobook-s15: create a common dtsi for Hamoa and Purwa variants - SAUCE: arm64: dts: qcom: x1-vivobook-s15: add Purwa-compatible device tree - SAUCE: firmware: qcom: scm: allow QSEECOM on ASUS Vivobook X1P42100 variant - SAUCE: arm64: dts: qcom: hamoa: Move PCIe PERST and Wake GPIOs to port nodes - SAUCE: arm64: dts: qcom: x1e-acer-swift-14: Move PCIe PERST and Wake GPIOs to port nodes * 25.10 Snapdragon X Elite: Sync concept kernel changes (LP: #2121477) - SAUCE: wip: arm64: dts: qcom: x1e78100-t14s: enable bluetooth * Miscellaneous Ubuntu changes - SAUCE: dt-bindings: arm: qcom: Document HP EliteBook 6 G1q - SAUCE: firmware: qcom: scm: Allow QSEECOM for HP EliteBook 6 G1q - SAUCE: arm64: dts: qcom: x1p42100-hp-elitebook-6-g1q: DT for HP EliteBook 6 G1q - [Config] PHY_QCOM_MIPI_CSI2=m - SAUCE: arm64: dts: x1e80100-lenovo-yoga-slim7x: Fix RGB camera supplies - [Config] toolchain version update - Update Changes.md after v7.0-rc5 rebase - [Packaging] update Ubuntu.md - [Config] enable SECURITY_APPARMOR_PACKET_MEDIATION_ENABLED - [Packaging] Add linux-main-modules-zfs to linux-modules depends * Miscellaneous upstream changes - Revert "UBUNTU: SAUCE: Add Bluetooth support for the Lenovo Yoga Slim 7x" -- Timo Aaltonen <timo.aaltonen@canonical.com> Thu, 02 Apr 2026 11:50:22 +0300 ** Changed in: linux (Ubuntu Resolute) Status: Fix Committed => 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/2145171 Title: [SRU] MIPI camera is not working after upgrading to 6.17-oem 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: Deferred Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: In Progress 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: SRU Justification: [Impact] Upstream v6.18-rc1 commit 4405a214df146775338a1e6232701a29024b82e1 "ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids[]" (also backported to v6.17.8, v6.12.58), which in effect reverts a not yet upstreamed Intel MIPI camera patch titled "ACPI: scan: Update HID for new platform" meant for bug 2090932, and therefore they share the same symptom: [ 4.484426] ov02c10 i2c-OVTI02C1:00: chip id mismatch: 560243!=0 [ 4.484432] ov02c10 i2c-OVTI02C1:00: failed to find sensor: -6 [Fix] While this should really be fixed by upstream Intel's CVS driver and remove the two platforms from acpi_ignore_dep_ids, a sauced change is made to preserve the honor effect and yet don't introduce potential conflict with the upstream before any further progress is made. [Test Plan] 1. Install the kernel from -proposed pocket and reboot into it. 2. Check dmesg has no aforementioned error, 3. Make sure the device appears in the gstreamer device enumeration: $ gst-inspect-1.0 icamerasrc ..... device-name : The input devices name queried from HAL flags: readable, writable Enum "GstCamerasrcDeviceName" Default: 0, "ov02c10-uf" (0): ov02c10-uf - ov02c10 as sensor. [Where problems could occur] No. This restores the hardware enablement effort for the affected platforms only. For Ubuntu, CVS driver is always available along with the kernel, and therefore for a device declared _DEP to the two ACPI devices, the driver can be installed either through ubuntu-drivers or through oem meta packages. [Other Info] While this has been backported to v6.17.8, it affects R and Q. And while this has also been backported to v6.12.58, and linux-6.8/noble is tracking stable 6.8 fixes, Noble will be affected soon or later. Nominate for N, Q and R accordingly. ========== original bug report ========== [Summary] During the kernel SRU testing, we found out that 3 xps13-9350 camera-related tests failed. I saw following in dmesg. ov02c10 i2c-OVTI02C1:00: failed to find sensor: -6 [Reproduce steps] 1. Install GM image 2. Run dist-upgrade to upgrade to 6.17-oem kerenl 3. Run checkbox sru test plan or use https://webcamtests.com/ to test the camera [Failure rate] 1/1 [Affected machines] 202507-36962 202407-34215 202407-34216 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1014-oem 6.17.0-1014.14 ProcVersionSignature: Ubuntu 6.17.0-1014.14-oem 6.17.13 Uname: Linux 6.17.0-1014-oem x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC0: ubuntu 1597 F.... pipewire                       ubuntu 1600 F.... wireplumber  /dev/snd/seq: ubuntu 1597 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Mon Mar 23 05:41:57 2026 DistributionChannelDescriptor:  # This is the distribution channel descriptor for Ubuntu 24.04 for Dell  # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor  canonical-oem-somerville-noble-oem-24.04b-proposed-20241224-151 InstallationDate: Installed on 2026-03-04 (19 days ago) InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20241223) IwConfig:  lo no wireless extensions.  enx00e04ca9f5c8 no wireless extensions.  wlp0s20f3 no wireless extensions. MachineType: Dell Inc. XPS 13 9350 ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=screen-256color ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1014-oem root=UUID=6acf835d-3bec-4909-9cf9-8848785f287d ro quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-6.17.0-1014-oem N/A  linux-backports-modules-6.17.0-1014-oem N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.26 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2024 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 07NFRM dmi.board.vendor: Dell Inc. dmi.board.version: X05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/06/2024:br1.7:efr1.16:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07NFRM:rvrX05:cvnDellInc.:ct10:cvr:sku0CC9: dmi.product.family: XPS dmi.product.name: XPS 13 9350 dmi.product.sku: 0CC9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2145171/+subscriptions