[Bug 2158106] [NEW] [Jammy] soft lockups and rcu stalls in fq_flush_timeout causing system hangs

Public bug reported: [SRU Justification] [Impact] Systems on Jammy running high-throughput DMA workloads experience soft lockups and RCU stalls in fq_flush_timeout, which result in system hangs. The IOVA allocator in the 5.15 kernel uses a per-CPU magazine cache (rcache) to avoid expensive rbtree operations. Each CPU has two magazines of 128 PFNs; when both are full, the primary "loaded" magazine is pushed to a global depot (a fixed-size array of 32 magazines per size-bin). When the depot is also full, the overflow magazine is freed via iova_magazine_free_pfns(), which acquires iova_rbtree_lock and performs up to 128 rbtree lookups and removals while holding it. The problem manifests through the flush-queue timer. Every 10ms, fq_flush_timeout fires in softirq context and drains all CPUs' flush queues in a single non-preemptible loop. Because __iova_rcache_insert uses raw_cpu_ptr(), all recycled IOVAs are funnelled into the timer CPU's magazines. Once those magazines and the shared depot are full, every subsequent overflow triggers the expensive iova_magazine_free_pfns, resulting in up to 128 rbtree operations under iova_rbtree_lock, all within the same softirq: fq_flush_timeout (timer softirq on CPU X) iova_domain_flush for_each_possible_cpu(cpu): fq_ring_free (up to IOVA_FQ_SIZE=256 entries) free_iova_fast __iova_rcache_insert (into CPU X's rcache via raw_cpu_ptr) if depot_size >= 32: iova_magazine_free_pfns (128 rbtree ops under iova_rbtree_lock) The RCU stall trace from an affected system on 5.15.0-117 confirms this exact path with reliable stack frames: native_queued_spin_lock_slowpath+0x2c/0x40 _raw_spin_lock_irqsave+0x3d/0x50 iova_magazine_free_pfns.part.0+0x20/0xd0 free_iova_fast+0x219/0x290 fq_ring_free+0xa8/0x170 fq_flush_timeout+0x74/0xc0 call_timer_fn run_timer_softirq __do_softirq [Fix] Backport upstream commits, adapted for the 5.15 codebase: 1. 911aa1245da8 ("iommu/iova: Make the rcache depot scale better") 2. 233045378dbb ("iommu/iova: Manage the depot list size") Cherry-pick upstream commit: 3. 7591c127f3b1 ("kmemleak: iommu/iova: fix transient kmemleak false positive") Patch 1 replaces the fixed-size depot array with an unbounded singly-linked list. Magazines are always pushed to the depot regardless of size. As a result, the overflow path and its inline call to iova_magazine_free_pfns are eliminated from __iova_rcache_insert. Patch 2 prevents unbounded memory growth of the now-unlimited depot by adding a delayed_work (background workqueue) that trims the depot when it exceeds num_online_cpus() magazines. This reclaim runs in process context, which is preemptible and sleepable, and therefore, cannot cause soft lockups. Patch 3 fixes a kmemleak false positive introduced by patch 1. Adaptations made for 5.15 backport: - Patches 1 and 2 modify both drivers/iommu/iova.c and include/linux/iova.h because in 5.15, struct iova_rcache is defined in the header (upstream moved it into iova.c in a prior refactoring series not present in 5.15). - The rcache init function in 5.15 is init_iova_rcaches() (static void, called unconditionally from init_iova_domain) rather than upstream's iova_domain_init_rcaches() (exported, returns int with error cleanup). The backport preserves the 5.15 function signature and error handling pattern. - 5.15 uses top-of-function variable declarations rather than upstream's C99 in-loop declarations. - The core logic (depot linked-list, overflow elimination, background worker) is identical between upstream and the backport. [Test Plan] TODO [Where problems could occur] Regression risk is low as changes in patches 1 and 2 are confined to the IOVA rcache depot internals (drivers/iommu/iova.c and include/linux/iova.h). No changes have been made to IOVA allocation or free semantics from the caller's perspective. Patch 3 is purely diagnostic and has no runtime effect. Moreover, the fix is already available on Noble and Resolute, where it has been thoroughly tested. [Other Info] Similar issues have been reported in [0], [1], and [2]. The fix has already been integrated into Noble and subsequent releases. Backporting this fix ensures stability for users of the 5.15 kernel. [0] - https://lkml.rescloud.iu.edu/2304.1/01286.html [1] - https://mailweb.openeuler.org/archives/list/kernel@openeuler.org/message/FAOBDKYWJ5SNADM625H2A4YCOPRAIRGB/ [2] - https://access.redhat.com/solutions/7031930 ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Munir Siddiqui (munirsid) Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Resolute) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Munir Siddiqui (munirsid) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158106 Title: [Jammy] soft lockups and rcu stalls in fq_flush_timeout causing system hangs Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Status in linux source package in Noble: Fix Released Status in linux source package in Resolute: Fix Released Bug description: [SRU Justification] [Impact] Systems on Jammy running high-throughput DMA workloads experience soft lockups and RCU stalls in fq_flush_timeout, which result in system hangs. The IOVA allocator in the 5.15 kernel uses a per-CPU magazine cache (rcache) to avoid expensive rbtree operations. Each CPU has two magazines of 128 PFNs; when both are full, the primary "loaded" magazine is pushed to a global depot (a fixed-size array of 32 magazines per size-bin). When the depot is also full, the overflow magazine is freed via iova_magazine_free_pfns(), which acquires iova_rbtree_lock and performs up to 128 rbtree lookups and removals while holding it. The problem manifests through the flush-queue timer. Every 10ms, fq_flush_timeout fires in softirq context and drains all CPUs' flush queues in a single non-preemptible loop. Because __iova_rcache_insert uses raw_cpu_ptr(), all recycled IOVAs are funnelled into the timer CPU's magazines. Once those magazines and the shared depot are full, every subsequent overflow triggers the expensive iova_magazine_free_pfns, resulting in up to 128 rbtree operations under iova_rbtree_lock, all within the same softirq: fq_flush_timeout (timer softirq on CPU X) iova_domain_flush for_each_possible_cpu(cpu): fq_ring_free (up to IOVA_FQ_SIZE=256 entries) free_iova_fast __iova_rcache_insert (into CPU X's rcache via raw_cpu_ptr) if depot_size >= 32: iova_magazine_free_pfns (128 rbtree ops under iova_rbtree_lock) The RCU stall trace from an affected system on 5.15.0-117 confirms this exact path with reliable stack frames: native_queued_spin_lock_slowpath+0x2c/0x40 _raw_spin_lock_irqsave+0x3d/0x50 iova_magazine_free_pfns.part.0+0x20/0xd0 free_iova_fast+0x219/0x290 fq_ring_free+0xa8/0x170 fq_flush_timeout+0x74/0xc0 call_timer_fn run_timer_softirq __do_softirq [Fix] Backport upstream commits, adapted for the 5.15 codebase: 1. 911aa1245da8 ("iommu/iova: Make the rcache depot scale better") 2. 233045378dbb ("iommu/iova: Manage the depot list size") Cherry-pick upstream commit: 3. 7591c127f3b1 ("kmemleak: iommu/iova: fix transient kmemleak false positive") Patch 1 replaces the fixed-size depot array with an unbounded singly-linked list. Magazines are always pushed to the depot regardless of size. As a result, the overflow path and its inline call to iova_magazine_free_pfns are eliminated from __iova_rcache_insert. Patch 2 prevents unbounded memory growth of the now-unlimited depot by adding a delayed_work (background workqueue) that trims the depot when it exceeds num_online_cpus() magazines. This reclaim runs in process context, which is preemptible and sleepable, and therefore, cannot cause soft lockups. Patch 3 fixes a kmemleak false positive introduced by patch 1. Adaptations made for 5.15 backport: - Patches 1 and 2 modify both drivers/iommu/iova.c and include/linux/iova.h because in 5.15, struct iova_rcache is defined in the header (upstream moved it into iova.c in a prior refactoring series not present in 5.15). - The rcache init function in 5.15 is init_iova_rcaches() (static void, called unconditionally from init_iova_domain) rather than upstream's iova_domain_init_rcaches() (exported, returns int with error cleanup). The backport preserves the 5.15 function signature and error handling pattern. - 5.15 uses top-of-function variable declarations rather than upstream's C99 in-loop declarations. - The core logic (depot linked-list, overflow elimination, background worker) is identical between upstream and the backport. [Test Plan] TODO [Where problems could occur] Regression risk is low as changes in patches 1 and 2 are confined to the IOVA rcache depot internals (drivers/iommu/iova.c and include/linux/iova.h). No changes have been made to IOVA allocation or free semantics from the caller's perspective. Patch 3 is purely diagnostic and has no runtime effect. Moreover, the fix is already available on Noble and Resolute, where it has been thoroughly tested. [Other Info] Similar issues have been reported in [0], [1], and [2]. The fix has already been integrated into Noble and subsequent releases. Backporting this fix ensures stability for users of the 5.15 kernel. [0] - https://lkml.rescloud.iu.edu/2304.1/01286.html [1] - https://mailweb.openeuler.org/archives/list/kernel@openeuler.org/message/FAOBDKYWJ5SNADM625H2A4YCOPRAIRGB/ [2] - https://access.redhat.com/solutions/7031930 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158106/+subscriptions

[Bug 2155609] Re: net/tls: Three upstream fixes without CVE missing from Ubuntu 6.8.0-124-generic

** Changed in: linux (Ubuntu) Assignee: (unassigned) => Cengiz Can (cengizcan) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Cengiz Can (cengizcan) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155609 Title: net/tls: Three upstream fixes without CVE missing from Ubuntu 6.8.0-124-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: == Summary == During source code analysis of Ubuntu 6.8.0-124-generic, 3 upstream security fixes in net/tls/tls_sw.c were found missing. None of these fixes have been assigned a CVE. == Environment == Kernel: 6.8.0-124-generic Package: linux-source-6.8.0 (apt) Verification method: Source diff vs upstream commits == Issue 1: Silent data drop under pipe back-pressure == Upstream fix: 7e7be31bfdb0 (2026-05-02) Author: Jakub Kicinski CVE: NOT ASSIGNED Vulnerable code (tls_sw.c line 2288-2290): if (chunk < rxm->full_len) { rxm->offset += len; rxm->full_len -= len; Required fix: if (copied < rxm->full_len) { rxm->offset += copied; rxm->full_len -= copied; Impact: When pipe is full during tls_sw_splice_read(), skb_splice_bits() returns copied < chunk. Ubuntu code advances rxm->offset by len instead of copied, silently skipping unread bytes. Causes data integrity violation in TLS RX splice path. == Issue 2: Off-by-one in sg_chain entry count == Upstream fix: 285943c6e7ca (2026-05-14) Author: Jakub Kicinski CVE: NOT ASSIGNED Reported by: 钱一铭 (yimingqian591@gmail.com) Vulnerable code (tls_sw.c line 803-804): sg_chain(&msg_pl->sg.data[msg_pl->sg.start], MAX_SKB_FRAGS - msg_pl->sg.start + 1, msg_pl->sg.data); Required fix: sg_chain(msg_pl->sg.data, ARRAY_SIZE(msg_pl->sg.data), msg_pl->sg.data); Impact: When sk_msg scatterlist ring wraps (sg.end < sg.start), wrong sg_chain index places chain pointer at data[MAX_SKB_FRAGS] instead of true last entry. Crypto engine receives invalid scatterlist, potential slab-out-of-bounds read/write. == Issue 3: chain-after-chain prevention in TLS 1.3 == Upstream fix: ff26a0e8377d (2026-05-14) Author: Jakub Kicinski CVE: NOT ASSIGNED Vulnerable code (tls_sw.c line 796): sg_chain(msg_pl->sg.data, msg_pl->sg.end + 1, &rec->sg_content_type); Required fix: sg_chain(msg_pl->sg.data, i + 2, &rec->sg_content_type); Impact: SGL does not allow chain-after-chain. For TLS 1.3, wrong chain size when wrap entry exists causes invalid scatterlist for content_type byte, potential memory corruption in crypto path. == Verification == Commands to reproduce: sudo apt install linux-source-6.8.0 sudo tar xf /usr/src/linux-source-6.8.0/\ linux-source-6.8.0.tar.bz2 -C /tmp/ # Issue 1: grep -n "rxm->offset += len" \ /tmp/linux-source-6.8.0/net/tls/tls_sw.c # Expected: line 2289 (vulnerable) # Issue 2: grep -n "MAX_SKB_FRAGS - msg_pl->sg.start" \ /tmp/linux-source-6.8.0/net/tls/tls_sw.c # Expected: line 804 (vulnerable) # Issue 3: grep -n "sg.end + 1" \ /tmp/linux-source-6.8.0/net/tls/tls_sw.c # Expected: line 796 (vulnerable) == References == 7e7be31bfdb0: https://git.kernel.org/torvalds/c/7e7be31bfdb0 285943c6e7ca: https://git.kernel.org/torvalds/c/285943c6e7ca ff26a0e8377d: https://git.kernel.org/torvalds/c/ff26a0e8377d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155609/+subscriptions

[Bug 2158075] Re: PCI/PM Regression: NVIDIA MX250 / PCI Bridge unable to change power state from D3cold to D0 on kernels >= 6.8 (HP Envy)

This is the other log that didnt attach ** Attachment added: "PCI Allocation" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158075/+attachment/5978735/+files/pci_allocation_bug.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158075 Title: PCI/PM Regression: NVIDIA MX250 / PCI Bridge unable to change power state from D3cold to D0 on kernels >= 6.8 (HP Envy) Status in linux package in Ubuntu: New Bug description: Expected Behavior: The discrete NVIDIA GeForce MX250 GPU should successfully initialize and wake from low-power runtime states during system boot and user session initialization. Actual Behavior: During the early system boot phase, the kernel fails to wake the discrete GPU from its power-saving D3cold state to D0. Because the hardware remains unresponsive, it reports a broken 64-bit BAR allocation window mapped above 4GB, and the NVIDIA proprietary driver fails to initialize entirely. This bug is persistent across modern HWE kernel stacks (tested on 6.11.0-29-generic and 6.17.0-35-generic). Steps taken that did NOT resolve the issue: - Verified DKMS modules compile completely cleanly for NVIDIA 535.309.01 against both kernels. - Attempted ACPI OSI overrides via GRUB including 'acpi_osi="Windows 2015"' and 'acpi_osi="Windows 2009"' to force legacy vendor firmware paths; the D3cold -> D0 timeout persisted. - Tested kernel and driver power-state management parameters including 'pcie_port_pm=off', 'pci=realloc', and 'nvidia.NVreg_DynamicPowerManagement=1'. None of these flags successfully intercepted or prevented the hardware from falling into an un-wakeable D3cold state. - System is only stable when completely bypassing the device initialization tree using 'prime-select intel'. Hardware Platform: - Laptop: HP Envy x360 15-dr0003np - GPU: NVIDIA GeForce MX250 / Integrated Intel Graphics - OS: Linux Mint 22.3 (Noble Base) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158075/+subscriptions

[Bug 2158075] [NEW] PCI/PM Regression: NVIDIA MX250 / PCI Bridge unable to change power state from D3cold to D0 on kernels >= 6.8 (HP Envy)

Public bug reported: Expected Behavior: The discrete NVIDIA GeForce MX250 GPU should successfully initialize and wake from low-power runtime states during system boot and user session initialization. Actual Behavior: During the early system boot phase, the kernel fails to wake the discrete GPU from its power-saving D3cold state to D0. Because the hardware remains unresponsive, it reports a broken 64-bit BAR allocation window mapped above 4GB, and the NVIDIA proprietary driver fails to initialize entirely. This bug is persistent across modern HWE kernel stacks (tested on 6.11.0-29-generic and 6.17.0-35-generic). Steps taken that did NOT resolve the issue: - Verified DKMS modules compile completely cleanly for NVIDIA 535.309.01 against both kernels. - Attempted ACPI OSI overrides via GRUB including 'acpi_osi="Windows 2015"' and 'acpi_osi="Windows 2009"' to force legacy vendor firmware paths; the D3cold -> D0 timeout persisted. - Tested kernel and driver power-state management parameters including 'pcie_port_pm=off', 'pci=realloc', and 'nvidia.NVreg_DynamicPowerManagement=1'. None of these flags successfully intercepted or prevented the hardware from falling into an un-wakeable D3cold state. - System is only stable when completely bypassing the device initialization tree using 'prime-select intel'. Hardware Platform: - Laptop: HP Envy x360 15-dr0003np - GPU: NVIDIA GeForce MX250 / Integrated Intel Graphics - OS: Linux Mint 22.3 (Noble Base) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Kernel logs" https://bugs.launchpad.net/bugs/2158075/+attachment/5978734/+files/kernel_power_bug.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158075 Title: PCI/PM Regression: NVIDIA MX250 / PCI Bridge unable to change power state from D3cold to D0 on kernels >= 6.8 (HP Envy) Status in linux package in Ubuntu: New Bug description: Expected Behavior: The discrete NVIDIA GeForce MX250 GPU should successfully initialize and wake from low-power runtime states during system boot and user session initialization. Actual Behavior: During the early system boot phase, the kernel fails to wake the discrete GPU from its power-saving D3cold state to D0. Because the hardware remains unresponsive, it reports a broken 64-bit BAR allocation window mapped above 4GB, and the NVIDIA proprietary driver fails to initialize entirely. This bug is persistent across modern HWE kernel stacks (tested on 6.11.0-29-generic and 6.17.0-35-generic). Steps taken that did NOT resolve the issue: - Verified DKMS modules compile completely cleanly for NVIDIA 535.309.01 against both kernels. - Attempted ACPI OSI overrides via GRUB including 'acpi_osi="Windows 2015"' and 'acpi_osi="Windows 2009"' to force legacy vendor firmware paths; the D3cold -> D0 timeout persisted. - Tested kernel and driver power-state management parameters including 'pcie_port_pm=off', 'pci=realloc', and 'nvidia.NVreg_DynamicPowerManagement=1'. None of these flags successfully intercepted or prevented the hardware from falling into an un-wakeable D3cold state. - System is only stable when completely bypassing the device initialization tree using 'prime-select intel'. Hardware Platform: - Laptop: HP Envy x360 15-dr0003np - GPU: NVIDIA GeForce MX250 / Integrated Intel Graphics - OS: Linux Mint 22.3 (Noble Base) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158075/+subscriptions

[Bug 2158074] [NEW] Dynabook RA/ZYB (AMD ACP 6.3, subsystem 3100:f07b): internal speakers silent, headphones have periodic dropouts

Public bug reported: On Dynabook RA/ZYB laptop running Ubuntu 26.04 LTS (kernel 7.0.0-22-generic), audio is not working correctly. Hardware: - Audio Coprocessor: AMD ACP 6.3 [1022:15e2] rev 63, subsystem Dynabook Inc. [3100:f07b] - SoundWire codec: Realtek rt722-sdca (sdw:0:0:025d:0722:01) - Driver in use: snd_pci_ps (legacy path, snd_acp_sdw_legacy_mach) Issue 1: Internal speakers completely silent - aplay -l detects Card 1 (amd-soundwire) with devices 0 (SimpleJack) and 2 (SmartAmp) - wpctl status shows "Audio Coprocessor Speaker" as default sink - ALSA control "Speaker Switch" is on, volumes at max (87/87) - speaker-test on hw:1,2 produces no audio even with PipeWire stopped - Suspected cause: subsystem ID 3100:f07b (Dynabook RA/ZYB) is not registered in snd_soc_acpi_amd_sdca_quirks, so the SmartAmp function of the rt722 SDCA codec is not properly initialized for this machine. Issue 2: Headphone jack has periodic dropouts (~1 per second) - Audio signal is present but interrupted approximately once per second - dmesg shows: "workqueue: acpi_os_execute_deferred hogged CPU for >10000us" occurring repeatedly, causing PipeWire buffer underruns - No ALSA/audio-specific errors in dmesg Expected: internal speakers and headphones work correctly Actual: internal speakers completely silent, headphones have periodic dropouts A quirk entry for subsystem 3100:f07b is likely needed in sound/soc/amd/ps/acp63-sdca-quirks.c or equivalent. 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 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ryuji 15355 F.... pipewire ryuji 15356 F.... wireplumber /dev/snd/controlC0: ryuji 15356 F.... wireplumber /dev/snd/seq: ryuji 15355 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:38:02 2026 InstallationDate: Installed on 2026-06-22 (2 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dynabook Inc. dynabook RA/ZYB ProcEnviron: LANG=ja_JP.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=002a38ae-4aa4-4550-918d-24be59ef4a54 ro quiet splash 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: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.80 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 1.80 dmi.board.asset.tag: 0000000000 dmi.board.name: OK012C/0000 dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 0000000000 dmi.chassis.type: 10 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion1.80:bd03/19/2026:br1.80:efr1.40:svnDynabookInc.:pndynabookRA/ZYB:pvrW6RAZY7BAH:rvnDynabookInc.:rnOK012C/0000:rvrVersionA0:cvnDynabookInc.:ct10:cvrVersion1.0:skuPGA10N:pfadynabook: dmi.product.family: dynabook dmi.product.name: dynabook RA/ZYB dmi.product.sku: PGA10N dmi.product.version: W6RAZY7BAH dmi.sys.vendor: Dynabook Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute ** Attachment added: "logs.tgz" https://bugs.launchpad.net/bugs/2158074/+attachment/5978713/+files/logs.tgz -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158074 Title: Dynabook RA/ZYB (AMD ACP 6.3, subsystem 3100:f07b): internal speakers silent, headphones have periodic dropouts Status in linux package in Ubuntu: New Bug description: On Dynabook RA/ZYB laptop running Ubuntu 26.04 LTS (kernel 7.0.0-22-generic), audio is not working correctly. Hardware: - Audio Coprocessor: AMD ACP 6.3 [1022:15e2] rev 63, subsystem Dynabook Inc. [3100:f07b] - SoundWire codec: Realtek rt722-sdca (sdw:0:0:025d:0722:01) - Driver in use: snd_pci_ps (legacy path, snd_acp_sdw_legacy_mach) Issue 1: Internal speakers completely silent - aplay -l detects Card 1 (amd-soundwire) with devices 0 (SimpleJack) and 2 (SmartAmp) - wpctl status shows "Audio Coprocessor Speaker" as default sink - ALSA control "Speaker Switch" is on, volumes at max (87/87) - speaker-test on hw:1,2 produces no audio even with PipeWire stopped - Suspected cause: subsystem ID 3100:f07b (Dynabook RA/ZYB) is not registered in snd_soc_acpi_amd_sdca_quirks, so the SmartAmp function of the rt722 SDCA codec is not properly initialized for this machine. Issue 2: Headphone jack has periodic dropouts (~1 per second) - Audio signal is present but interrupted approximately once per second - dmesg shows: "workqueue: acpi_os_execute_deferred hogged CPU for >10000us" occurring repeatedly, causing PipeWire buffer underruns - No ALSA/audio-specific errors in dmesg Expected: internal speakers and headphones work correctly Actual: internal speakers completely silent, headphones have periodic dropouts A quirk entry for subsystem 3100:f07b is likely needed in sound/soc/amd/ps/acp63-sdca-quirks.c or equivalent. 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 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ryuji 15355 F.... pipewire ryuji 15356 F.... wireplumber /dev/snd/controlC0: ryuji 15356 F.... wireplumber /dev/snd/seq: ryuji 15355 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:38:02 2026 InstallationDate: Installed on 2026-06-22 (2 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dynabook Inc. dynabook RA/ZYB ProcEnviron: LANG=ja_JP.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=002a38ae-4aa4-4550-918d-24be59ef4a54 ro quiet splash 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: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.80 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 1.80 dmi.board.asset.tag: 0000000000 dmi.board.name: OK012C/0000 dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 0000000000 dmi.chassis.type: 10 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion1.80:bd03/19/2026:br1.80:efr1.40:svnDynabookInc.:pndynabookRA/ZYB:pvrW6RAZY7BAH:rvnDynabookInc.:rnOK012C/0000:rvrVersionA0:cvnDynabookInc.:ct10:cvrVersion1.0:skuPGA10N:pfadynabook: dmi.product.family: dynabook dmi.product.name: dynabook RA/ZYB dmi.product.sku: PGA10N dmi.product.version: W6RAZY7BAH dmi.sys.vendor: Dynabook Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158074/+subscriptions

[Bug 2141634] Re: [Regression] Analog Audio Jack (3.5mm) not working after Kernel Update - Works on previous Kernel

Okay maybe another workaround if you have this issue. I managed to restore analog audio after booting without the headphones connected. I did so by running this command: systemctl --user restart pipewire pipewire-pulse.service pipewire-pulse.socket pipewire.socket -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2141634 Title: [Regression] Analog Audio Jack (3.5mm) not working after Kernel Update - Works on previous Kernel Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update, the analog audio output (headphone jack) has stopped working. Other audio outputs like internal laptop speakers and USB-C audio continue to work fine. The Problem: When using the new kernel, there is no sound from the 3.5mm jack. A background process repeatedly reports the following error: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running. Evidence of Regression: This issue does not occur when booting with the previous kernel version. All audio outputs, including the 3.5mm jack, work perfectly there. System Info: - Working Kernel: 6.17.0-12-generic Broken Kernel: 6.17.0-14-generic Audio Hardware: XPS 16 9640 with Codec: Intel Meteor Lake HDMI ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-14-generic 6.17.0-14.14 ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9 Uname: Linux 6.17.0-14-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: sfrey 3491 F.... wireplumber /dev/snd/controlC0: sfrey 3474 F.... pipewire sfrey 3491 F.... wireplumber /dev/snd/seq: sfrey 3474 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Feb 12 07:47:40 2026 InstallationDate: Installed on 2025-02-16 (361 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: Dell Inc. XPS 16 9640 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=0991c915-477e-44f9-93de-2fb39edfd762 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.6 SourcePackage: linux UpgradeStatus: Upgraded to questing on 2026-01-26 (17 days ago) dmi.bios.date: 09/05/2025 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0FJYF3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd09/05/2025:br1.18:efr1.20:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0FJYF3:rvrA01:cvnDellInc.:ct10:cvr:sku0C63: dmi.product.family: XPS dmi.product.name: XPS 16 9640 dmi.product.sku: 0C63 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141634/+subscriptions

[Bug 2158059] [NEW] amd-soundwire: dual TAS2783 link fails to prepare (Program params failed: -22) → PipeWire busy-loop, idle heat — Strix Halo / ProArt PX13

Public bug reported: What happens — the AMD ACP SoundWire link carrying two TI TAS2783 SmartAmps fails to program transport params at boot/stream-prepare, throwing repeated "Program params failed: -22" and leaving the ASoC node in a bad state. PipeWire then busy-loops recovering the node, pegging pipewire/journald with no audio playing — measurable idle heat and power draw. Release / kernel — Ubuntu 26.04 LTS, linux-image-7.0.0-22-generic 7.0.0-22.22 Hardware — ASUS ProArt PX13 HN7306EAC (BIOS HN7306EAC.304) · AMD Ryzen AI MAX+ 395 "Strix Halo" · AMD Audio Coprocessor [1022:15e2] rev 70 · amd-soundwire (card1); link SDW1 = 2× TI TAS2783 (sdw:0:1:0102:0000:01:8, sdw:0:1:0102:0000:01:b) + Realtek RT721 SDCA jack (sdw:0:1:025d:0721:01); driver snd_soc_tas2783_sdw on soundwire_amd. Key log lines (journalctl -b -k): amd_sdw_manager amd_sdw_manager.1: SDW1 cmd status retry failed amd_sdw_manager amd_sdw_manager.1: command timeout for Slave 1 slave-tas2783 sdw:0:1:0102:0000:01:b: FW download failed: -110 slave-tas2783 sdw:0:1:0102:0000:01:b: fw with no files amd_sdw_manager amd_sdw_manager.1: SDW1 manager is in bad state soundwire sdw-master-0-1: trf on Slave 1 failed:-110 write addr 8088 count 32632 soundwire sdw-master-0-1: Program transport params failed: -22 soundwire sdw-master-0-1: Program params failed: -22 SDW1-PIN4-CAPTURE-SmartAmp: ASoC error (-22): at snd_soc_link_prepare() on SDW1-PIN4-CAPTURE-SmartAmp sdw_deprepare_stream: subdevice #0-Capture: inconsistent state state 1 (~20 "Program params failed: -22" per affected boot. Some boots present as "SDW_SCP_BUSCLOCK_SCALE register write failed" instead. Two amps on one link appears to be the trigger.) Upstream — reported on the SOF kernel tree: https://github.com/thesofproject/linux/issues/5824 . No merged fix is pinned yet for this exact dual-TAS2783 ACP prepare failure. Active AMD ACP7.0 SoundWire area: TAS2783A driver thesofproject/linux#5510, related reports #5796 / #5620. Requesting investigation and, once a fix exists upstream, backport into the 26.04 7.0 kernel. Workaround in place — WirePlumber session.suspend-timeout-seconds=5 masks the PipeWire busy-loop, but the kernel-side -22 desync still occurs every few boots. Reproducibility — intermittent at boot, every few boots; once desynced it is reliably present until "systemctl --user restart wireplumber" or a reboot. 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 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: iky 1774 F.... wireplumber /dev/snd/pcmC1D2p: iky 1755 F...m pipewire /dev/snd/controlC0: iky 1774 F.... wireplumber /dev/snd/seq: iky 1755 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 24 10:15:05 2026 InstallationDate: Installed on 2026-06-04 (20 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) MachineType: ASUS ProArt PX13 HN7306EAC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=e654732d-a446-4ea4-bace-32c9af08b2e9 ro quiet splash ttm.pages_limit=30208000 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2025 dmi.bios.release: 5.36 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: HN7306EAC.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: HN7306EAC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHN7306EAC.304:bd12/24/2025:br5.36:efr3.4:svnASUS:pnProArtPX13HN7306EAC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnHN7306EAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:pfaProArtPX13: dmi.product.family: ProArt PX13 dmi.product.name: ProArt PX13 HN7306EAC dmi.product.version: 1.0 dmi.sys.vendor: ASUS ** 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/2158059 Title: amd-soundwire: dual TAS2783 link fails to prepare (Program params failed: -22) → PipeWire busy-loop, idle heat — Strix Halo / ProArt PX13 Status in linux package in Ubuntu: New Bug description: What happens — the AMD ACP SoundWire link carrying two TI TAS2783 SmartAmps fails to program transport params at boot/stream-prepare, throwing repeated "Program params failed: -22" and leaving the ASoC node in a bad state. PipeWire then busy-loops recovering the node, pegging pipewire/journald with no audio playing — measurable idle heat and power draw. Release / kernel — Ubuntu 26.04 LTS, linux-image-7.0.0-22-generic 7.0.0-22.22 Hardware — ASUS ProArt PX13 HN7306EAC (BIOS HN7306EAC.304) · AMD Ryzen AI MAX+ 395 "Strix Halo" · AMD Audio Coprocessor [1022:15e2] rev 70 · amd-soundwire (card1); link SDW1 = 2× TI TAS2783 (sdw:0:1:0102:0000:01:8, sdw:0:1:0102:0000:01:b) + Realtek RT721 SDCA jack (sdw:0:1:025d:0721:01); driver snd_soc_tas2783_sdw on soundwire_amd. Key log lines (journalctl -b -k): amd_sdw_manager amd_sdw_manager.1: SDW1 cmd status retry failed amd_sdw_manager amd_sdw_manager.1: command timeout for Slave 1 slave-tas2783 sdw:0:1:0102:0000:01:b: FW download failed: -110 slave-tas2783 sdw:0:1:0102:0000:01:b: fw with no files amd_sdw_manager amd_sdw_manager.1: SDW1 manager is in bad state soundwire sdw-master-0-1: trf on Slave 1 failed:-110 write addr 8088 count 32632 soundwire sdw-master-0-1: Program transport params failed: -22 soundwire sdw-master-0-1: Program params failed: -22 SDW1-PIN4-CAPTURE-SmartAmp: ASoC error (-22): at snd_soc_link_prepare() on SDW1-PIN4-CAPTURE-SmartAmp sdw_deprepare_stream: subdevice #0-Capture: inconsistent state state 1 (~20 "Program params failed: -22" per affected boot. Some boots present as "SDW_SCP_BUSCLOCK_SCALE register write failed" instead. Two amps on one link appears to be the trigger.) Upstream — reported on the SOF kernel tree: https://github.com/thesofproject/linux/issues/5824 . No merged fix is pinned yet for this exact dual-TAS2783 ACP prepare failure. Active AMD ACP7.0 SoundWire area: TAS2783A driver thesofproject/linux#5510, related reports #5796 / #5620. Requesting investigation and, once a fix exists upstream, backport into the 26.04 7.0 kernel. Workaround in place — WirePlumber session.suspend-timeout-seconds=5 masks the PipeWire busy-loop, but the kernel-side -22 desync still occurs every few boots. Reproducibility — intermittent at boot, every few boots; once desynced it is reliably present until "systemctl --user restart wireplumber" or a reboot. 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 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: iky 1774 F.... wireplumber /dev/snd/pcmC1D2p: iky 1755 F...m pipewire /dev/snd/controlC0: iky 1774 F.... wireplumber /dev/snd/seq: iky 1755 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 24 10:15:05 2026 InstallationDate: Installed on 2026-06-04 (20 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) MachineType: ASUS ProArt PX13 HN7306EAC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=e654732d-a446-4ea4-bace-32c9af08b2e9 ro quiet splash ttm.pages_limit=30208000 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2025 dmi.bios.release: 5.36 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: HN7306EAC.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: HN7306EAC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHN7306EAC.304:bd12/24/2025:br5.36:efr3.4:svnASUS:pnProArtPX13HN7306EAC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnHN7306EAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:pfaProArtPX13: dmi.product.family: ProArt PX13 dmi.product.name: ProArt PX13 HN7306EAC dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158059/+subscriptions

[Bug 2150196] Re: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms

This bug is awaiting verification that the linux-nvidia/7.0.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-nvidia' to 'verification-done- resolute-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia' to 'verification-failed- resolute-linux-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-v2 verification-needed-resolute-linux-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150196 Title: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: Fix Released Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in alsa-ucm-conf source package in Questing: Fix Released Status in linux source package in Questing: Won't Fix Status in linux-oem-6.17 source package in Questing: Invalid Status in alsa-ucm-conf source package in Resolute: Fix Released Status in linux source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Status in alsa-ucm-conf source package in Stonking: Fix Released Status in linux source package in Stonking: Fix Committed Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: SRU Justification: [ Impact ] Lenovo PTL systems with rt722 headset codec + rt1320 speaker amp over SoundWire have no speaker audio and no DMIC. The kernel's PTL match table lacks the rt722_l0_rt1320_l23 topology, the rt1320 codec_info_list is missing its DMIC dai, and the is_amp flag is absent -- so the machine driver never matches and the wrong name prefix is assigned. [ Fix ] Seven upstream commits from Linus's mainline, applied in topological order: 1. 38ecd1384079 (v6.19) -- add ptl_rt722_l0_rt1320_l23 match table entry 2. 4fbd3b2ec04d (v7.0) -- use aggregated endpoints for rt722 in that entry 3. 403a0591be68 (v6.19) -- fix name_prefix of second rt1320 (rt1320-2) 4. 754b3dade5dd (v7.0) -- drop rt721 monolithic match tables (prerequisite for 5) 5. 9033f7b7f27d (linux/master, not yet tagged) -- drop rt722 monolithic match tables 6. dd4a1963ddf0 (linux/master, not yet tagged) -- add is_amp flag to fix wrong name prefix 7. ae2cb3384337 (linux/master, not yet tagged) -- add rt1320/rt1321 DMIC dai in codec_info_list All cherry-pick cleanly with zero conflicts. Diffs are byte-identical to upstream (only hunk offsets and context lines differ due to different base tree). [ Test Plan ] On a Lenovo PTL system with spk:rt1320 + hs:rt722: 1. Boot without patches: no speaker sound card components, no DMIC 2. Boot with patches:    - Speaker playback: aplay -D hw:0,2 tone.wav    - DMIC loopback: play 1kHz tone through speaker, record from DMIC, FFT confirms peak at 1000 Hz    - WirePlumber sees all devices    - Mute LEDs functional (speaker and mic)    - Suspend/resume: full status diff pre vs post identical, loopback and LEDs work after resume [ Where problems could occur ] Patches touch PTL match tables, SoundWire codec_info_list, and SOF HDA codec matching. A wrong match table entry could cause a different PTL topology to break (wrong codec matched). The is_amp flag override in find_acpi_adr_device() runs for all SoundWire codecs on Intel SOF platforms -- if the flag logic is wrong, non-amp codecs could get misidentified, breaking name prefixes and DAI routing. Commits 4-5 remove rt721/rt722 monolithic match tables; any PTL machine still relying on monolithic matching (rather than function topologies) would lose its match entry. [ Other Info ] Commits 5-7 are merged on linux/master but not yet in a tagged release. Tested on two Lenovo PTL machines -- full audio pass including loopback and suspend/resume. Target: oem-6.17 and resolute only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150196/+subscriptions

[Bug 2154536] Re: Firefox crashes system and reboots on certain webpages

** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154536 Title: Firefox crashes system and reboots on certain webpages Status in firefox package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When I tried to open certain web pages on Firefox on an ARM64 machine (a ThinkPad X13s Gen 1 with a Snapdragon 8cx Gen 3 SoC), the screen would go black and the system would reboot. I have not tried it on chromium yet, but if that browser works, I will be using it until a patch is made. This happened to me twice on the following webpages https://swaywm.org and https://www.ti.com/tool/MSP-EXP430FR5994 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: firefox 1:1snap1-0ubuntu8 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic aarch64 ApportVersion: 2.34.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:22:42 2026 InstallationDate: Installed on 2026-05-28 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release arm64 (20260423.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> SnapChanges: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2154536/+subscriptions

[Bug 1040526] Re: Graphics dithered on Desktop image

Is this still an issue with a current release? ** Changed in: ubuntu-cdimage Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1040526 Title: Graphics dithered on Desktop image Status in Ubuntu CD Images: Incomplete Status in linux package in Ubuntu: Expired Bug description: The graphics on the install disk for the 20120821 Desktop image are dithered and ugly. See attached screen shot. WORKAROUND: Booting with kernel parameter: live video=ofonly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040526/+subscriptions

[Bug 2157970] [NEW] Enable micmute LED on HP EliteBook 6 G1a (AD3Q9ET#UUG)

Public bug reported: The HP EliteBook 6 G1a (SSID 103c:8e0d, SKU Number: AD3Q9ET#UUG) uses a Realtek ALC236 codec. Without a quirk no fixup is selected and the mic-mute LED stays off. It needs the same ALC236_FIXUP_HP_MUTE_LED_MICMUTE_VREF quirk as the already-supported 14" variant (SSID 103c:8dfb). I've attached patch that enables mic-mute led with my current kernel (7.0.0-26-generic) Patch was built on top of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-26-generic 7.0.0-26.26 ProcVersionSignature: Ubuntu 7.0.0-26.26-generic 7.0.6 Uname: Linux 7.0.0-26-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:26:48 2026 HibernationDevice: UUID=e8d43458-12a7-473b-a92b-d47015438b66 InstallationDate: Installed on 2022-05-10 (1505 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-26-generic root=UUID=e8d43458-12a7-473b-a92b-d47015438b66 ro mitigations=off audit=0 apparmor=0 selinux=0 transparent_hugepage=always amd_pstate=active hibernate=nocompress,protect_image hibernate.compressor=lzo hibernate_compression_threads=8 resume=UUID=42953b41-f743-4d5b-ae16-f9f28892df68 amd_iommu=off iommu=noforce panic=0 snd_intel_dspcfg.dsp_driver=3 zswap.enabled=0 zswap.compressor=lz4 zswap.zpool=zsmalloc 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 2025-10-01 (265 days ago) dmi.bios.date: 05/12/2026 dmi.bios.release: 5.6 dmi.bios.vendor: HP dmi.bios.version: X76 Ver. 01.05.06 dmi.board.name: 8E0D dmi.board.vendor: HP dmi.board.version: KBC Version 58.31.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.49 dmi.modalias: dmi:bvnHP:bvrX76Ver.01.05.06:bd05/12/2026:br5.6:efr88.49:svnHP:pnHPEliteBook6G1a14inchNotebookNextGenAIPC:pvrSBKPFV3:rvnHP:rn8E0D:rvrKBCVersion58.31.00:cvnHP:ct10:cvr:skuAD3Q9ET#UUG:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC dmi.product.sku: AD3Q9ET#UUG dmi.product.version: SBKPFV3 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed resolute third-party-packages wayland-session ** Patch added: "v1_hpeb-6g1a-micmute.patch" https://bugs.launchpad.net/bugs/2157970/+attachment/5978564/+files/v1_hpeb-6g1a-micmute.patch -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157970 Title: Enable micmute LED on HP EliteBook 6 G1a (AD3Q9ET#UUG) Status in linux package in Ubuntu: New Bug description: The HP EliteBook 6 G1a (SSID 103c:8e0d, SKU Number: AD3Q9ET#UUG) uses a Realtek ALC236 codec. Without a quirk no fixup is selected and the mic-mute LED stays off. It needs the same ALC236_FIXUP_HP_MUTE_LED_MICMUTE_VREF quirk as the already-supported 14" variant (SSID 103c:8dfb). I've attached patch that enables mic-mute led with my current kernel (7.0.0-26-generic) Patch was built on top of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-26-generic 7.0.0-26.26 ProcVersionSignature: Ubuntu 7.0.0-26.26-generic 7.0.6 Uname: Linux 7.0.0-26-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:26:48 2026 HibernationDevice: UUID=e8d43458-12a7-473b-a92b-d47015438b66 InstallationDate: Installed on 2022-05-10 (1505 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-26-generic root=UUID=e8d43458-12a7-473b-a92b-d47015438b66 ro mitigations=off audit=0 apparmor=0 selinux=0 transparent_hugepage=always amd_pstate=active hibernate=nocompress,protect_image hibernate.compressor=lzo hibernate_compression_threads=8 resume=UUID=42953b41-f743-4d5b-ae16-f9f28892df68 amd_iommu=off iommu=noforce panic=0 snd_intel_dspcfg.dsp_driver=3 zswap.enabled=0 zswap.compressor=lz4 zswap.zpool=zsmalloc 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 2025-10-01 (265 days ago) dmi.bios.date: 05/12/2026 dmi.bios.release: 5.6 dmi.bios.vendor: HP dmi.bios.version: X76 Ver. 01.05.06 dmi.board.name: 8E0D dmi.board.vendor: HP dmi.board.version: KBC Version 58.31.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.49 dmi.modalias: dmi:bvnHP:bvrX76Ver.01.05.06:bd05/12/2026:br5.6:efr88.49:svnHP:pnHPEliteBook6G1a14inchNotebookNextGenAIPC:pvrSBKPFV3:rvnHP:rn8E0D:rvrKBCVersion58.31.00:cvnHP:ct10:cvr:skuAD3Q9ET#UUG:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC dmi.product.sku: AD3Q9ET#UUG dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157970/+subscriptions

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

** Changed in: linux (Ubuntu Stonking) Status: New => In Progress ** Changed in: linux (Ubuntu Stonking) Assignee: (unassigned) => Bin Li (binli) -- 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 Committed 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 Committed 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 1894964] Re: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build)

Kernel EOL, and this is not referenced in our hint database. Closing it. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1894964 Title: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build) Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Expired Status in linux source package in Groovy: Won't Fix Bug description: Issue found on 5.8.0-1001.1 - kvm Test build failed with: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' In file included from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:5, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/kernel.h:8, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.h:10, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:8: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c: In function ‘__func_get_name’: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:38: warning: nested extern declaration of ‘__compiletime_assert_0’ [-Wnested-externs] 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~~~~~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:16:15: note: in definition of macro ‘__compiletime_assert’ 16 | extern void prefix ## suffix(void) __compiletime_error(msg); \ | ^~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:2: note: in expansion of macro ‘_compiletime_assert’ 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~~~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:39:37: note: in expansion of macro ‘compiletime_assert’ 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) | ^~~~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:50:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’ 50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition) | ^~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:20:2: note: in expansion of macro ‘BUILD_BUG_ON’ 20 | BUILD_BUG_ON(ARRAY_SIZE(func_id_str) != __BPF_FUNC_MAX_ID); | ^~~~~~~~~~~~ libbpf: failed to open format: No such file or directory Error: failed to load BTF from format: No such file or directory make[1]: *** [Makefile:190: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h] Error 2 make[1]: *** Deleting file '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h' make: *** [Makefile:157: all] Error 2 Please find attachment for the complete build log. As the ubuntu_kernel_selftests needs bpf to be built first, this will block the ubuntu_kernel_selftests/net to build as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894964/+subscriptions