[Bug 2158928] [NEW] Thinkpad T14 gen4 AMD: Frequent kernel panics on boot since 7.0.0-22

Public bug reported: I experience random kernel panic and lock on boot since kernel 7.0.0-22 at least, but happens also on 7.0.0-27. The kernel 7.0.0-15 seems to be fine but it would require multiple reboots. Jul 01 21:10:11 earl kernel: INFO: task kworker/u64:6:187 blocked for more than 122 seconds. Jul 01 21:10:11 earl kernel: Not tainted 7.0.0-27-generic #27-Ubuntu Jul 01 21:10:11 earl kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 01 21:10:11 earl kernel: task:kworker/u64:6 state:D stack:0 pid:187 tgid:187 ppid:2 task_flags:0x4208060 flags:0x00080000 Jul 01 21:10:11 earl kernel: Workqueue: pm pm_runtime_work Jul 01 21:10:11 earl kernel: Call Trace: Jul 01 21:10:11 earl kernel: <TASK> Jul 01 21:10:11 earl kernel: __schedule+0x2b2/0x630 Jul 01 21:10:11 earl kernel: schedule+0x27/0x90 Jul 01 21:10:11 earl kernel: schedule_timeout+0xcf/0x110 Jul 01 21:10:11 earl kernel: wait_for_completion+0x81/0x140 Jul 01 21:10:11 earl kernel: __flush_work+0x270/0x3c0 Jul 01 21:10:11 earl kernel: ? __pfx_wq_barrier_func+0x10/0x10 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: flush_work+0x21/0x30 Jul 01 21:10:11 earl kernel: tb_ring_stop+0xd9/0x200 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_switch_suspend+0x167/0x1b0 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_ctl_stop+0x3c/0x100 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_runtime_suspend+0x5c/0x70 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_domain_runtime_suspend+0x3a/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: nhi_runtime_suspend+0x1f/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: pci_pm_runtime_suspend+0x6a/0x1a0 Jul 01 21:10:11 earl kernel: __rpm_callback+0x4b/0x1f0 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: ? ktime_get_mono_fast_ns+0x36/0xe0 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: rpm_callback+0x77/0x80 Jul 01 21:10:11 earl kernel: rpm_suspend+0xe1/0x610 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: rpm_idle+0x247/0x360 Jul 01 21:10:11 earl kernel: pm_runtime_work+0x8d/0xa0 Jul 01 21:10:11 earl kernel: process_one_work+0x1ac/0x3d0 Jul 01 21:10:11 earl kernel: worker_thread+0x1b8/0x360 Jul 01 21:10:11 earl kernel: ? __pfx_worker_thread+0x10/0x10 Jul 01 21:10:11 earl kernel: kthread+0xf7/0x130 Jul 01 21:10:11 earl kernel: ? __pfx_kthread+0x10/0x10 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:19:59 2026 InstallationDate: Installed on 2025-04-12 (445 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21K3S0DS00 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x8000 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-19 (43 days ago) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET69W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3S0DS00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR2FET69W(1.49):bd03/19/2026:br1.49:efr1.33:svnLENOVO:pn21K3S0DS00:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3S0DS00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4:pfaThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3S0DS00 dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "kernel_lpxxxx_ubuntu7.0.0-27-boot-freeze.log" https://bugs.launchpad.net/bugs/2158928/+attachment/5979767/+files/kernel_lpxxxx_ubuntu7.0.0-27-boot-freeze.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158928 Title: Thinkpad T14 gen4 AMD: Frequent kernel panics on boot since 7.0.0-22 Status in linux package in Ubuntu: New Bug description: I experience random kernel panic and lock on boot since kernel 7.0.0-22 at least, but happens also on 7.0.0-27. The kernel 7.0.0-15 seems to be fine but it would require multiple reboots. Jul 01 21:10:11 earl kernel: INFO: task kworker/u64:6:187 blocked for more than 122 seconds. Jul 01 21:10:11 earl kernel: Not tainted 7.0.0-27-generic #27-Ubuntu Jul 01 21:10:11 earl kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 01 21:10:11 earl kernel: task:kworker/u64:6 state:D stack:0 pid:187 tgid:187 ppid:2 task_flags:0x4208060 flags:0x00080000 Jul 01 21:10:11 earl kernel: Workqueue: pm pm_runtime_work Jul 01 21:10:11 earl kernel: Call Trace: Jul 01 21:10:11 earl kernel: <TASK> Jul 01 21:10:11 earl kernel: __schedule+0x2b2/0x630 Jul 01 21:10:11 earl kernel: schedule+0x27/0x90 Jul 01 21:10:11 earl kernel: schedule_timeout+0xcf/0x110 Jul 01 21:10:11 earl kernel: wait_for_completion+0x81/0x140 Jul 01 21:10:11 earl kernel: __flush_work+0x270/0x3c0 Jul 01 21:10:11 earl kernel: ? __pfx_wq_barrier_func+0x10/0x10 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: flush_work+0x21/0x30 Jul 01 21:10:11 earl kernel: tb_ring_stop+0xd9/0x200 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_switch_suspend+0x167/0x1b0 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_ctl_stop+0x3c/0x100 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_runtime_suspend+0x5c/0x70 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_domain_runtime_suspend+0x3a/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: nhi_runtime_suspend+0x1f/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: pci_pm_runtime_suspend+0x6a/0x1a0 Jul 01 21:10:11 earl kernel: __rpm_callback+0x4b/0x1f0 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: ? ktime_get_mono_fast_ns+0x36/0xe0 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: rpm_callback+0x77/0x80 Jul 01 21:10:11 earl kernel: rpm_suspend+0xe1/0x610 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: rpm_idle+0x247/0x360 Jul 01 21:10:11 earl kernel: pm_runtime_work+0x8d/0xa0 Jul 01 21:10:11 earl kernel: process_one_work+0x1ac/0x3d0 Jul 01 21:10:11 earl kernel: worker_thread+0x1b8/0x360 Jul 01 21:10:11 earl kernel: ? __pfx_worker_thread+0x10/0x10 Jul 01 21:10:11 earl kernel: kthread+0xf7/0x130 Jul 01 21:10:11 earl kernel: ? __pfx_kthread+0x10/0x10 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:19:59 2026 InstallationDate: Installed on 2025-04-12 (445 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21K3S0DS00 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x8000 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-19 (43 days ago) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET69W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3S0DS00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR2FET69W(1.49):bd03/19/2026:br1.49:efr1.33:svnLENOVO:pn21K3S0DS00:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3S0DS00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4:pfaThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3S0DS00 dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158928/+subscriptions

[Bug 2158286] Re: NFC driver on Thinkpad T14 AMD gen4 causes a lot interrupts

Hi, Gabriela, here it is. on the current 7.0.0-27 journalctl -b 0 -k > kernel_lp2158286_ubuntu7.0.0-27.log $ cat top_ubuntu7.0.0-27.txt top - 19:11:31 up 6 min, 1 user, load average: 4.40, 1.88, 0.89 Tasks: 721 total, 1 running, 720 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.6 us, 3.9 sy, 0.0 ni, 95.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 30209.5 total, 16793.8 free, 5993.6 used, 7629.5 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 24215.9 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 787 root -51 0 0 0 0 S 33.3 0.0 2:03.80 irq/91-+ 4666 root 20 0 0 0 0 I 16.7 0.0 0:00.61 kworker+ 573 root 20 0 0 0 0 I 8.3 0.0 0:00.38 kworker+ 4664 root 20 0 0 0 0 I 8.3 0.0 0:00.97 kworker+ 17210 mastier 20 0 16468 6420 4236 R 8.3 0.0 0:00.02 top 1 root 20 0 28840 19068 11100 S 0.0 0.1 0:03.86 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pool_wo+ 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 7 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ ** Attachment added: "kernel_lp2158286_ubuntu7.0.0-27.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158286/+attachment/5979765/+files/kernel_lp2158286_ubuntu7.0.0-27.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158286 Title: NFC driver on Thinkpad T14 AMD gen4 causes a lot interrupts Status in linux package in Ubuntu: New Bug description: Recently on kernel 7.0.0-generic-22 (after upgrade from 24.04 to 26.04) my fans started to behave quite noisy even in Balanced mode (3000rpm), while in powersaving instead of going down to 0 RPM and still oscilate at 2200RPM level. So I researched and it seems there is NFC driver causing a lot interrupts  mastier@earl:~$ cat /proc/acpi/ibm/fan   status: enabled   speed: 3081   level: auto   mastier@earl:~$ sensors   thinkpad-isa-0000   Adapter: ISA adapter   fan1: 3077 RPM   fan2: 3077 RPM   CPU: +56.0°C ... The interrupts: mastier@earl:~$ top -b -n 1 -o +%CPU | head -n 20 top - 16:57:13 up 5:08, 1 user, load average: 1.13, 1.29, 1.05 Tasks: 736 total, 1 running, 735 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.4 us, 6.7 sy, 0.0 ni, 89.4 id, 0.0 wa, 0.0 hi, 0.6 si, 0.0 st MiB Mem : 30209.5 total, 2540.6 free, 14878.1 used, 10510.9 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 15331.4 avail Mem     PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND   13162 mastier 20 0 28.6g 900176 316932 S 91.7 2.9 16:06.74 firefox     773 root -51 0 0 0 0 S 33.3 0.0 96:47.99 irq/91-+    2186 root 20 0 1423172 57652 25748 S 8.3 0.2 1:55.52 tailsca+  136500 mastier 20 0 16464 6384 4204 R 8.3 0.0 0:00.02 top       1 root 20 0 28836 19296 11248 S 0.0 0.1 0:06.74 systemd       2 root 20 0 0 0 0 S 0.0 0.0 0:00.89 kthreadd       3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pool_wo+ ...  $ grep "91:" /proc/interrupts   91: 0 0 0 0 0 834177081 0 0 0 0 0 0 0 0 0 0 amd_gpio 84 nxp-nci_i2c ```` so I unloaded this driver temporarily and now it looks better sudo rmmod nxp_nci_i2c sudo rmmod nxp_nci now looks better mastier@earl:~$ top -b -n 1 -o +%CPU | head -n 20 top - 17:14:56 up 5:26, 1 user, load average: 1.15, 0.92, 0.95 Tasks: 734 total, 1 running, 733 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.6 us, 1.6 sy, 0.0 ni, 94.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 30209.5 total, 1952.3 free, 15122.9 used, 10699.8 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 15086.6 avail Mem     PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND  148217 mastier 20 0 16464 6384 4204 R 16.7 0.0 0:00.03 top    8911 mastier 20 0 10.9g 423028 205996 S 8.3 1.4 24:40.69 gnome-s+   16791 mastier 20 0 2716908 131808 77456 S 8.3 0.4 0:45.95 Isolate+       1 root 20 0 28836 19296 11248 S 0.0 0.1 0:06.83 systemd       2 root 20 0 0 0 0 S 0.0 0.0 0:00.93 kthreadd       3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pool_wo+       4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       7 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+      10 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+      13 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ It seems to be the result of the following regression: https://patchew.org/linux/20260519-nfc-nxp-nci-i2c-restore-irq-trigger-fallback-v4-1-8580d8e18016@amd.com/ https://patchew.org/linux/20260511082611.12721-1-bartosz.golaszewski@oss.qualcomm.com/ also relevant thread: https://bbs.archlinux.org/viewtopic.php?id=312733 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 17:03:23 2026 InstallationDate: Installed on 2025-04-12 (439 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21K3S0DS00 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x8000 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-19 (37 days ago) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET69W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3S0DS00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR2FET69W(1.49):bd03/19/2026:br1.49:efr1.33:svnLENOVO:pn21K3S0DS00:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3S0DS00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4:pfaThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3S0DS00 dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158286/+subscriptions

[Bug 2158920] Re: noble-stable-2026-06-16 dropped a bracket causing FTBFS

** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Alice C. Munduruca (cremfuelled) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158920 Title: noble-stable-2026-06-16 dropped a bracket causing FTBFS Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: [ Impact ] Azure kernels have recently been seeing FTBFS' due to a broken change introduced by upstream stable. Configs in that kernel bring out a compilation error due to a broken patch I adjusted in noble- stable-2026-06-16. [ Test Plan ] Kernel should compile properly after patch application. [ Where problems could occur ] Since the previous state was already a regression, there is no real risk of getting much worse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158920/+subscriptions

[Bug 2158920] [NEW] noble-stable-2026-06-16 dropped a bracket causing FTBFS

Public bug reported: [ Impact ] Azure kernels have recently been seeing FTBFS' due to a broken change introduced by upstream stable. Configs in that kernel bring out a compilation error due to a broken patch I adjusted in noble- stable-2026-06-16. [ Test Plan ] Kernel should compile properly after patch application. [ Where problems could occur ] Since the previous state was already a regression, there is no real risk of getting much worse. ** Affects: linux (Ubuntu) Importance: High Assignee: Alice C. Munduruca (cremfuelled) Status: Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158920 Title: noble-stable-2026-06-16 dropped a bracket causing FTBFS Status in linux package in Ubuntu: Confirmed Bug description: [ Impact ] Azure kernels have recently been seeing FTBFS' due to a broken change introduced by upstream stable. Configs in that kernel bring out a compilation error due to a broken patch I adjusted in noble- stable-2026-06-16. [ Test Plan ] Kernel should compile properly after patch application. [ Where problems could occur ] Since the previous state was already a regression, there is no real risk of getting much worse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158920/+subscriptions

[Bug 2065059] Re: kernel selftest powerpc/math:fpu_preempt consistently timeouts

*** This bug is a duplicate of bug 2141536 *** https://bugs.launchpad.net/bugs/2141536 ** This bug has been marked a duplicate of bug 2141536 Some powerpc test from ubuntu_kernel_selftests timeout with 45 seconds -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2065059 Title: kernel selftest powerpc/math:fpu_preempt consistently timeouts Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux source package in Oracular: Won't Fix Bug description: [Impact] ubuntu_kernel_selftests.powerpc/math:fpu_preempt consistently fails on ppc64el: ... # timeout set to 45 # selftests: powerpc: fpu_preempt # test: fpu_preempt # tags: git_version:Ubuntu-6.8.0-32.32-0-g227b79edaa92 # Waiting for all workers to start...done # Waiting for 60 seconds to let some workers get preempted...done # Stopping workers...done # not ok 1 selftests: powerpc: fpu_preempt # TIMEOUT 45 seconds ... [Fix] Apply the attached fix to bump the timeout back to 300. # timeout set to 300 # selftests: powerpc/math: fpu_preempt # test: fpu_preempt # tags: git_version:Ubuntu-6.8.0-32.32-0-g227b79edaa92 # Waiting for all workers to start...done # Waiting for 60 seconds to let some workers get preempted...done # Stopping workers...done # success: fpu_preempt ok 1 selftests: powerpc/math: fpu_preempt [How to test] Rerun the test after applying the fix. [Regression potential] None, we are just bumping the timeout for a single test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065059/+subscriptions

[Bug 2156830] Re: Fix missing audio output device on Dell Slate HPT platform

This bug was fixed in the package linux-oem-6.17 - 6.17.0-1028.28 --------------- linux-oem-6.17 (6.17.0-1028.28) noble; urgency=medium * noble/linux-oem-6.17: 6.17.0-1028.28 -proposed tracker (LP: #2158224) * [SRU]Enable Realtek ALC287 + Cirrus CS35L56 Audio for Lenovo Yoga Pro 7 (LP: #2156867) - ALSA: hda/realtek: ALC269 fixup for Lenovo Yoga Pro 7 15ASH111 audio - ALSA: hda/realtek:ALC269 fixup for Yoga Pro 7 15ASH11 mic mute LED - ASoC: amd: acp: add DMI override for ACP70 flag - ASoC: amd: acp: Add DMI quirk for Lenovo Yoga Pro 7 15ASH11 * Fix missing audio output device on Dell Slate HPT platform (LP: #2156830) - ASoC: amd: acp: Add ACP6.3 match entries for Cirrus Logic parts * MIPI camera of a BBG809N3A_B sensor SKU of the DELL Pro 14 Premium PA14260 renders upside-down (LP: #2155837) - SAUCE: media: ipu-bridge: correct platform handling for DELL Pro 14 Premium PA14260 * Fix no audio from right built-in speaker on HP ZBook with TAS2781 amplifier (LP: #2156556) - ALSA: hda/tas2781: Fix device-0 reset issue and handle -EXDEV in block data processing * Audio shows Dummy Output on systems with Cirrus Logic cs42l43 codec (LP: #2156313) - SAUCE: ASoC: sdw_utils: fix missing component_name for cs42l43 part_id 0x2A3B * [SRU] Correct FIXED_VS Link Rate Toggle Condition (LP: #2155619) - drm/amd/display: Correct FIXED_VS Link Rate Toggle Condition * Internal display black screen on Intel Lunar Lake with eDP panel (LP: #2156312) - drm/i915/alpm: Allow LOBF only for platform that have Always on VRR TG -- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Thu, 25 Jun 2026 13:35:25 +0800 ** Changed in: linux-oem-6.17 (Ubuntu Noble) 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/2156830 Title: Fix missing audio output device on Dell Slate HPT platform Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: Fix Released Status in linux-firmware source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] New Dell Slate HPT platform with CirrusLogic audio solution will have no basic audio functions w/o ACP6.3 match entries. ================ Linux Kernel ======================== [Fix] Backport upstream fix fd13fc700e3e ("ASoC: amd: acp: Add ACP6.3 match entries for Cirrus Logic parts") ================ linux-firmware ======================== [Fix] Backport upstream fix [1]: cirrus: cs42l45: Update CS42L45 SDCA codec firmware for Dell laptops (!1094) · Merge requests · kernel-firmware / Linux Firmware · GitLab [2]: cirrus: cs35l63: Add Cirrus CS35L63 firmware mappings for various Dell laptops - kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel [Test Case] 1. Boot up the machine of new Dell Slate HPT platform. 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 `aplay` basic speaker play functions. [Where problems could occur] The commit simply add ACP 6.3 entries for CirrusLogic codecs. No regression expected at the current stage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156830/+subscriptions

[Bug 2156867] Re: [SRU]Enable Realtek ALC287 + Cirrus CS35L56 Audio for Lenovo Yoga Pro 7

This bug was fixed in the package linux-oem-6.17 - 6.17.0-1028.28 --------------- linux-oem-6.17 (6.17.0-1028.28) noble; urgency=medium * noble/linux-oem-6.17: 6.17.0-1028.28 -proposed tracker (LP: #2158224) * [SRU]Enable Realtek ALC287 + Cirrus CS35L56 Audio for Lenovo Yoga Pro 7 (LP: #2156867) - ALSA: hda/realtek: ALC269 fixup for Lenovo Yoga Pro 7 15ASH111 audio - ALSA: hda/realtek:ALC269 fixup for Yoga Pro 7 15ASH11 mic mute LED - ASoC: amd: acp: add DMI override for ACP70 flag - ASoC: amd: acp: Add DMI quirk for Lenovo Yoga Pro 7 15ASH11 * Fix missing audio output device on Dell Slate HPT platform (LP: #2156830) - ASoC: amd: acp: Add ACP6.3 match entries for Cirrus Logic parts * MIPI camera of a BBG809N3A_B sensor SKU of the DELL Pro 14 Premium PA14260 renders upside-down (LP: #2155837) - SAUCE: media: ipu-bridge: correct platform handling for DELL Pro 14 Premium PA14260 * Fix no audio from right built-in speaker on HP ZBook with TAS2781 amplifier (LP: #2156556) - ALSA: hda/tas2781: Fix device-0 reset issue and handle -EXDEV in block data processing * Audio shows Dummy Output on systems with Cirrus Logic cs42l43 codec (LP: #2156313) - SAUCE: ASoC: sdw_utils: fix missing component_name for cs42l43 part_id 0x2A3B * [SRU] Correct FIXED_VS Link Rate Toggle Condition (LP: #2155619) - drm/amd/display: Correct FIXED_VS Link Rate Toggle Condition * Internal display black screen on Intel Lunar Lake with eDP panel (LP: #2156312) - drm/i915/alpm: Allow LOBF only for platform that have Always on VRR TG -- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Thu, 25 Jun 2026 13:35:25 +0800 ** Changed in: linux-oem-6.17 (Ubuntu Noble) 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/2156867 Title: [SRU]Enable Realtek ALC287 + Cirrus CS35L56 Audio for Lenovo Yoga Pro 7 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux-oem-7.0 source package in Noble: Invalid Status in linux source package in Resolute: In Progress Status in linux-firmware source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: Fix Released Status in linux source package in Stonking: In Progress Status in linux-firmware source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [ Impact ] Users running Ubuntu on newer Lenovo Yoga Pro 7 laptops experience critical audio subsystem degradation. The three primary failure points are: * Critically Low Speaker Volume: Sound output through the built-in speaker array is barely audible, even when userspace volume sliders are set to 100%. While the host Realtek ALC287 codec initializes, its companion Cirrus Logic CS35L56 smart amplifiers default to an uncalibrated, low-power fallback state ("FIRMWARE_MISSING") because the system lacks their manufacturer-supplied hardware-tuning profiles. * Non-Functional Speaker-Mute Keyboard LED: Pressing the F1 Audio Mute key on the keyboard toggles the stream status within PulseAudio/PipeWire correctly, but the physical amber LED hardware indicator on the keycap fails to illuminate. The software mute state is disconnected from the motherboard's GPIO controller. * Missing/Dead Microphone Array: The system completely fails to register or capture audio via the internal digital microphone array. The default driver stack attempts to locate the DMIC components on a digital sub-link connected directly to the main processor's AMD ACP block, whereas Lenovo routed the microphone hardware channels through the primary Realtek codec pins. [ Fix ] * Kernel Driver Fixes  - fc12cf16df9a ("ASoC: amd: acp: Add DMI quirk for Lenovo Yoga Pro 7 15ASH11") - d0426510a9e1 ("ASoC: amd: acp: add DMI override for ACP70 flag")  - 17065203e1bc ("ALSA: hda/realtek:ALC269 fixup for Yoga Pro 7 15ASH11 mic mute LED")  - 83dca2530fb3 ("ALSA: hda/realtek: ALC269 fixup for Lenovo Yoga Pro 7 15ASH111 audio") * Firmware Environment Fixes  - d33a9c6d7661 ("cirrus: cs35l56: Update firmware for Cirrus Amps for a couple of Lenovo laptops")  - 604cb45fbe6d ("cirrus: cs35l56: Add firmware for Cirrus Amps for some Lenovo laptops")  - cc2cb17f5ed9 ("cirrus: cs35l56: Add firmware for Cirrus Amps for some ASUS laptops")  - 1d57ec2fdc3f ("cirrus: cs35l56: Add firmware for Cirrus Amps for some Lenovo laptops")  - 0c9b82b60972 ("cirrus: Add cs35l56 firmware symlinks for Asus UM5606KA") [ Test Plan ] Install the patched kernel package and updated linux-firmware payload on an affected Lenovo Yoga Pro 7, then reboot to check: 1. Verify Amp Calibration & Speaker Volume:   Play an audio stream at a standard volume level (30–50%). Confirm it produces crisp, loudly scaled audio. 2. Verify Microphone Capture:    Open Ubuntu Settings -> Sound -> Input. Confirm that the ghost "Digital Microphone" tied to the AMD ACP is gone, and a functioning Internal Stereo Microphone device is present.  Speak or tap on the chassis to confirm that the input visualizer bar responds dynamically to incoming audio data. 3 Verify Mute LED and Mic LED Illumination:    Press the physical F1/F4 Mute hotkey. The amber LED light on the keycap must illuminate immediately when muted, and cleanly shut off as soon as the system is unmuted. [ Where problems could occur ] Scope of Regression: Extremely isolated. All changes are heavily guarded behind rigid DMI string check loops inside vendor-specific sub-drivers (AMD ACP matching tables, Realtek HDA quirk lists, and specific sub-hardware ID firmware loading paths). Systems built by other vendors (such as Dell, HP, or ASUS) or other laptop lines will bypass these conditional rules entirely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156867/+subscriptions

[Bug 2158377] Re: ext4: writeback causes kernel oops when low on space

This bug was fixed in the package linux - 6.8.0-134.134 --------------- linux (6.8.0-134.134) noble; urgency=medium * noble/linux: 6.8.0-134.134 -proposed tracker (LP: #2158432) * ext4: writeback causes kernel oops when low on space (LP: #2158377) - ext4: get rid of ppath in get_ext_path() linux (6.8.0-131.131) noble; urgency=medium * noble/linux: 6.8.0-131.131 -proposed tracker (LP: #2157196) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts * CVE-2026-46244 - netfilter: nft_inner: Fix IPv6 inner_thoff desync * CVE-2026-43185 - ksmbd: fix signededness bug in smb_direct_prepare_negotiation() * CVE-2026-46289 - lib/scatterlist: fix length calculations in extract_kvec_to_sg * CVE-2026-46119 - libceph: Fix slab-out-of-bounds access in auth message processing * CVE-2026-46135 - nvmet-tcp: fix race between ICReq handling and queue teardown * CVE-2026-46185 - smb/client: fix out-of-bounds read in symlink_data() * CVE-2026-46195 - smb: client: validate dacloffset before building DACL pointers * CVE-2026-46115 - block: add pgmap check to biovec_phys_mergeable * CVE-2026-43501 - ipv6: rpl: reserve mac_len headroom when recompressed SRH grows * CVE-2026-45988 - rxrpc: Fix re-decryption of RESPONSE packets * CVE-2026-46043 - RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv * CVE-2026-43493 - crypto: pcrypt - Fix handling of MAY_BACKLOG requests * CVE-2026-43071 - dcache: Limit the minimal number of bucket to two * CVE-2026-31685 - netfilter: ip6t_eui64: reject invalid MAC header for all packets * CVE-2026-43117 - btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() * CVE-2026-43114 - netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry * CVE-2026-31607 - usbip: validate number_of_packets in usbip_pack_ret_submit() * CVE-2026-31659 - batman-adv: reject oversized global TT response buffers * CVE-2026-31649 - net: stmmac: fix integer underflow in chain mode * CVE-2026-31657 - batman-adv: hold claim backbone gateways by reference * CVE-2026-31637 - rxrpc: reject undecryptable rxkad response tickets * CVE-2026-31669 - mptcp: fix slab-use-after-free in __inet_lookup_established * CVE-2026-31668 - seg6: separate dst_cache for input and output paths in seg6 lwtunnel * CVE-2026-43011 - net/x25: Fix potential double free of skb * CVE-2026-43037 - ip6_tunnel: clear skb2->cb[] in ip4ip6_err() * CVE-2026-43341 - net/ipv6: ioam6: prevent schema length wraparound in trace fill * CVE-2026-43038 - ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() * CVE-2026-31682 - bridge: br_nd_send: linearize skb before parsing ND options * CVE-2026-31436 - dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() * CVE-2026-43384 - net/tcp-ao: Fix MAC comparison to be constant-time * CVE-2026-31448 - ext4: get rid of ppath in ext4_find_extent() - ext4: get rid of ppath in ext4_ext_create_new_leaf() - ext4: get rid of ppath in ext4_ext_insert_extent() - ext4: avoid infinite loops caused by residual data * CVE-2026-31478 - ksmbd: replace hardcoded hdr2_len with offsetof() in smb2_calc_max_out_buf_len() * CVE-2026-23428 - ksmbd: fix use-after-free of share_conf in compound request * CVE-2026-23450 - net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() * CVE-2026-23455 - netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() * CVE-2026-31402 - nfsd: fix heap overflow in NFSv4.0 LOCK replay cache * CVE-2026-43383 - net/tcp-md5: Fix MAC comparison to be constant-time * CVE-2026-43378 - smb: server: fix use-after-free in smb2_open() * CVE-2026-46243 - smb: client: reject userspace cifs.spnego descriptions * CVE-2026-43414 - scsi: qla2xxx: Completely fix fcport double free * CVE-2026-43407 - libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() * CVE-2026-43406 - libceph: prevent potential out-of-bounds reads in process_message_header() -- Manuel Diewald <manuel.diewald@canonical.com> Fri, 26 Jun 2026 17:31:04 +0200 ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** CVE added: https://cve.org/CVERecord?id=CVE-2026-23428 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-23450 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-23455 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31402 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31436 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31448 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31478 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31607 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31637 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31649 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31657 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31659 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31668 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31669 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31682 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31685 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43011 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43037 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43038 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43071 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43114 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43117 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43185 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43341 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43378 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43383 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43384 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43406 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43407 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43414 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43493 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-43501 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-45988 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46043 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46115 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46119 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46135 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46185 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46195 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46243 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46244 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-46289 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158377 Title: ext4: writeback causes kernel oops when low on space Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: SRU Justification: [Impact] The noble upstream stable patchset 2026-05-28 (LP: #2154496) introduced refactoring patches targeting ext4 code, originating from upstream stable branch linux-6.6.y. During regression testing of the generic noble kernel, the ltp tests mmap14 and mmap16 were observed to fail, causing a kernel oops. Through bisecting, upstream commit f7d1331f16a8 ("ext4: get rid of ppath in ext4_ext_insert_extent()") was found to be cause. This commit was the first in the refactoring series of commits targeting ext4 in v6.6.130. The following stacktrace was recorded on an arm64 openstack instance: [ 1194.380996] Unable to handle kernel paging request at virtual address ffffffffffffffec [ 1194.381993] Mem abort info: [ 1194.382451] ESR = 0x0000000096000004 [ 1194.382950] EC = 0x25: DABT (current EL), IL = 32 bits [ 1194.383615] SET = 0, FnV = 0 [ 1194.384067] EA = 0, S1PTW = 0 [ 1194.384534] FSC = 0x04: level 0 translation fault [ 1194.385143] Data abort info: [ 1194.385626] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 1194.386310] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 1194.387026] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 1194.391322] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000cc641000 [ 1194.393554] [ffffffffffffffec] pgd=0000000000000000, p4d=0000000000000000 [ 1194.394958] Internal error: Oops: 0000000096000004 [#1] SMP [ 1194.395660] Modules linked in: brd overlay exfat bcachefs lz4hc_compress lz4_compress xfs sctp ip6_udp_tunnel udp_tunnel nfsd auth_rpcgss nfs_acl lockd grace sunrpc tls qrtr cfg80211 binfmt_misc nls_iso8859_1 input_leds sch_fq_codel dm_multipath efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 hid_generic usbhid hid btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_arm64 virtio_gpu arm_smccc_trng sha1_ce virtio_rng virtio_dma_buf xhci_pci xhci_pci_renesas aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [last unloaded: init_module(OE)] [ 1194.405523] CPU: 1 PID: 95 Comm: kworker/u6:1 Tainted: G OE 6.8.0-132-generic #133-Ubuntu [ 1194.407319] Hardware name: QEMU KVM Virtual Machine, BIOS 2025.02-8~22.04.0~ppa3 05/14/2025 [ 1194.408502] Workqueue: writeback wb_workfn (flush-7:0) [ 1194.409343] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1194.410263] pc : ext4_ext_map_blocks+0x2a0/0xa18 [ 1194.410979] lr : ext4_ext_map_blocks+0x8e8/0xa18 [ 1194.411685] sp : ffff8000803db600 [ 1194.412280] x29: ffff8000803db6a0 x28: 0000000000000ee8 x27: ffff0000c3641280 [ 1194.413248] x26: ffff0000cb20b000 x25: ffffffffffffffe4 x24: 000000000000042f [ 1194.414196] x23: ffff0000c286bc40 x22: ffff0000c36413a8 x21: ffff8000803db948 [ 1194.415141] x20: 0000000000000008 x19: 0000000000000000 x18: ffff800080381078 [ 1194.416131] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 1194.417083] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 1194.418051] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa6fb00b8227c [ 1194.419026] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000 [ 1194.419949] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 1194.420897] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 [ 1194.421851] Call trace: [ 1194.422404] ext4_ext_map_blocks+0x2a0/0xa18 [ 1194.423106] ext4_map_blocks+0x1c4/0x650 [ 1194.423755] mpage_map_one_extent+0x7c/0x1e0 [ 1194.424456] mpage_map_and_submit_extent+0x94/0x428 [ 1194.425196] ext4_do_writepages+0x6c0/0x7d8 [ 1194.425883] ext4_writepages+0x88/0x128 [ 1194.426570] do_writepages+0x98/0x210 [ 1194.427222] __writeback_single_inode+0x50/0x390 [ 1194.427947] writeback_sb_inodes+0x230/0x4d8 [ 1194.428666] wb_writeback+0x128/0x410 [ 1194.429324] wb_do_writeback+0xb4/0x398 [ 1194.429998] wb_workfn+0x80/0x258 [ 1194.430604] process_one_work+0x17c/0x448 [ 1194.431289] worker_thread+0x1bc/0x3a0 [ 1194.431923] kthread+0xf8/0x110 [ 1194.432533] ret_from_fork+0x10/0x20 [ 1194.433178] Code: b9003fe2 f94023f9 b9000ea0 b4001a39 (79401337) [ 1194.434077] ---[ end trace 0000000000000000 ]--- The crash is triggered during normal writeback when the filesystem is low on space. Any workload that writes to ext4 with unwritten (preallocated/fallocated) extents under space pressure can hit this. It is fatal to the affected writeback worker thread. [Explanation] The kernel crash (oops) occurs during ext4 writeback in `ext4_ext_map_blocks()` when the filesystem encounters an ENOSPC (no space left on device) condition while handling unwritten extents. The crash manifests as a page fault at address `0xffffffffffffffec` (which is `ERR_PTR(-ENOSPC) + 8`) on arm64, triggered from a writeback worker thread. The ext4 extent code underwent a significant refactoring series that changed how extent path objects are passed between functions. Previously, functions used double-pointer (`struct ext4_ext_path **ppath`) semantics — on error, the callee would set `*ppath = NULL`, ensuring the caller never held a dangling or invalid pointer. The refactoring changed these functions to return the path directly (or `ERR_PTR` on error). After this refactoring, functions like `ext4_ext_handle_unwritten_extents()` and `ext4_ext_insert_extent()` return `ERR_PTR(-ENOSPC)` on failure. The caller (`ext4_ext_map_blocks`) stores this error pointer in its local `path` variable and jumps to its cleanup label, where `ext4_free_ext_path(path)` is called. However, `ext4_free_ext_path()` was never updated to handle `ERR_PTR` values — it only had a NULL check. As a result, it attempts to dereference the error pointer (specifically reading `path->p_depth`), causing the kernel page fault. [Fix] Cherry-pick this missing prerequisite patch: 6b854d552711 ("ext4: get rid of ppath in get_ext_path()"). This patch adds `IS_ERR_OR_NULL()` guards to both `ext4_ext_drop_refs()` and `ext4_free_ext_path()`. This teaches these cleanup functions to gracefully handle error pointers by returning immediately, which is necessary now that the refactored call chain can leave `path` set to an `ERR_PTR` value when reaching cleanup code. [Test Plan] Run the ltp tests mmap14 and mmp16 that reliably trigger the crash. The tests should complete successfully without triggering a kernel crash. [Where problems could occur] If problems with this fix were to occur, they would manifest as silent memory leaks in ext4 extent handling - specifically, any code path that previously relied on `ext4_free_ext_path()` to actually free a valid path object but now mistakenly passes an `IS_ERR()` value would silently skip the free and leak the already-freed (or never-allocated) path, making such bugs harder to detect rather than causing a visible crash. Conversely, if any code path were to accidentally store an `ERR_PTR` in a path variable that is later reused (rather than cleaned up), the `IS_ERR_OR_NULL` guard would mask what should be a loud failure, potentially leading to subtle use-after-free or NULL-dereference bugs downstream when that variable is subsequently passed to `ext4_find_extent()` for recycling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158377/+subscriptions

[Bug 2158818] [NEW] SOF IPC4 topology ABI mismatch causes DSP crash (EHOSTDOWN) — regression in 7.0.0-22

Public bug reported: On ASUS Zenbook UX3405MA (Intel Core Ultra 7 155H / Meteor Lake-P), kernel versions 7.0.0-22 and 7.0.0-27 crash the SOF DSP on first audio playback attempt, making all wired audio (headphones, speakers) permanently silent until reboot. Bluetooth audio is unaffected. Hardware is confirmed good (Windows works; Ubuntu 26.04 live CD with kernel 7.0.0-14 works). Root cause: The installed firmware-sof-signed 2025.12.2-1 provides IPC4 topology files with ABI version 3:29:1. The kernel SOF driver reports its supported ABI as 3:23:1 and logs: sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1 On kernel 7.0.0-14 (confirmed from live CD) this mismatch is handled gracefully and audio works. Starting with 7.0.0-22, the kernel's IPC4 topology parser sends malformed pipeline configuration to the DSP firmware when it encounters the newer ABI, causing the DSP to crash. All subsequent playback returns -EHOSTDOWN. The DSP crash is confirmed via debugfs: - /sys/kernel/debug/sof/fw_state — empty (cleared after crash) - /sys/kernel/debug/sof/fw_version — empty - /sys/kernel/debug/sof/exception — non-zero binary crash dump - /sys/kernel/debug/sof/fw_regs — first dword = 0x05 (exception state) Steps to reproduce: 1. Install Ubuntu 26.04 with firmware-sof-signed 2025.12.2-1 (default) 2. Boot kernel 7.0.0-22 or 7.0.0-27 on affected hardware 3. Attempt any audio playback 4. Observe: Playback open error: -112, Host is down; all subsequent playback attempts also fail with EHOSTDOWN until reboot Expected behaviour: The SOF driver should handle a topology file with a newer minor ABI version gracefully — parsing only the fields it understands (as done in 7.0.0-14) — without crashing the DSP. Workaround: Patching the 2-byte minor version field in /lib/firmware/intel/sof-ipc4-tplg/sof-hda-generic-2ch.tplg at offset 0x96 from 0x1d 0x00 (29) to 0x17 0x00 (23) causes the kernel to apply the 3:23:1 parsing path and audio works correctly on both 7.0.0-22 and 7.0.0-27. Hardware: ASUS Zenbook UX3405MA, Intel Core Ultra 7 155H (Meteor Lake-P), ALC294 HDA codec (SSID 1043:1A63), CS35L41 speaker amps (SPI, SSID 10431A63) Affected kernels: 7.0.0-22-generic, 7.0.0-27-generic Working kernel: 7.0.0-14-generic (via live CD) firmware-sof-signed: 2025.12.2-1 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jens 10150 F.... pipewire jens 10170 F.... wireplumber /dev/snd/seq: jens 10150 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 30 22:31:56 2026 InstallationDate: Installed on 2026-02-04 (146 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UX3405MA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5adc1058-8261-4c9f-877c-899756f0d609 ro quiet splash acpi_enforce_resources=lax crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-16 (45 days ago) dmi.bios.date: 06/06/2025 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3405MA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3405MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3405MA.311:bd06/06/2025:br5.32:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UX3405MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3405MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UX3405MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158818 Title: SOF IPC4 topology ABI mismatch causes DSP crash (EHOSTDOWN) — regression in 7.0.0-22 Status in linux package in Ubuntu: New Bug description: On ASUS Zenbook UX3405MA (Intel Core Ultra 7 155H / Meteor Lake-P), kernel versions 7.0.0-22 and 7.0.0-27 crash the SOF DSP on first audio playback attempt, making all wired audio (headphones, speakers) permanently silent until reboot. Bluetooth audio is unaffected. Hardware is confirmed good (Windows works; Ubuntu 26.04 live CD with kernel 7.0.0-14 works). Root cause: The installed firmware-sof-signed 2025.12.2-1 provides IPC4 topology files with ABI version 3:29:1. The kernel SOF driver reports its supported ABI as 3:23:1 and logs: sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1 On kernel 7.0.0-14 (confirmed from live CD) this mismatch is handled gracefully and audio works. Starting with 7.0.0-22, the kernel's IPC4 topology parser sends malformed pipeline configuration to the DSP firmware when it encounters the newer ABI, causing the DSP to crash. All subsequent playback returns -EHOSTDOWN. The DSP crash is confirmed via debugfs: - /sys/kernel/debug/sof/fw_state — empty (cleared after crash) - /sys/kernel/debug/sof/fw_version — empty - /sys/kernel/debug/sof/exception — non-zero binary crash dump - /sys/kernel/debug/sof/fw_regs — first dword = 0x05 (exception state) Steps to reproduce: 1. Install Ubuntu 26.04 with firmware-sof-signed 2025.12.2-1 (default) 2. Boot kernel 7.0.0-22 or 7.0.0-27 on affected hardware 3. Attempt any audio playback 4. Observe: Playback open error: -112, Host is down; all subsequent playback attempts also fail with EHOSTDOWN until reboot Expected behaviour: The SOF driver should handle a topology file with a newer minor ABI version gracefully — parsing only the fields it understands (as done in 7.0.0-14) — without crashing the DSP. Workaround: Patching the 2-byte minor version field in /lib/firmware/intel/sof-ipc4-tplg/sof-hda-generic-2ch.tplg at offset 0x96 from 0x1d 0x00 (29) to 0x17 0x00 (23) causes the kernel to apply the 3:23:1 parsing path and audio works correctly on both 7.0.0-22 and 7.0.0-27. Hardware: ASUS Zenbook UX3405MA, Intel Core Ultra 7 155H (Meteor Lake-P), ALC294 HDA codec (SSID 1043:1A63), CS35L41 speaker amps (SPI, SSID 10431A63) Affected kernels: 7.0.0-22-generic, 7.0.0-27-generic Working kernel: 7.0.0-14-generic (via live CD) firmware-sof-signed: 2025.12.2-1 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jens 10150 F.... pipewire jens 10170 F.... wireplumber /dev/snd/seq: jens 10150 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 30 22:31:56 2026 InstallationDate: Installed on 2026-02-04 (146 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UX3405MA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5adc1058-8261-4c9f-877c-899756f0d609 ro quiet splash acpi_enforce_resources=lax crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-16 (45 days ago) dmi.bios.date: 06/06/2025 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3405MA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3405MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3405MA.311:bd06/06/2025:br5.32:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UX3405MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3405MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UX3405MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158818/+subscriptions

[Bug 2158815] [NEW] Resolute update: v7.0.14 upstream stable release

Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v7.0.14 upstream stable release from git://git.kernel.org/ io_uring/net: Avoid msghdr on op_connect/op_bind async data arm64/entry: Fix arm64-specific rseq brokenness lockd: fix TEST handling when not all permissions are available. firmware: exynos-acpm: Count number of commands in acpm_xfer firmware: exynos-acpm: Count acpm_xfer buffers with __counted_by_ptr firmware: samsung: acpm: Fix cross-thread RX length corruption firmware: samsung: acpm: Fix false timeouts and Use-After-Free in polling firmware: samsung: acpm: Fix missing LKMM barriers in sequence allocator fuse: re-lock request before replacing page cache folio Revert "NFSD: Defer sub-object cleanup in export put callbacks" RDMA/bnxt_re: zero shared page before exposing to userspace bpf: Fix NULL pointer dereference in bpf_sk_storage_clone and diag paths i2c: stub: Reject I2C block transfers with invalid length net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() agp/amd64: Fix broken error propagation in agp_amd64_probe() rose: fix dev_put() leak in rose_loopback_timer() rose: hold loopback neighbour reference across timer callback rose: fix race between loopback timer and module removal rose: clear neighbour pointer after rose_neigh_put() in state machines rose: guard rose_neigh_put() against NULL in timer expiry rose: fix netdev double-hold in rose_rx_call_request() rose: fix notifier unregistered too early in rose_exit() rose: set SOCK_DESTROY in rose_kill_by_device() for prompt cleanup rose: disconnect orphaned STATE_2 sockets when device is gone rose: fix netdev double-hold in rose_make_new() rose: release netdev ref and destroy orphaned incoming sockets rose: drop CALL_REQUEST in loopback timer when device is not running rose: cancel neighbour timers in rose_neigh_put() before freeing rose: clear neighbour pointer in rose_kill_by_device() rose: don't free fd-owned sockets when reaping in the heartbeat net: export netif_open for self_test usage net: net_failover: Fix the deadlock in slave register iio: light: veml6075: add bounds check to veml6075_it_ms index iio: adc: ti-ads1298: add bounds check to pga_settings index crypto: qat - remove unused character device and IOCTLs vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails drivers/base/memory: set mem->altmap after successful device registration ksmbd: reject non-VALID session in compound request branch media: vidtv: fix NULL pointer dereference in vidtv_mux_push_si virtiofs: fix UAF on submount umount Linux 7.0.14 UBUNTU: Upstream stable to v7.0.14 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Resolute) Importance: Medium Assignee: Alice C. Munduruca (cremfuelled) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu Resolute) Assignee: (unassigned) => Alice C. Munduruca (cremfuelled) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v7.0.14 upstream stable release from git://git.kernel.org/ - + io_uring/net: Avoid msghdr on op_connect/op_bind async data + arm64/entry: Fix arm64-specific rseq brokenness + lockd: fix TEST handling when not all permissions are available. + firmware: exynos-acpm: Count number of commands in acpm_xfer + firmware: exynos-acpm: Count acpm_xfer buffers with __counted_by_ptr + firmware: samsung: acpm: Fix cross-thread RX length corruption + firmware: samsung: acpm: Fix false timeouts and Use-After-Free in polling + firmware: samsung: acpm: Fix missing LKMM barriers in sequence allocator + fuse: re-lock request before replacing page cache folio + Revert "NFSD: Defer sub-object cleanup in export put callbacks" + RDMA/bnxt_re: zero shared page before exposing to userspace + bpf: Fix NULL pointer dereference in bpf_sk_storage_clone and diag paths + i2c: stub: Reject I2C block transfers with invalid length + net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() + agp/amd64: Fix broken error propagation in agp_amd64_probe() + rose: fix dev_put() leak in rose_loopback_timer() + rose: hold loopback neighbour reference across timer callback + rose: fix race between loopback timer and module removal + rose: clear neighbour pointer after rose_neigh_put() in state machines + rose: guard rose_neigh_put() against NULL in timer expiry + rose: fix netdev double-hold in rose_rx_call_request() + rose: fix notifier unregistered too early in rose_exit() + rose: set SOCK_DESTROY in rose_kill_by_device() for prompt cleanup + rose: disconnect orphaned STATE_2 sockets when device is gone + rose: fix netdev double-hold in rose_make_new() + rose: release netdev ref and destroy orphaned incoming sockets + rose: drop CALL_REQUEST in loopback timer when device is not running + rose: cancel neighbour timers in rose_neigh_put() before freeing + rose: clear neighbour pointer in rose_kill_by_device() + rose: don't free fd-owned sockets when reaping in the heartbeat + net: export netif_open for self_test usage + net: net_failover: Fix the deadlock in slave register + iio: light: veml6075: add bounds check to veml6075_it_ms index + iio: adc: ti-ads1298: add bounds check to pga_settings index + crypto: qat - remove unused character device and IOCTLs + vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write + serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero + serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails + drivers/base/memory: set mem->altmap after successful device registration + ksmbd: reject non-VALID session in compound request branch + media: vidtv: fix NULL pointer dereference in vidtv_mux_push_si + virtiofs: fix UAF on submount umount Linux 7.0.14 - virtiofs: fix UAF on submount umount - media: vidtv: fix NULL pointer dereference in vidtv_mux_push_si - ksmbd: reject non-VALID session in compound request branch - drivers/base/memory: set mem->altmap after successful device registration - serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero - vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write - crypto: qat - remove unused character device and IOCTLs - iio: adc: ti-ads1298: add bounds check to pga_settings index - iio: light: veml6075: add bounds check to veml6075_it_ms index - net: net_failover: Fix the deadlock in slave register - net: export netif_open for self_test usage - rose: don't free fd-owned sockets when reaping in the heartbeat - rose: clear neighbour pointer in rose_kill_by_device() - rose: cancel neighbour timers in rose_neigh_put() before freeing - rose: drop CALL_REQUEST in loopback timer when device is not running - rose: release netdev ref and destroy orphaned incoming sockets - rose: fix netdev double-hold in rose_make_new() - rose: disconnect orphaned STATE_2 sockets when device is gone - rose: set SOCK_DESTROY in rose_kill_by_device() for prompt cleanup - rose: fix notifier unregistered too early in rose_exit() - rose: fix netdev double-hold in rose_rx_call_request() - rose: guard rose_neigh_put() against NULL in timer expiry - rose: clear neighbour pointer after rose_neigh_put() in state machines - rose: fix race between loopback timer and module removal - rose: hold loopback neighbour reference across timer callback - rose: fix dev_put() leak in rose_loopback_timer() - agp/amd64: Fix broken error propagation in agp_amd64_probe() - net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - i2c: stub: Reject I2C block transfers with invalid length - bpf: Fix NULL pointer dereference in bpf_sk_storage_clone and diag paths - RDMA/bnxt_re: zero shared page before exposing to userspace - Revert "NFSD: Defer sub-object cleanup in export put callbacks" - fuse: re-lock request before replacing page cache folio - firmware: samsung: acpm: Fix missing LKMM barriers in sequence allocator - firmware: samsung: acpm: Fix false timeouts and Use-After-Free in polling - firmware: samsung: acpm: Fix cross-thread RX length corruption - firmware: exynos-acpm: Count acpm_xfer buffers with __counted_by_ptr - firmware: exynos-acpm: Count number of commands in acpm_xfer - lockd: fix TEST handling when not all permissions are available. - arm64/entry: Fix arm64-specific rseq brokenness - io_uring/net: Avoid msghdr on op_connect/op_bind async data + UBUNTU: Upstream stable to v7.0.14 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158815 Title: Resolute update: v7.0.14 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v7.0.14 upstream stable release from git://git.kernel.org/ io_uring/net: Avoid msghdr on op_connect/op_bind async data arm64/entry: Fix arm64-specific rseq brokenness lockd: fix TEST handling when not all permissions are available. firmware: exynos-acpm: Count number of commands in acpm_xfer firmware: exynos-acpm: Count acpm_xfer buffers with __counted_by_ptr firmware: samsung: acpm: Fix cross-thread RX length corruption firmware: samsung: acpm: Fix false timeouts and Use-After-Free in polling firmware: samsung: acpm: Fix missing LKMM barriers in sequence allocator fuse: re-lock request before replacing page cache folio Revert "NFSD: Defer sub-object cleanup in export put callbacks" RDMA/bnxt_re: zero shared page before exposing to userspace bpf: Fix NULL pointer dereference in bpf_sk_storage_clone and diag paths i2c: stub: Reject I2C block transfers with invalid length net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() agp/amd64: Fix broken error propagation in agp_amd64_probe() rose: fix dev_put() leak in rose_loopback_timer() rose: hold loopback neighbour reference across timer callback rose: fix race between loopback timer and module removal rose: clear neighbour pointer after rose_neigh_put() in state machines rose: guard rose_neigh_put() against NULL in timer expiry rose: fix netdev double-hold in rose_rx_call_request() rose: fix notifier unregistered too early in rose_exit() rose: set SOCK_DESTROY in rose_kill_by_device() for prompt cleanup rose: disconnect orphaned STATE_2 sockets when device is gone rose: fix netdev double-hold in rose_make_new() rose: release netdev ref and destroy orphaned incoming sockets rose: drop CALL_REQUEST in loopback timer when device is not running rose: cancel neighbour timers in rose_neigh_put() before freeing rose: clear neighbour pointer in rose_kill_by_device() rose: don't free fd-owned sockets when reaping in the heartbeat net: export netif_open for self_test usage net: net_failover: Fix the deadlock in slave register iio: light: veml6075: add bounds check to veml6075_it_ms index iio: adc: ti-ads1298: add bounds check to pga_settings index crypto: qat - remove unused character device and IOCTLs vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails drivers/base/memory: set mem->altmap after successful device registration ksmbd: reject non-VALID session in compound request branch media: vidtv: fix NULL pointer dereference in vidtv_mux_push_si virtiofs: fix UAF on submount umount Linux 7.0.14 UBUNTU: Upstream stable to v7.0.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158815/+subscriptions

[Bug 2152804] Re: Audient iD4 MkII stops responding after resume from sleep

tried using modprobe snd_usb_audio quirk_flags=2708:0009:force_iface_reset\|iface_delay; but no luck. Interface may need to be included in uac_clock_source_is_valid_quirk() in clock.c -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152804 Title: Audient iD4 MkII stops responding after resume from sleep Status in linux package in Ubuntu: New Bug description: After resuming from suspend, the Audient iD4 MKII audio interface stops working (no sound). Disconnecting/re-connecting the USB cable solves the problem. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat May 16 20:52:12 2026 InstallationDate: Installed on 2020-12-11 (1982 days ago) InstallationMedia: Ubuntu-Studio 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude E5440 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=6113b93f-df6d-4c19-a8d2-875eb03a523c ro usbcore.autosuspend=-1 quiet splash resume=UUID=7b24ab22-c809-4eab-8bec-a55a92ffea7e preempt=full rcu_nocbs=all preempt=full threadirqs rcu_nocbs=all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-15 (2 days ago) dmi.bios.date: 06/13/2019 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 061CGT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd06/13/2019:br65.24:svnDellInc.:pnLatitudeE5440:pvr00:rvnDellInc.:rn061CGT:rvrA00:cvnDellInc.:ct9:cvr:sku05DE:pfa: dmi.product.name: Latitude E5440 dmi.product.sku: 05DE dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152804/+subscriptions

[Bug 2156972] Re: Camera output is vague and color is abnormal

SRU: * https://kernel.ubuntu.com/forgejo/kernel/noble-linux-oem/pulls/435 (oem-6.17) * https://kernel.ubuntu.com/forgejo/kernel/resolute-linux-oem/pulls/10 (oem-7.0) * https://lists.ubuntu.com/archives/kernel-team/2026-June/169646.html (questing, resolute, stonking) ** Description changed: + [SRU Justification] + + [Impact] + + The camera output is abnormal, and it takes longer time to start the camera. + + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error + kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected + + [Fix] + + Upstream commit 477620dccf3e ("media: intel/ipu6: Improve DWC PHY + HSFREQRANGE band selection for overlapping ranges") in v7.2-rc1 fixes + commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY + implementation") from v6.10. + + [Test Plan] + + 1. capture video stream and verify the video quality. + + $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink + location=out.avi + + 2. check no error found in dmesg + + $ sudo dmesg |grep intel_ipu6_isys + + [Where problems could occur] + + The regression can be considered as low, because the patch is meant to + locate a band with higher osc_freq_target for best hardware utilization. + No other part is touched. + + [Other Info] + + While this affects kernels >= v6.10, nominate for all the newer kernels. + And since this is already in v7.2-rc1, skip Unstable. + + ========== original bug report ========== + The camera output is abnormal, and it takes longer time to start the camera. I record the video by command: $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink location=out.avi Some errors reported in the driver: kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected Proposed fix was in https://github.com/intel/ipu6-drivers/pull/447. This affects kernel v6.10 and up, which added D-PHY implementation in commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY implementation"). It's then submitted into upstream as commit 477620dccf3e ("media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges") in v7.2-rc1. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156972 Title: Camera output is vague and color is abnormal Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux-oem-7.0 source package in Noble: Invalid Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux-oem-7.0 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [SRU Justification] [Impact] The camera output is abnormal, and it takes longer time to start the camera. kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected [Fix] Upstream commit 477620dccf3e ("media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges") in v7.2-rc1 fixes commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY implementation") from v6.10. [Test Plan] 1. capture video stream and verify the video quality. $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink location=out.avi 2. check no error found in dmesg $ sudo dmesg |grep intel_ipu6_isys [Where problems could occur] The regression can be considered as low, because the patch is meant to locate a band with higher osc_freq_target for best hardware utilization. No other part is touched. [Other Info] While this affects kernels >= v6.10, nominate for all the newer kernels. And since this is already in v7.2-rc1, skip Unstable. ========== original bug report ========== The camera output is abnormal, and it takes longer time to start the camera. I record the video by command: $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink location=out.avi Some errors reported in the driver: kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected Proposed fix was in https://github.com/intel/ipu6-drivers/pull/447. This affects kernel v6.10 and up, which added D-PHY implementation in commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY implementation"). It's then submitted into upstream as commit 477620dccf3e ("media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges") in v7.2-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156972/+subscriptions

[Bug 2158614] Re: amdgpu: Granite Ridge iGPU gfx ring timeout after Chrome GPU page fault causes gnome-shell SIGABRT and session loss

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158614 Title: amdgpu: Granite Ridge iGPU gfx ring timeout after Chrome GPU page fault causes gnome-shell SIGABRT and session loss Status in linux package in Ubuntu: New Bug description: What happened ============= During a Microsoft Teams video call in Google Chrome, the entire GNOME session was terminated at approximately 09:54 CEST on 2026-06-29. The system did not reboot — the kernel remained running and GDM presented the login screen after the session was lost. Failure sequence (from journalctl -b 0) ============= *** 09:53:56 — Chrome triggers AMD GPU page fault (PERMISSION_FAULTS: read+write denied) kernel: amdgpu 0000:70:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:75) kernel: amdgpu 0000:70:00.0: Process chrome pid 14088 thread chrome:cs0 pid 14114 kernel: amdgpu 0000:70:00.0: in page starting at address 0x000000003f919000 from client 0x1b (UTCL2) kernel: amdgpu 0000:70:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430 kernel: amdgpu 0000:70:00.0: Faulty UTCL2 client ID: SQC (data) (0xa) kernel: amdgpu 0000:70:00.0: PERMISSION_FAULTS: 0x3 *** 09:53:58 — gfx_0.1.0 ring times out; gnome-shell is a victim on the same ring; ring reset fails; full GPU reset triggered kernel: amdgpu 0000:70:00.0: ring gfx_0.1.0 timeout, signaled seq=93148, emitted seq=93149 kernel: amdgpu 0000:70:00.0: Process gnome-shell pid 8975 thread gnome-shel:cs0 pid 8992 kernel: amdgpu 0000:70:00.0: Starting gfx_0.1.0 ring reset kernel: amdgpu 0000:70:00.0: Ring gfx_0.1.0 reset failed kernel: amdgpu 0000:70:00.0: GPU reset begin!. Source: 1 Note: Vulkan was already reporting VK_SUBOPTIMAL_KHR on the swapchain from gnome-text-editor at 09:52:19 and 09:53:12, suggesting the GPU was under stress for ~2 minutes before the crash. *** 09:53:59–09:54:00 — GPU MODE2 reset completes, hardware recovers, but gnome-shell loses its rendering context kernel: amdgpu 0000:70:00.0: MODE2 reset kernel: amdgpu 0000:70:00.0: GPU reset succeeded, trying to resume kernel: amdgpu 0000:70:00.0: GPU reset(1) succeeded! kernel: amdgpu 0000:70:00.0: [drm] device wedged, but recovered through reset gnome-shell[8975]: amdgpu: The CS has cancelled because the context is lost. This context is innocent. *** 09:54:04 — gnome-shell crashes (SIGABRT / core dump), taking the Wayland compositor down systemd[8328]: org.gnome.Shell@ubuntu.service: Main process exited, code=dumped, status=6/ABRT All Wayland clients lose their connection simultaneously: gnome-text-editor[62307]: Lost connection to Wayland compositor. google-chrome.desktop[14032]: Gdk-Message: Lost connection to Wayland compositor. ptyxis[10929]: Lost connection to Wayland compositor. gnome-calendar[11623]: Lost connection to Wayland compositor. gnome-shell[10351]: (EE) failed to read Wayland events: Broken pipe *** 09:54:05 — GNOME session is torn down; GDM login screen appears gdm-password][7929]: pam_unix(gdm-password:session): session closed for user albert systemd-logind[3000]: Removed session 2. gdm-launch-environment][62675]: pam_unix(gdm-launch-environment:session): session opened for user gdm-greeter A GPU coredump was created by the kernel: /sys/class/drm/card1/device/devcoredump/data Root cause analysis ==================== 1. Chrome (pid 14088) submitted a GPU command buffer that caused an UTCL2 page fault (bad virtual address mapping, read+write permission violation). 2. This stalled the gfx_0.1.0 command ring, which gnome-shell (pid 8975) was also submitting work to. 3. The ring-level reset failed, requiring a full MODE2 GPU reset. 4. The hardware reset succeeded, but gnome-shell (the Wayland compositor) cannot survive losing its Vulkan/GL context mid-frame and aborted. 5. With the Wayland compositor gone, the entire user session was terminated. The core issue is that one process (Chrome) triggering a GPU fault can destroy the GPU context of an unrelated innocent process (gnome- shell), resulting in total session loss. Ideally either: * the ring reset should succeed without a full GPU reset, or * gnome-shell should be able to recover from context loss after a GPU reset without crashing. Steps to reproduce ================== Reliably reproducible conditions are not yet confirmed, but the crash occurred during: Active Google Chrome usage with Teams video call (hardware-accelerated video decode active) gnome-shell simultaneously rendering the desktop via the same gfx ring Additional notes ================ * No system reboot occurred; the kernel and all non-GNOME processes survived. * The AMD GPU firmware is from 2026-03-19 (20260319.git217ca6e4). Newer upstream firmware from AMD may address the page fault or ring reset failure. * GPU device ID: 1002:13c0 (Granite Ridge / Ryzen 9000 series iGPU) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: albert 66499 F.... wireplumber /dev/snd/controlC0: albert 66499 F.... wireplumber /dev/snd/seq: albert 66498 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 12:50:22 2026 InstallationDate: Installed on 2026-06-22 (7 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Gigabyte Technology Co., Ltd. X870M AORUS ELITE WIFI7 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F10a dmi.board.asset.tag: Default string dmi.board.name: X870M AORUS ELITE WIFI7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF10a:bd06/09/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnX870MAORUSELITEWIFI7:pvrDefaultstring-WCP-ADO:rvnGigabyteTechnologyCo.,Ltd.:rnX870MAORUSELITEWIFI7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX870MB: dmi.product.family: X870 MB dmi.product.name: X870M AORUS ELITE WIFI7 dmi.product.sku: Default string dmi.product.version: Default string-WCP-ADO dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158614/+subscriptions