Tried reboot= with acpi, efi and psi without any change. Tried disabling PCIe ASPM in bios, still hanging. However, this works: GRUB_CMDLINE_LINUX_DEFAULT="pcie_aspm=off" -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142891 Title: NUC10I7FNK hangs on reboot > 6.8.0-94 & 6.17.0-14 Status in linux package in Ubuntu: New Bug description: System hangs after "rebooting system" with a black screen on kernels mentioned in subject, downgrading to 6.8.0-94-generic fixes the problem. Have tested reboot= settings on new kernels with no effect. Let me know if you need details from the logs of the failing kernel, the reports added is from the working kernel. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-94-generic 6.8.0-94.96 ProcVersionSignature: Ubuntu 6.8.0-94.96-generic 6.8.12 Uname: Linux 6.8.0-94-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-94-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Fri Feb 27 19:46:25 2026 InstallationDate: Installed on 2025-09-17 (163 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-94-generic root=/dev/mapper/vg0-ubuntu ro reboot=acpi RelatedPackageVersions: linux-restricted-modules-6.8.0-94-generic N/A linux-backports-modules-6.8.0-94-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.25 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2022 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0058.2022.0720.1011 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: M38062-307 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0058.2022.0720.1011:bd07/20/2022:br5.16:efr3.12:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrM38010-308:rvnIntelCorporation:rnNUC10i7FNB:rvrM38062-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i7FNHN: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNHN dmi.product.version: M38010-308 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142891/+subscriptions
суббота
[Bug 2158074] Re: Dynabook RA/ZYB (AMD ACP 6.3, subsystem 3100:f07b): internal speakers silent, headphones have periodic dropouts
Closing as Invalid. The audio issue was caused by warm reboot from Windows. A full power cycle (shutdown from Windows, then boot Ubuntu) resolves the issue. No kernel changes are needed. ** Changed in: linux (Ubuntu) Status: New => Invalid -- 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: Invalid 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 2142891] Re: NUC10I7FNK hangs on reboot > 6.8.0-94 & 6.17.0-14
Checked linux-image-6.8.0-124-generic today, and the problem is still present. Stuck on linux-image-6.8.0-94-generic, as that is the last kernel I have found that does not hang with a black screen before the system reboots to UEFI log. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142891 Title: NUC10I7FNK hangs on reboot > 6.8.0-94 & 6.17.0-14 Status in linux package in Ubuntu: New Bug description: System hangs after "rebooting system" with a black screen on kernels mentioned in subject, downgrading to 6.8.0-94-generic fixes the problem. Have tested reboot= settings on new kernels with no effect. Let me know if you need details from the logs of the failing kernel, the reports added is from the working kernel. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-94-generic 6.8.0-94.96 ProcVersionSignature: Ubuntu 6.8.0-94.96-generic 6.8.12 Uname: Linux 6.8.0-94-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-94-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Fri Feb 27 19:46:25 2026 InstallationDate: Installed on 2025-09-17 (163 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel(R) Client Systems NUC10i7FNH ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-94-generic root=/dev/mapper/vg0-ubuntu ro reboot=acpi RelatedPackageVersions: linux-restricted-modules-6.8.0-94-generic N/A linux-backports-modules-6.8.0-94-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.25 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2022 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0058.2022.0720.1011 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: M38062-307 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0058.2022.0720.1011:bd07/20/2022:br5.16:efr3.12:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrM38010-308:rvnIntelCorporation:rnNUC10i7FNB:rvrM38062-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i7FNHN: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNHN dmi.product.version: M38010-308 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142891/+subscriptions
[Bug 2154075] Re: [REGRESSION] ASUS Zenbook S16 UM5606GA (Ryzen AI 9 HX470) graphical freeze before login with Ubuntu 26.04 kernel 7.0.x, fixed by kernel 6.17
Does sound function well with 6.18.7-760061807? While the display functions well with Ubuntu 24.04 kernel (on Ubuntu 26.04), sound does not. I cannot issue a bug on that, because Ubuntu's bug reporting tool refuses to run if the kernel does not match the distribution. Thanks! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154075 Title: [REGRESSION] ASUS Zenbook S16 UM5606GA (Ryzen AI 9 HX470) graphical freeze before login with Ubuntu 26.04 kernel 7.0.x, fixed by kernel 6.17 Status in linux package in Ubuntu: Confirmed Bug description: System experiences a reproducible graphical freeze during boot on Ubuntu 26.04 when using Ubuntu kernel 7.0.x. Hardware: * ASUS Zenbook S16 UM5606GA * AMD Ryzen AI 9 HX470 * integrated AMD graphics * BIOS version: UM5606GA.305 * BIOS date: 2026-02-25 * Secure Boot enabled Affected kernels: * 7.0.0-15-generic (fails) Known-good kernels: * 6.17.0-29-generic (works correctly) The issue appears shortly before the graphical login prompt should appear. Symptoms: * display freezes before login screen * mouse cursor may briefly move after resume from suspend * GUI remains visually frozen * keyboard and GUI actions occasionally appear after subsequent wake events * SSH access continues to function normally * system does not panic or reboot This suggests the kernel remains operational while the graphics/display stack hangs. Environment: * Ubuntu 26.04 userspace * GNOME * both Wayland and Xorg tested * same Mesa userspace for both working and failing kernels Regression evidence: The following configuration changes were tested and reverted unless otherwise noted: 1. Booting Ubuntu 26.04 live environment using "Safe graphics" Result: * works correctly 2. Booting installed system with: nomodeset Result: * works correctly * accelerated graphics unavailable 3. GRUB: set gfxpayload=keep Result: * Ubuntu live environment boots correctly in safe graphics mode 4. Kernel parameter: amdgpu.dcdebugmask=0x12 Result: * no improvement 5. Kernel parameter: amdgpu.mes=0 Result: * no improvement 6. Kernel parameter: amdgpu.dc=0 Result: * system freezes earlier during splash screen * SSH remains operational 7. Kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Result: * no improvement 8. Kernel parameter: pcie_aspm=off Result: * no improvement 9. Forced Xorg instead of Wayland Result: * same behavior 10. Replaced /lib/firmware/amdgpu firmware files with Ubuntu 24.04 versions Result: * no improvement * reverted afterward 11. Ubuntu 24.04 live environment Result: * boots correctly without safe graphics 12. Installed Ubuntu kernel: 6.17.0-29-generic Packages installed: * linux-headers-6.17.0-29-generic * linux-image-6.17.0-29-generic * linux-modules-6.17.0-29-generic * linux-tools-6.17.0-29-generic Result: * fully stable system * accelerated graphics functional * graphical login works correctly * suspend/resume functional Current working kernel: Linux aeon 6.17.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Tue May 5 19:42:34 UTC 2026 x86_64 GNU/Linux Conclusion: This appears to be a regression introduced in Ubuntu kernel 7.0.x affecting AMDGPU graphics initialization or display handling on Ryzen AI 9 HX470 / Strix Point hardware. The issue does not appear specific to: * GNOME * Wayland * Xorg * userspace Mesa because the same userspace environment works correctly under kernel 6.17. Suspected subsystem: * amdgpu * DRM/DCN * DMUB/DMCUB * modesetting * display core * Ryzen AI / Strix Point graphics enablement Potential duplicates / related reports: 1. Bug #2148753 linux-firmware-amd-graphics graphical boot regression on Ryzen AI ASUS Zenbook systems https://bugs.launchpad.net/ubuntu/+source/linux-firmware-amd-graphics/+bug/2148753 Mirror: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg6269039.html 2. Bug #2147541 Ryzen AI platform regression under Ubuntu 26.04 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147541 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 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sat May 23 17:32:03 2026 InstallationDate: Installed on 2026-05-15 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS Zenbook S16 UM5606GA 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-15-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 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: 02/25/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM5606GA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM5606GA 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.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5606GA.305:bd02/25/2026:br5.35:efr3.3:svnASUS:pnZenbookS16UM5606GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5606GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaZenbookS16: dmi.product.family: Zenbook S16 dmi.product.name: Zenbook S16 UM5606GA 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/2154075/+subscriptions
[Bug 2158523] [NEW] [Snapdragon X Elite / X1E80100] ThinkPad T14s Gen 6 (21N1): spontaneous in-use hard reset — no kernel panic, no pstore dump, corrupted journal (distinct from suspend bug #2127013)
Public bug reported: Summary ------- On a Lenovo ThinkPad T14s Gen 6 (Snapdragon X Elite / X1E80100) the machine spontaneously hard-resets while in normal use — not during suspend, not during USB-C hotplug. The reset is firmware/SoC-level: there is no kernel panic, no oops, no soft/hard-lockup trace, nothing in pstore/ramoops, and the systemd journal of the killed boot is left corrupted (the kernel never got to log anything). The machine reboots on its own after a hard cut. This is a different failure from LP #2127013, which is suspend/resume- specific (immediate resume after s2idle). This report is specifically about resets that occur while the machine is awake and in use. Hardware -------- - Model: Lenovo ThinkPad T14s Gen 6 - Machine type / product: 21N10001US (MT 21N1) - SoC: Qualcomm Snapdragon X Elite, X1E80100 (aarch64) - BIOS: LENOVO N42ET97W (2.27), date 2026-02-24 Software -------- - Ubuntu 26.04 LTS - Kernel: 7.0.0-27-generic (#27-Ubuntu SMP PREEMPT_DYNAMIC aarch64) - Suspend mode: s2idle - Kernel command line: ro arm64.nopauth clk_ignore_unused pd_ignore_unused cma=128M efi=noruntime quiet splash console=tty0 mem_sleep_default=s2idle crashkernel=2G-4G:320M,... (clk_ignore_unused / pd_ignore_unused / efi=noruntime are the documented required X1E params; arm64.nopauth was added as a speculative mitigation and made no observable difference.) Impact ------ Unpredictable loss of all unsaved work; filesystem orphan-cleanup on every recovery boot. Because the reset is below the OS, kdump never fires and no crash artifact is produced, making it very hard to diagnose. What happens ------------ The system is running normally (light desktop + containers), then without warning the screen cuts and the machine resets and reboots. It is not correlated with suspend or with plugging/unplugging USB-C. Failure signature (forensics from one captured instance) -------------------------------------------------------- - The boot that died ran ~3h10m entirely in-use. It performed ZERO suspend cycles before the reset (so this is not the s2idle path). - The last kernel-ring message preceded the reset by ~2h18m; there is no kernel activity logged at the moment of the cut. - No "panic", "oops", "BUG:", soft/hard-lockup, RCU stall, MCE, or thermal-trip message anywhere near the reset. - /sys/fs/pstore is empty after the reset (kdump-tools active, crashkernel reserved) — nothing was captured. - On the recovery boot: "EXT4-fs (nvmeXn1pY): orphan cleanup on readonly fs" and "system.journal corrupted or uncleanly shut down" — i.e. a hard power cut, not a graceful reboot. - Note: the platform reports "watchdog: NMI not fully supported" / "Hard watchdog permanently disabled", so a CPU soft-lockup would not be caught by an NMI watchdog. Reproducibility --------------- Intermittent — occurs roughly every few hours of uptime, not on demand. I have installed a small boot-flag service (writes a flag on boot, removes it on clean shutdown) so each reset is unambiguously recorded with a timestamp and whether the prior boot had suspended; I can attach this log over time to characterise frequency. Related observation (may point at the layer involved) ---------------------------------------------------- After some of these resets, the next Linux boot comes up with the display(s) black (both internal eDP and external). A full cold power-off + drain does NOT clear it; only booting Windows once and then back into Linux restores the display. This strongly suggests a Qualcomm subsystem / display-PHY / firmware state that the proprietary Windows driver stack tears down but Linux does not — consistent with the reset itself being a firmware/SoC-level event rather than a kernel fault. What I have tried ----------------- - Upgraded 25.10 (6.17) -> 26.04 (7.0.0-27): the lenovo-thinkpad-t14s EC driver is now loaded; it did not stop the in-use resets. - Added arm64.nopauth: no observable change. - Confirmed it is not the suspend path (#2127013) and not USB-C hotplug. Request ------- 1. Is there any known X1E80100 SoC watchdog / PMIC power-collapse / PDR-SSR path that can trigger a full SoC reset without a kernel trace, and any way to surface it (e.g. enabling a Qualcomm-side log, ramoops backend that survives this reset type, or a debug build)? 2. Guidance on capturing anything at all from a reset that leaves pstore empty would be very welcome. 3. Happy to test debug kernels / patches and to provide the reset-frequency log and any apport data. 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 aarch64 ApportVersion: 2.34.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: devop 4290 F.... pipewire devop 4573 F.... wireplumber /dev/snd/seq: devop 4290 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 16:35:57 2026 InstallationDate: Installed on 2026-01-07 (171 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release arm64 (20251007) Lspci-vt: -[0004:00]---00.0-[01-ff]----00.0 Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] -[0005:00]---00.0-[01-ff]-- -[0006:00]---00.0-[01-ff]----00.0 Sandisk Corp WD PC SN740 NVMe SSD 512GB (DRAM-less) MachineType: LENOVO 21N10001US ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=17fb0394-4f34-4e43-bb6a-ae0867401e98 ro arm64.nopauth clk_ignore_unused pd_ignore_unused cma=128M efi=noruntime quiet splash console=tty0 mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-27 (0 days ago) acpidump: dmi.bios.date: 02/24/2026 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: N42ET97W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21N10001US dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN ptal����8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN42ET97W(2.27):bd02/24/2026:br2.27:efr1.32:svnLENOVO:pn21N10001US:pvrThinkPadT14sGen6:rvnLENOVO:rn21N10001US:rvrSDK0T76576WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21N1_BU_Think_FM_ThinkPadT14sGen6:pfaThinkPadT14sGen6: dmi.product.family: ThinkPad T14s Gen 6 dmi.product.name: 21N10001US dmi.product.sku: LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6 dmi.product.version: ThinkPad T14s Gen 6 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 qualcomm resolute snapdragon thinkpad wayland-session x1e80100 ** Attachment added: "launchpad-evidence.txt" https://bugs.launchpad.net/bugs/2158523/+attachment/5979220/+files/launchpad-evidence.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158523 Title: [Snapdragon X Elite / X1E80100] ThinkPad T14s Gen 6 (21N1): spontaneous in-use hard reset — no kernel panic, no pstore dump, corrupted journal (distinct from suspend bug #2127013) Status in linux package in Ubuntu: New Bug description: Summary ------- On a Lenovo ThinkPad T14s Gen 6 (Snapdragon X Elite / X1E80100) the machine spontaneously hard-resets while in normal use — not during suspend, not during USB-C hotplug. The reset is firmware/SoC-level: there is no kernel panic, no oops, no soft/hard-lockup trace, nothing in pstore/ramoops, and the systemd journal of the killed boot is left corrupted (the kernel never got to log anything). The machine reboots on its own after a hard cut. This is a different failure from LP #2127013, which is suspend/resume- specific (immediate resume after s2idle). This report is specifically about resets that occur while the machine is awake and in use. Hardware -------- - Model: Lenovo ThinkPad T14s Gen 6 - Machine type / product: 21N10001US (MT 21N1) - SoC: Qualcomm Snapdragon X Elite, X1E80100 (aarch64) - BIOS: LENOVO N42ET97W (2.27), date 2026-02-24 Software -------- - Ubuntu 26.04 LTS - Kernel: 7.0.0-27-generic (#27-Ubuntu SMP PREEMPT_DYNAMIC aarch64) - Suspend mode: s2idle - Kernel command line: ro arm64.nopauth clk_ignore_unused pd_ignore_unused cma=128M efi=noruntime quiet splash console=tty0 mem_sleep_default=s2idle crashkernel=2G-4G:320M,... (clk_ignore_unused / pd_ignore_unused / efi=noruntime are the documented required X1E params; arm64.nopauth was added as a speculative mitigation and made no observable difference.) Impact ------ Unpredictable loss of all unsaved work; filesystem orphan-cleanup on every recovery boot. Because the reset is below the OS, kdump never fires and no crash artifact is produced, making it very hard to diagnose. What happens ------------ The system is running normally (light desktop + containers), then without warning the screen cuts and the machine resets and reboots. It is not correlated with suspend or with plugging/unplugging USB-C. Failure signature (forensics from one captured instance) -------------------------------------------------------- - The boot that died ran ~3h10m entirely in-use. It performed ZERO suspend cycles before the reset (so this is not the s2idle path). - The last kernel-ring message preceded the reset by ~2h18m; there is no kernel activity logged at the moment of the cut. - No "panic", "oops", "BUG:", soft/hard-lockup, RCU stall, MCE, or thermal-trip message anywhere near the reset. - /sys/fs/pstore is empty after the reset (kdump-tools active, crashkernel reserved) — nothing was captured. - On the recovery boot: "EXT4-fs (nvmeXn1pY): orphan cleanup on readonly fs" and "system.journal corrupted or uncleanly shut down" — i.e. a hard power cut, not a graceful reboot. - Note: the platform reports "watchdog: NMI not fully supported" / "Hard watchdog permanently disabled", so a CPU soft-lockup would not be caught by an NMI watchdog. Reproducibility --------------- Intermittent — occurs roughly every few hours of uptime, not on demand. I have installed a small boot-flag service (writes a flag on boot, removes it on clean shutdown) so each reset is unambiguously recorded with a timestamp and whether the prior boot had suspended; I can attach this log over time to characterise frequency. Related observation (may point at the layer involved) ---------------------------------------------------- After some of these resets, the next Linux boot comes up with the display(s) black (both internal eDP and external). A full cold power-off + drain does NOT clear it; only booting Windows once and then back into Linux restores the display. This strongly suggests a Qualcomm subsystem / display-PHY / firmware state that the proprietary Windows driver stack tears down but Linux does not — consistent with the reset itself being a firmware/SoC-level event rather than a kernel fault. What I have tried ----------------- - Upgraded 25.10 (6.17) -> 26.04 (7.0.0-27): the lenovo-thinkpad-t14s EC driver is now loaded; it did not stop the in-use resets. - Added arm64.nopauth: no observable change. - Confirmed it is not the suspend path (#2127013) and not USB-C hotplug. Request ------- 1. Is there any known X1E80100 SoC watchdog / PMIC power-collapse / PDR-SSR path that can trigger a full SoC reset without a kernel trace, and any way to surface it (e.g. enabling a Qualcomm-side log, ramoops backend that survives this reset type, or a debug build)? 2. Guidance on capturing anything at all from a reset that leaves pstore empty would be very welcome. 3. Happy to test debug kernels / patches and to provide the reset-frequency log and any apport data. 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 aarch64 ApportVersion: 2.34.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: devop 4290 F.... pipewire devop 4573 F.... wireplumber /dev/snd/seq: devop 4290 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 16:35:57 2026 InstallationDate: Installed on 2026-01-07 (171 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release arm64 (20251007) Lspci-vt: -[0004:00]---00.0-[01-ff]----00.0 Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] -[0005:00]---00.0-[01-ff]-- -[0006:00]---00.0-[01-ff]----00.0 Sandisk Corp WD PC SN740 NVMe SSD 512GB (DRAM-less) MachineType: LENOVO 21N10001US ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=17fb0394-4f34-4e43-bb6a-ae0867401e98 ro arm64.nopauth clk_ignore_unused pd_ignore_unused cma=128M efi=noruntime quiet splash console=tty0 mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-27 (0 days ago) acpidump: dmi.bios.date: 02/24/2026 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: N42ET97W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21N10001US dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN ptal����8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN42ET97W(2.27):bd02/24/2026:br2.27:efr1.32:svnLENOVO:pn21N10001US:pvrThinkPadT14sGen6:rvnLENOVO:rn21N10001US:rvrSDK0T76576WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21N1_BU_Think_FM_ThinkPadT14sGen6:pfaThinkPadT14sGen6: dmi.product.family: ThinkPad T14s Gen 6 dmi.product.name: 21N10001US dmi.product.sku: LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6 dmi.product.version: ThinkPad T14s Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158523/+subscriptions
[Bug 2158514] [NEW] [Dell Vostro 3520] CS8409/CS42L42 headset mic regression: works on 6.17.0-20, broken on 6.17.0-35 (HWE 24.04)
Public bug reported: The 3.5mm combo-jack headset microphone stopped working after a kernel update on a Dell Vostro 3520 (PCI SSID 1028:0b94, codec CS8409/CS42L42). == Summary == - Wired headset mic works correctly on 6.17.0-20.20~24.04.1-generic - Wired headset mic produces only silence on 6.17.0-35.35~24.04.1-generic - Internal mic and all audio output work on both kernels - This is a clean A/B regression between these two HWE point releases == Steps to reproduce (on -35) == 1. Plug a headset into the 3.5mm combo jack 2. Record: arecord -d 5 -f cd test.wav && aplay test.wav 3. Result: silence. No signal in pavucontrol input meter either. The 'Mic' ALSA control has a volume slider but no capture switch, and no separate headset-mic source appears in PipeWire. == Investigation already done == Both kernels are built on the same mainline stable base (6.17.13). The CS8409 codec init is BIT-IDENTICAL on good and bad kernels: picked fixup for PCI SSID 1028:0b94 Internal Mic=0x44 Mic=0x34 i2c-designware enumeration is also identical. So the regression is NOT in the cs8409 codec driver or its i2c path -- the codec is configured the same way on both. The break appears to be in the ALSA/HDA core capture path or another subsystem between -20 and -35. There are 926 commits between the two tags; none touch sound/hda/codecs/cirrus/ or patch_cs8409.*. Candidates worth checking in the HDA/i2c/gpio area include: 83827930c184 i2c: designware: Disable SMBus interrupts ... 687ba06f49b2 gpiolib: acpi: Add quirk for Dell Precision 7780 I can build kernels and run a full git bisect between Ubuntu-hwe-6.17-6.17.0-20.20_24.04.1 (good) and Ubuntu-hwe-6.17-6.17.0-35.35_24.04.1 (bad) if that would help. Possibly related historical bugs: LP #1972815, LP #1918378. NOTE: Reported manually because the system runs Zorin OS (Ubuntu 24.04 base) and apport refused the kernel as a non-official package. The affected kernel is the standard Ubuntu HWE 6.17 kernel. Logs (uname, version_signature, dmesg, lspci -vvnn) are attached. == System == - Hardware: Dell Vostro 3520 - Codec: CS8409 / CS42L42, PCI SSID 1028:0b94 - Distro: Zorin OS (Ubuntu 24.04 base), HWE 6.17 kernel - Good: 6.17.0-20.20~24.04.1-generic - Bad: 6.17.0-35.35~24.04.1-generic ** 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/2158514 Title: [Dell Vostro 3520] CS8409/CS42L42 headset mic regression: works on 6.17.0-20, broken on 6.17.0-35 (HWE 24.04) Status in linux package in Ubuntu: New Bug description: The 3.5mm combo-jack headset microphone stopped working after a kernel update on a Dell Vostro 3520 (PCI SSID 1028:0b94, codec CS8409/CS42L42). == Summary == - Wired headset mic works correctly on 6.17.0-20.20~24.04.1-generic - Wired headset mic produces only silence on 6.17.0-35.35~24.04.1-generic - Internal mic and all audio output work on both kernels - This is a clean A/B regression between these two HWE point releases == Steps to reproduce (on -35) == 1. Plug a headset into the 3.5mm combo jack 2. Record: arecord -d 5 -f cd test.wav && aplay test.wav 3. Result: silence. No signal in pavucontrol input meter either. The 'Mic' ALSA control has a volume slider but no capture switch, and no separate headset-mic source appears in PipeWire. == Investigation already done == Both kernels are built on the same mainline stable base (6.17.13). The CS8409 codec init is BIT-IDENTICAL on good and bad kernels: picked fixup for PCI SSID 1028:0b94 Internal Mic=0x44 Mic=0x34 i2c-designware enumeration is also identical. So the regression is NOT in the cs8409 codec driver or its i2c path -- the codec is configured the same way on both. The break appears to be in the ALSA/HDA core capture path or another subsystem between -20 and -35. There are 926 commits between the two tags; none touch sound/hda/codecs/cirrus/ or patch_cs8409.*. Candidates worth checking in the HDA/i2c/gpio area include: 83827930c184 i2c: designware: Disable SMBus interrupts ... 687ba06f49b2 gpiolib: acpi: Add quirk for Dell Precision 7780 I can build kernels and run a full git bisect between Ubuntu-hwe-6.17-6.17.0-20.20_24.04.1 (good) and Ubuntu-hwe-6.17-6.17.0-35.35_24.04.1 (bad) if that would help. Possibly related historical bugs: LP #1972815, LP #1918378. NOTE: Reported manually because the system runs Zorin OS (Ubuntu 24.04 base) and apport refused the kernel as a non-official package. The affected kernel is the standard Ubuntu HWE 6.17 kernel. Logs (uname, version_signature, dmesg, lspci -vvnn) are attached. == System == - Hardware: Dell Vostro 3520 - Codec: CS8409 / CS42L42, PCI SSID 1028:0b94 - Distro: Zorin OS (Ubuntu 24.04 base), HWE 6.17 kernel - Good: 6.17.0-20.20~24.04.1-generic - Bad: 6.17.0-35.35~24.04.1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158514/+subscriptions
пятница
[Bug 2154075] Re: [REGRESSION] ASUS Zenbook S16 UM5606GA (Ryzen AI 9 HX470) graphical freeze before login with Ubuntu 26.04 kernel 7.0.x, fixed by kernel 6.17
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154075 Title: [REGRESSION] ASUS Zenbook S16 UM5606GA (Ryzen AI 9 HX470) graphical freeze before login with Ubuntu 26.04 kernel 7.0.x, fixed by kernel 6.17 Status in linux package in Ubuntu: Confirmed Bug description: System experiences a reproducible graphical freeze during boot on Ubuntu 26.04 when using Ubuntu kernel 7.0.x. Hardware: * ASUS Zenbook S16 UM5606GA * AMD Ryzen AI 9 HX470 * integrated AMD graphics * BIOS version: UM5606GA.305 * BIOS date: 2026-02-25 * Secure Boot enabled Affected kernels: * 7.0.0-15-generic (fails) Known-good kernels: * 6.17.0-29-generic (works correctly) The issue appears shortly before the graphical login prompt should appear. Symptoms: * display freezes before login screen * mouse cursor may briefly move after resume from suspend * GUI remains visually frozen * keyboard and GUI actions occasionally appear after subsequent wake events * SSH access continues to function normally * system does not panic or reboot This suggests the kernel remains operational while the graphics/display stack hangs. Environment: * Ubuntu 26.04 userspace * GNOME * both Wayland and Xorg tested * same Mesa userspace for both working and failing kernels Regression evidence: The following configuration changes were tested and reverted unless otherwise noted: 1. Booting Ubuntu 26.04 live environment using "Safe graphics" Result: * works correctly 2. Booting installed system with: nomodeset Result: * works correctly * accelerated graphics unavailable 3. GRUB: set gfxpayload=keep Result: * Ubuntu live environment boots correctly in safe graphics mode 4. Kernel parameter: amdgpu.dcdebugmask=0x12 Result: * no improvement 5. Kernel parameter: amdgpu.mes=0 Result: * no improvement 6. Kernel parameter: amdgpu.dc=0 Result: * system freezes earlier during splash screen * SSH remains operational 7. Kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Result: * no improvement 8. Kernel parameter: pcie_aspm=off Result: * no improvement 9. Forced Xorg instead of Wayland Result: * same behavior 10. Replaced /lib/firmware/amdgpu firmware files with Ubuntu 24.04 versions Result: * no improvement * reverted afterward 11. Ubuntu 24.04 live environment Result: * boots correctly without safe graphics 12. Installed Ubuntu kernel: 6.17.0-29-generic Packages installed: * linux-headers-6.17.0-29-generic * linux-image-6.17.0-29-generic * linux-modules-6.17.0-29-generic * linux-tools-6.17.0-29-generic Result: * fully stable system * accelerated graphics functional * graphical login works correctly * suspend/resume functional Current working kernel: Linux aeon 6.17.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Tue May 5 19:42:34 UTC 2026 x86_64 GNU/Linux Conclusion: This appears to be a regression introduced in Ubuntu kernel 7.0.x affecting AMDGPU graphics initialization or display handling on Ryzen AI 9 HX470 / Strix Point hardware. The issue does not appear specific to: * GNOME * Wayland * Xorg * userspace Mesa because the same userspace environment works correctly under kernel 6.17. Suspected subsystem: * amdgpu * DRM/DCN * DMUB/DMCUB * modesetting * display core * Ryzen AI / Strix Point graphics enablement Potential duplicates / related reports: 1. Bug #2148753 linux-firmware-amd-graphics graphical boot regression on Ryzen AI ASUS Zenbook systems https://bugs.launchpad.net/ubuntu/+source/linux-firmware-amd-graphics/+bug/2148753 Mirror: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg6269039.html 2. Bug #2147541 Ryzen AI platform regression under Ubuntu 26.04 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147541 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 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sat May 23 17:32:03 2026 InstallationDate: Installed on 2026-05-15 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS Zenbook S16 UM5606GA 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-15-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 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: 02/25/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM5606GA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM5606GA 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.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5606GA.305:bd02/25/2026:br5.35:efr3.3:svnASUS:pnZenbookS16UM5606GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5606GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaZenbookS16: dmi.product.family: Zenbook S16 dmi.product.name: Zenbook S16 UM5606GA 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/2154075/+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)
I have used AI intensively for the last 3 days in order to back track my steps, review them over and over again; and finally spot the solution. Not sure if this can help someone but for sure helped me, hope this documentation can be used for somebody else. -- 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 2158440] [NEW] kernel-7.0.0-22 thermal regression
Public bug reported: My Dell Vostro 5515 hits 100°C even when only running Chrome. Switching from kernel 7.0.0-22 to 7.0.0-14 fixed the overheating. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 20:39:35 2026 InstallationDate: Installed on 2026-01-08 (169 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: Dell Inc. Vostro 5515 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=95a0af7d-0884-47b9-ae31-23fe2749a34c ro 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-04-24 (63 days ago) dmi.bios.date: 02/26/2025 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.28.0 dmi.board.name: 078X6R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.28.0 dmi.modalias: dmi:bvnDellInc.:bvr1.28.0:bd02/26/2025:br5.3:svnDellInc.:pnVostro5515:pvr1.28.0:rvnDellInc.:rn078X6R:rvrA00:cvnDellInc.:ct10:cvr1.28.0:sku0A7A:pfaVostro: dmi.product.family: Vostro dmi.product.name: Vostro 5515 dmi.product.sku: 0A7A dmi.product.version: 1.28.0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-thermal-regression regression-update resolute wayland-session ** Attachment added: "kernel-7.0.0-22-thermal-regression-summary.txt" https://bugs.launchpad.net/bugs/2158440/+attachment/5979099/+files/kernel-7.0.0-22-thermal-regression-summary.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158440 Title: kernel-7.0.0-22 thermal regression Status in linux package in Ubuntu: New Bug description: My Dell Vostro 5515 hits 100°C even when only running Chrome. Switching from kernel 7.0.0-22 to 7.0.0-14 fixed the overheating. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 20:39:35 2026 InstallationDate: Installed on 2026-01-08 (169 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: Dell Inc. Vostro 5515 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=95a0af7d-0884-47b9-ae31-23fe2749a34c ro 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-04-24 (63 days ago) dmi.bios.date: 02/26/2025 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.28.0 dmi.board.name: 078X6R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.28.0 dmi.modalias: dmi:bvnDellInc.:bvr1.28.0:bd02/26/2025:br5.3:svnDellInc.:pnVostro5515:pvr1.28.0:rvnDellInc.:rn078X6R:rvrA00:cvnDellInc.:ct10:cvr1.28.0:sku0A7A:pfaVostro: dmi.product.family: Vostro dmi.product.name: Vostro 5515 dmi.product.sku: 0A7A dmi.product.version: 1.28.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158440/+subscriptions
[Bug 2158377] [NEW] ext4: writeback causes kernel oops when low on space
Public bug reported: 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: High Assignee: Manuel Diewald (diewald) Status: In Progress ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Manuel Diewald (diewald) ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Invalid -- 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: In Progress 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 2156858] Re: [SRU] Fix GPU throttling limits on Strix Halo
For OEM-6.17: https://kernel.ubuntu.com/forgejo/kernel/noble-linux- oem/pulls/432 For 7.0 generic: https://lists.ubuntu.com/archives/kernel- team/2026-June/169539.html -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156858 Title: [SRU] Fix GPU throttling limits on Strix Halo Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2156858 [ Impact ] We found that setting power_dpm_force_performance_level to high and running heavy workload on Strix Halo platforms somehow makes it reboot. This is due to the throttling limits in amdgpu don't aligned with the power management firmware properly. [ Fix ] Cherry-pick the following commit: - 03b70e0d8aa26bab (drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range) which has been accepted since mainline v7.1 [ Test ] 1. Boot the kernel 2. Run the same compute workload on a Strix Halo system, and it shouldn't reboot. [ Where problems could occur ] If the driver throttles to aggressively this may impact performance, but this is safer than letting Strix Halo burn. [ Additional Information ] https://github.com/torvalds/linux/commit/03b70e0d8aa26bab89a0f1394c1c80a871925e42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156858/+subscriptions
[Bug 2151747] Re: AppArmor Vulnerabilities
This bug is awaiting verification that the linux-xuantie/7.0.0-1004.4 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-xuantie' to 'verification-done- resolute-linux-xuantie'. If the problem still exists, change the tag 'verification-needed-resolute-linux-xuantie' to 'verification-failed- resolute-linux-xuantie'. 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-xuantie-v2 verification-needed-resolute-linux-xuantie -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151747 Title: AppArmor Vulnerabilities Status in linux package in Ubuntu: Fix Released Bug description: Tracking the following commits: apparmor: fix NULL pointer dereference in unpack_pdb apparmor: fix NULL pointer dereference in bind_map_addr apparmor: fix use of unintialized variable in net opt level apparmor: fix possible NULL pointer dereference by adding a NULL check apparmor: fix sleep prone memory allocation under a spin_lock apparmor: remove redundant kref_init for listener->count apparmor: fix dfa unpacking size of the notification filter apparmor: fix size check against type instead of pointer apparmor: fix changing rules list without a lock apparmor: initialize variable used in uninitialized context apparmor: fix name validation bypass on notification apparmor: fix glob memory leak after kstrdup apparmor: pass big_resp to handler apparmor: fix inverted NULL check after aa_get_buffer apparmor: Fix incorrect profile->signal range check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151747/+subscriptions
[Bug 2154172] Re: GRO managed-frag use-after-free leading to local privilege escalation
This bug is awaiting verification that the linux-xuantie/7.0.0-1004.4 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-xuantie' to 'verification-done- resolute-linux-xuantie'. If the problem still exists, change the tag 'verification-needed-resolute-linux-xuantie' to 'verification-failed- resolute-linux-xuantie'. 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-xuantie-v2 verification-needed-resolute-linux-xuantie -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154172 Title: GRO managed-frag use-after-free leading to local privilege escalation Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux source package in Resolute: Fix Released Bug description: [ Impact ] skb_gro_receive() in net/core/gro.c transfers frag descriptors from a source skb into a GRO accumulator without checking the SKBFL_MANAGED_FRAG_REFS flag. A managed-frag skb does not hold a per-frag page reference; the caller owns page lifetime. When such frags are appended to a non-managed accumulator, skb_release_data() later calls put_page() on frags it never get_page()'d, producing a page refcount underflow. The resulting use-after-free is reachable by an unprivileged local user via io_uring SEND_ZC with fixed buffers over a GRO-enabled interface, and yields local privilege escalation. The bug was introduced upstream by commit 753f1ca4e1e5 ("net: introduce managed frags infrastructure"), which first landed in v5.20/v6.0. [ Fix ] commit 4db79a322db8c97f7b73b8a347395ef4d685eb40 ("net: gro: don't merge zcopy skbs") Refuse to merge in skb_gro_receive() when either side has SKBFL_MANAGED_FRAG_REFS or any zerocopy flag set. Landed in net.git for v7.1-rc5. [ Test Plan ] A user-space reproducer is run on a VM with the candidate kernel installed. sha256(/etc/passwd) is captured pre and post. Patched kernel: reproducer self-reports failure, sha256 unchanged. Unpatched kernel: reproducer succeeds, sha256 changes during the run. [ Where Problems Could Occur ] The fix only refuses a merge in a case that was always unsafe. The visible effect is that GRO occasionally produces one more segment-sized skb than otherwise on flows that mix managed and non-managed frags. Tiny throughput change in an uncommon path, no crash or correctness risk. No userspace API change, no kernel ABI change, no module change. [ Other Info ] No CVE ID assigned at the time of filing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154172/+subscriptions