Ever since 7.0.0.30 was rolled out I have not had this issue occur, perhaps it is due to the kernel itself or other system updates that were rolled out along with it. 7.0.0.31 also does not have this issue, so I'm assuming the issue was addressed by the kernel update or system updates, but after several reboots and fresh starts using the newer kernels the problem has vanished for me. I didn't do any other configuration changes as I was relying on my script to mitigate the issue but since 7.0.0.30 my script hasn't executed once and I have gone days and days without any issues. Laying my script to rest and moving on with life as usual. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: Fix Released Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions
пятница
[Bug 2156644] Re: GNOME Panel & Activities Overview workspace thumbnails flickering issue
Ever since 7.0.0.30 was rolled out I have not had this issue occur, perhaps it is due to the kernel itself or other system updates that were rolled out along with it. 7.0.0.31 also does not have this issue. ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: Fix Released Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions
[Bug 2166998] Re: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701)
** Tags added: linux-firmware-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166998 Title: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701) Status in linux package in Ubuntu: Confirmed Status in linux-firmware-misc package in Ubuntu: Confirmed Bug description: speakers silent while HDMI, Bluetooth and headphone jack work; audio worked under Windows; subsystem ID 0x10433701; dmesg showing speaker_outs=0 with the generic driver; mixer unmuted with Auto-Mute disabled; and the workarounds that failed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: alsa-base 1.0.25+dfsg-0ubuntu9 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ajit 4051 F.... pipewire ajit 4064 F.... wireplumber /dev/snd/seq: ajit 4051 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 21:42:10 2026 InstallationDate: Installed on 2026-09-06 (4 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK P5406CCA PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 5.32 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: P5406CCA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P5406CCA 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: 2.11 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrP5406CCA.203:bd03/20/2026:br5.32:efr2.11:svnASUS:pnASUSEXPERTBOOKP5406CCA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP5406CCA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK P5406CCA 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/2166998/+subscriptions
[Bug 2167089] Re: ASUS TUF Gaming A15 FA506NCG intermittently fails to resume reliably from s2idle suspend on Ubuntu 26.04
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167089 Title: ASUS TUF Gaming A15 FA506NCG intermittently fails to resume reliably from s2idle suspend on Ubuntu 26.04 Status in linux package in Ubuntu: New Bug description: I am experiencing intermittent suspend/resume failures on Ubuntu 26.04 LTS on an ASUS TUF Gaming A15 FA506NCG. Hardware: * ASUS TUF Gaming A15 FA506NCG * AMD Ryzen 7 7445HS * Integrated AMD Radeon 740M * NVIDIA GeForce RTX 3050 * Current kernel: 7.0.0-31-generic Suspend used to work reliably on this same machine. After system/kernel updates, suspend became unreliable and I eventually stopped using it because intermittent failures made it unsafe for a production/work machine. The system uses s2idle. In successful diagnostic tests, the kernel logs showed a complete suspend/resume sequence: PM: suspend entry (s2idle) ... amdgpu 0000:05:00.0: SMU is resumed successfully! ... PM: suspend exit The AMD PMC debug information after one successful manual suspend also showed: Last S0i3 Status: Success Time to S0i3: 312545 us Time in S0i3: 168579 us Time to resume from S0i3: 187317 us This indicates that the machine is capable of successfully entering and leaving S0i3/s2idle. However, suspend is not reliable in normal use. Intermittently, after suspending the notebook, the system does not return to a reliably usable state and may require a forced power-off. Because the failure is intermittent, individual manual suspend tests can succeed while normal usage later fails. The problem was observed both in normal notebook usage involving lid- close suspend and during the period when suspend was configured as the normal sleep action. Some previously collected kernel logs also contained ACPI/firmware warnings around the power-management environment, including: ACPI Error: AE_NOT_FOUND involving _SB_.PLTF.C00C through C00F and: Firmware Bug: WQ00 data block query control method not found Expected result: Suspend/resume should work reliably every time. The notebook should enter s2idle and restore the existing graphical session without freezes or requiring a forced shutdown. Actual result: Suspend/resume is intermittent. Although some cycles complete successfully according to amd_pmc and kernel logs, other real-world suspend/resume cycles make the notebook unreliable or unusable and can require forced power-off. Regression information: Suspend worked correctly on this same notebook previously. The reliability problems appeared after Ubuntu/kernel updates. I have therefore disabled automatic suspend on AC and battery as a workaround: org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type = 'nothing' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type = 'nothing' This is a production/work notebook, so repeatedly testing unstable suspend/resume is not a practical workaround. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: davi 5222 F.... wireplumber /dev/snd/controlC0: davi 5222 F.... wireplumber /dev/snd/controlC1: davi 5222 F.... wireplumber /dev/snd/seq: davi 5199 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 09:16:40 2026 HibernationDevice: RESUME=UUID=f8c71c5e-b42c-447c-8bc3-ba41f79feb35 InstallationDate: Installed on 2026-06-12 (91 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506NCG_FA506NCG ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=02541ac4-8171-4fd6-8b5a-dfae21ab0c80 ro quiet splash resume=UUID=f8c71c5e-b42c-447c-8bc3-ba41f79feb35 amdgpu.dc=1 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/11/2026 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA506NCG.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506NCG 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.4 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA506NCG.304:bd03/11/2026:br5.29:efr3.4:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506NCG_FA506NCG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506NCG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFGamingA15: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA506NCG_FA506NCG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167089/+subscriptions
[Bug 2167115] Re: amd_pmc: hard hang entering s2idle on ThinkPad P14s Gen 6 AMD (Ryzen AI 9 HX PRO 370)
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167115 Title: amd_pmc: hard hang entering s2idle on ThinkPad P14s Gen 6 AMD (Ryzen AI 9 HX PRO 370) Status in linux package in Ubuntu: New Bug description: # amd_pmc: hard hang entering s2idle on ThinkPad P14s Gen 6 AMD (Ryzen AI 9 HX PRO 370) ## Summary On a Lenovo ThinkPad P14s Gen 6 AMD, entering suspend-to-idle wedges the machine permanently. The kernel writes `PM: suspend entry (s2idle)` and never returns. There is no oops, no panic, no watchdog reset — the system is simply dead and only a hard power-off recovers it. **Unloading `amd_pmc` makes suspend work reliably. Reloading it brings the hang straight back.** This was verified as an A/B/A within four minutes on an otherwise idle machine. The hang is *past* every device suspend callback (proven with `/sys/power/pm_test`), so it is in the platform/SMU hardware-entry path rather than in any device driver. ## Affected system | | | |---|---| | Model | Lenovo ThinkPad P14s Gen 6 AMD, `21RV0016CK` | | CPU | AMD Ryzen AI 9 HX PRO 370 w/ Radeon 890M (family 26, model 36, stepping 0) | | BIOS | LENOVO `R2XET40W (1.20 )`, 2026-05-26 (latest available per `fwupdmgr get-upgrades`) | | Distro | Ubuntu 25.10 (Questing Quokka) | | Kernels | 6.17.0-41-generic **and** 6.17.0-40-generic — both affected | | Driver | `amd_pmc`, `CONFIG_AMD_PMC=m`, ACPI device `AMDI000A:00` | | SMU | `smu_fw_version` 93.23.0, `smu_program` 11 | | Sleep | `/sys/power/state` = `freeze mem`; `mem_sleep` = `[s2idle]`; no S3 offered by firmware | | | `Low-power S0 idle used by default for system suspend` | Kernel command line: ``` BOOT_IMAGE=/boot/vmlinuz-6.17.0-41-generic root=UUID=... ro quiet splash amd_pstate=active resume=UUID=... resume_offset=123500544 amdgpu.sg_display=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 ``` `amd_pmc` probes silently — it emits no messages at all on a normal boot. ## Symptom Every log ends identically: ``` kernel: PM: suspend entry (s2idle) <nothing further; journal never flushed> ``` No resume, no error return, no `last_failed_dev`. `/sys/power/suspend_stats` shows the attempt was never completed rather than failed. ## Reproducer ```sh modprobe amd_pmc # if not already loaded rtcwake -m mem -s 20 # or: echo mem > /sys/power/state ``` On this machine, since 2026-09-11 10:08 this hangs **100% of the time**. ## Evidence: A/B/A All timestamps 2026-09-11, same boot session where noted, machine otherwise idle. ### A — `amd_pmc` loaded: 7 hangs, 7 attempts | Time | Method | Kernel | Dock | Power | Result | |---|---|---|---|---|---| | 10:08:54 | logind (`systemctl suspend`) | 6.17.0-41 | docked | AC | hang | | 11:49:56 | logind | 6.17.0-41 | docked | AC | hang | | 12:47:48 | `rtcwake -m mem -s 20` | 6.17.0-41 | docked | AC | hang | | 12:55:55 | `rtcwake -m mem -s 20` | **6.17.0-40** | docked | AC | hang | | 13:11:05 | `echo mem > /sys/power/state` (no RTC alarm) | 6.17.0-41 | **undocked** | **battery** | hang | | 13:24:07 | plain write, from text VT, `pm_debug_messages=1` | 6.17.0-41 | undocked | battery | hang | | 13:31:23 | `rtcwake` — control, after reload | 6.17.0-41 | undocked | battery | hang | Independent of kernel version, dock state, AC vs battery, and suspend method. ### B — `amd_pmc` removed: 3 clean cycles ``` 13:28:28 ######## amd_pmc REMOVAL TEST kernel=6.17.0-41-generic cycles=3 ######## 13:28:28 before: amd_pmc loaded=1 refcnt=0 13:28:29 amd_pmc REMOVED ok (lsmod now: 0) 13:28:29 mem_sleep=[s2idle] state=freeze mem 13:28:29 START #1 (no amd_pmc) 13:28:35 RESUMED #1 rc=0 total_hw_sleep=0 13:28:40 START #2 (no amd_pmc) 13:28:46 RESUMED #2 rc=0 total_hw_sleep=0 13:28:51 START #3 (no amd_pmc) 13:28:55 RESUMED #3 rc=0 total_hw_sleep=0 13:29:00 ######## SURVIVED 3/3 WITHOUT amd_pmc ######## 13:29:00 amd_pmc reloaded ``` `total_hw_sleep` stays 0 without the driver, i.e. the SoC is not reaching deep s0ix — suspend/resume is simply shallower, but it works. ### A again — reloaded, hangs immediately ``` 13:31:23 ######## CONTROL: amd_pmc LOADED kernel=6.17.0-41-generic ######## 13:31:23 amd_pmc loaded=1 bound=1 13:31:23 START #1 (amd_pmc LOADED - expect hang) rtcwake: wakeup from "mem" using /dev/rtc0 at ... <dead> ``` This control rules out the alternative explanation that the failure window simply closed on its own between B and the end of A. ## What was ruled out **Phase bisect via `/sys/power/pm_test` — 30 cycles, 0 failures:** | Mode | Cycles | Result | |---|---|---| | `freezer` | 10 | clean | | `devices` | 10 | clean | | `platform` | 10 | clean | | `processors` | — | rejected: `PM: Unsupported test mode for suspend to idle` (-EAGAIN) | | `core` | — | rejected, same | `freezer`/`devices`/`platform` are the complete set s2idle accepts, and all pass. So task freezing, every device suspend callback, and ACPI platform prepare are all clean. The wedge is in what happens *after* those — the hardware entry. Also eliminated by direct test: - **Kernel regression** — 6.17.0-40 and 6.17.0-41 behave identically. - **Device drivers** — xHCI controllers, USB4/Thunderbolt routers (`NHI0`/`NHI1`), r8169 Wake-on-LAN: all covered by the clean `devices` stage. - **Dock / external display / USB-C** — hangs occur docked and undocked. - **AC vs battery** — hangs occur on both. - **`rtcwake` as a confound** — a plain `echo mem > /sys/power/state` with no RTC alarm hangs identically. - **Userspace** — hangs occur via logind and via a direct sysfs write that bypasses logind, NetworkManager teardown and all sleep hooks entirely. - **Out-of-tree modules** — `/proc/sys/kernel/tainted` = 0, none loaded. ## Why there is no trace to attach This is the frustrating part, and it is structural rather than a lack of trying: - **`pm_trace=1`** recorded nothing usable. The next boot read `PM: RTC time: 00:00:15, date: 2001-01-01` → `PM: Magic number: 1:0:0`, i.e. file hash 0 and dev hash 0 — no trace event was ever stored. Consistent with the hang being past all device callbacks, which is where `pm_trace` hooks. - **Console capture is impossible.** The hang is after device suspend, so amdgpu has already powered off the panel. Nothing printed after that point can be displayed, at any loglevel, on any VT. Confirmed empirically with `pm_debug_messages=1` + `console_suspend=N` from a text console: blank. - **netconsole / USB-serial** fail for the same reason — NIC and USB are already suspended at that point. The machine has no physical serial port. - **pstore** backend is `efi_pstore` only (no ramoops); it captures oops/panic, and a wedge is neither. `/sys/fs/pstore` is empty. No BERT, no MCE. ## Gap I could not close `/sys/kernel/debug/amd_pmc/` (`s0ix_stats`, `smu_fw_info`, `amd_pmc_idlemask`) is **unreadable even as root**, because the kernel is locked down under EFI Secure Boot: ``` Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 /sys/kernel/security/lockdown: none [integrity] confidentiality ``` If `s0ix_stats` would help, I can disable Secure Boot and re-run — please say so and I will attach it. ## Additional data point: the failure rate changed From 2026-08-18 to 2026-09-10 the hang rate was roughly **16% (10 hangs / 51 suspends)**. Since 2026-09-11 10:08 it has been **100% (7/7)**. Nothing in the software changed in that window — the only package activity was userspace (browsers, JDKs, mssql-tools); no kernel, firmware, or driver update, and the BIOS is unchanged. This suggests a state-dependent trigger that can latch, which may be a useful clue about the SMU handshake's failure mode. ## Workaround ```sh echo "blacklist amd_pmc" | sudo tee /etc/modprobe.d/blacklist-amd-pmc.conf sudo update-initramfs -u ``` Suspend then works; deep s0ix residency is lost, so sleep power draw increases. ## Happy to provide Anything else that would help — `acpidump`, full `dmesg`, `s0ix_stats` with Secure Boot disabled, or testing a patch or a debug kernel. The machine reproduces this 100% of the time right now, so patch turnaround is fast. ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-41-generic 6.17.0-41.41 ProcVersionSignature: Ubuntu 6.17.0-41.41-generic 6.17.13 Uname: Linux 6.17.0-41-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 16:13:30 2026 InstallationDate: Installed on 2025-12-03 (282 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 21RV0016CK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-41-generic root=UUID=2b934d1c-fc0d-4007-bf73-a6b393110cfd ro quiet splash amd_pstate=active resume=UUID=2b934d1c-fc0d-4007-bf73-a6b393110cfd resume_offset=123500544 amdgpu.sg_display=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2026 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: R2XET40W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 21RV0016CK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR2XET40W(1.20):bd05/26/2026:br1.20:efr1.12:svnLENOVO:pn21RV0016CK:pvrThinkPadP14sGen6AMD:rvnLENOVO:rn21RV0016CK:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21RV_BU_Think_FM_ThinkPadP14sGen6AMD: dmi.product.family: ThinkPad P14s Gen 6 AMD dmi.product.name: 21RV0016CK dmi.product.sku: LENOVO_MT_21RV_BU_Think_FM_ThinkPad P14s Gen 6 AMD dmi.product.version: ThinkPad P14s Gen 6 AMD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167115/+subscriptions
[Bug 2166998] Re: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701)
** Also affects: linux-firmware-misc (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware-misc (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/2166998 Title: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701) Status in linux package in Ubuntu: Confirmed Status in linux-firmware-misc package in Ubuntu: Confirmed Bug description: speakers silent while HDMI, Bluetooth and headphone jack work; audio worked under Windows; subsystem ID 0x10433701; dmesg showing speaker_outs=0 with the generic driver; mixer unmuted with Auto-Mute disabled; and the workarounds that failed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: alsa-base 1.0.25+dfsg-0ubuntu9 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ajit 4051 F.... pipewire ajit 4064 F.... wireplumber /dev/snd/seq: ajit 4051 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 21:42:10 2026 InstallationDate: Installed on 2026-09-06 (4 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK P5406CCA PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 5.32 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: P5406CCA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P5406CCA 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: 2.11 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrP5406CCA.203:bd03/20/2026:br5.32:efr2.11:svnASUS:pnASUSEXPERTBOOKP5406CCA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP5406CCA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK P5406CCA 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/2166998/+subscriptions
четверг
[Bug 2167009] Re: Regression in 6.8.0-139: resume from hibernation hangs (GSC proxy bind timeout); 6.8.0-138 unaffected with identical userspace
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167009 Title: Regression in 6.8.0-139: resume from hibernation hangs (GSC proxy bind timeout); 6.8.0-138 unaffected with identical userspace Status in linux package in Ubuntu: New Bug description: Hardware: CyberPowerPC / ASUS Z890 MAX GAMING WIFI7, BIOS 3002 (01/29/2026) CPU: Intel Core Ultra 9 285K (Arrow Lake) GPU: Intel Arrow Lake iGPU (i915) + NVIDIA RTX 4070 Ti SUPER (nvidia 595.84, DKMS) Kubuntu 24.04, X11/KDE Plasma Summary: Resume from hibernation reliably hangs on 6.8.0-139-generic. Booting 6.8.0-138-generic, with no other package changes, resumes from hibernation without any issues. This isolates the regression to the kernel package itself, not to userspace, initramfs, or firmware shipped alongside it. Details: The hibernation image is written and read back successfully. The restored kernel begins resuming devices and then never completes -- "PM: resume of devices complete" never prints. The machine is not frozen: it continues servicing timers indefinitely (observed for 5+ minutes without a hang or watchdog panic). Console output (captured with no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon): [ 52.940] PM: hibernation: Read 12721052 kbytes in 11.76 seconds [ 52.941] PM: Image successfully loaded [174.845] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin [174.865] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads [194.867] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout [194.873] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init [228.539] page_pool_release_retry() stalled pool shutdown: id 29, 7 inflight 60 sec (repeats at 120, 181, 241, 302, 362 sec ...) Note: mei_gsc_proxy binds correctly on resume from S3 (suspend-to-RAM) on this same machine; it only fails to bind after hibernation (S4). Also observed on the hibernate-entry path, one WARNING per CPU offlined (may be unrelated, noting for completeness): sysfs group 'package_00_die_00' not found for kobject 'intel_uncore_frequency' WARNING: at fs/sysfs/group.c:282 sysfs_remove_group+0x85/0x90 Call Trace: uncore_freq_remove_die_entry -> uncore_event_cpu_offline -> cpuhp_invoke_callback Steps to reproduce: 1. Boot 6.8.0-139-generic. 2. sudo systemctl hibernate (or via suspend-then-hibernate). 3. Power the machine back on. Expected: resumes normally. Actual: hangs indefinitely during device resume; only page_pool_release_retry warnings continue printing every ~60 seconds. Regression confirmed: Booted 6.8.0-138-generic with identical userspace/initramfs/firmware packages (only the running kernel differs). Hibernate/resume completed successfully with no issues. This confirms the regression is isolated to the 6.8.0-139 kernel package itself. Already ruled out: - nvidia DKMS module builds cleanly for 6.8.0-139; vermagic matches uname -r - Unloading all nvidia modules (nvidia_drm, nvidia_modeset, nvidia_uvm, nvidia) before hibernating does NOT fix the hang - CONFIG_DPM_WATCHDOG is not set in this kernel build, so no automatic panic/device name is produced on the hang; diagnosis required manual console capture via no_console_suspend Workaround in use: booting 6.8.0-138-generic until this is resolved. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: pm 3425 F.... wireplumber /dev/snd/controlC1: pm 3425 F.... wireplumber /dev/snd/controlC0: pm 3425 F.... wireplumber /dev/snd/seq: pm 3423 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 10 13:22:26 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (628 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-139-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2026 dmi.bios.release: 30.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd01/29/2026:br30.2:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167009/+subscriptions
[Bug 2166998] Re: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701)
Confirmed working. Two notes: On kernel 7.0, hda_model is a parameter of snd_sof_intel_hda_generic, not snd_sof_intel_hda_common. The original suggestion had no effect because /sys/module/snd_sof_intel_hda_common/parameters/hda_model does not exist on this kernel. With the corrected module name, internal speakers work: options snd-sof-intel-hda-generic hda_model=1043:1f1f /sys/module/snd_sof_intel_hda_generic/parameters/hda_model now reads 1043:1f1f and audio outputs correctly from the internal speakers on ASUS ExpertBook P5406CCA (subsystem 0x10433701). Thanks a lot. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166998 Title: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701) Status in linux package in Ubuntu: Confirmed Bug description: speakers silent while HDMI, Bluetooth and headphone jack work; audio worked under Windows; subsystem ID 0x10433701; dmesg showing speaker_outs=0 with the generic driver; mixer unmuted with Auto-Mute disabled; and the workarounds that failed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: alsa-base 1.0.25+dfsg-0ubuntu9 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ajit 4051 F.... pipewire ajit 4064 F.... wireplumber /dev/snd/seq: ajit 4051 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 21:42:10 2026 InstallationDate: Installed on 2026-09-06 (4 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK P5406CCA PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 5.32 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: P5406CCA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P5406CCA 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: 2.11 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrP5406CCA.203:bd03/20/2026:br5.32:efr2.11:svnASUS:pnASUSEXPERTBOOKP5406CCA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP5406CCA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK P5406CCA 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/2166998/+subscriptions
[Bug 2158229] Re: MT7925 wifi is hard blocked on Dell's machine
It looks like this "fix" completely destroyed MT7925 on Lenovo Thinkpad P14s (and probably others). Previously the hardware was woken up every second and now it silently goes to sleep and wakes - never. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158229 Title: MT7925 wifi is hard blocked on Dell's machine Status in linux package in Ubuntu: New Status in linux-hwe-7.0 package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-hwe-7.0 source package in Noble: Fix Released Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Won't Fix Status in linux-hwe-7.0 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Fix Released Status in linux-hwe-7.0 source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux source package in Stonking: New Status in linux-hwe-7.0 source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Impact] The Wi-Fi is hard blocked on Dell systems (CIDs: 202505-36757, 202501-36195, 202501-36253) and HP systems with Mediatek MT7925 cards. The wireless connection cannot be used. The rfkill state shows: $ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Fix] We revert the hardware rfkill polling feature for Mediatek MT7925 cards. This polling feature was introduced upstream in v6.16. We also revert the local DMI quirk for HP systems since polling is now disabled. Reverted commits: • Revert "wifi: mt76: mt7925: add rfkill_poll for hardware rfkill" (reverts upstream commit e54b870212c079bef4ff61238f8c1278a14d1863 from v6.16) • Revert local DMI quirk commit for HP systems (reverts local commit 20c9b07dcea9d49c876c9532a48a6dc88f43d0f9) [Test Plan] Check the rfkill state on affected hardware: $ rfkill list Without the patches: The Wireless LAN interface shows "Hard blocked: yes". The Wi-Fi connection does not work. With the patches: The Wireless LAN interface shows "Hard blocked: no". The Wi-Fi connection works. [Where problems could occur] This change affects the mt76 Mediatek wireless driver. If a system has a physical wireless switch that needs software polling, the switch will stop working. Toggling the physical switch would not change the Wi-Fi block state. ========================================================= [Impact] The wifi is hard blocked and can't be used randomly. [Test] 1. Boot up Machine 2. Run `rfkill list` to check wlan0 block state Wireless: Mediatek Inc. - 14c3:7925 ubuntu@localhost:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Affected Machines] 202505-36757 202501-36195 202501-36253 [Similar Issue] https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.14/+bug/2127044 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1020-oem 6.17.0-1020.20 ProcVersionSignature: Ubuntu 6.17.0-1020.20-oem 6.17.13 Uname: Linux 6.17.0-1020-oem x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1918 F.... pipewire ubuntu 1922 F.... wireplumber /dev/snd/controlC0: ubuntu 1922 F.... wireplumber /dev/snd/seq: ubuntu 1918 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Jun 25 05:43:16 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-proposed-20250604-520 InstallationDate: Installed on 2026-05-07 (49 days ago) InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250603) IwConfig: lo no wireless extensions. enp195s0f0 no wireless extensions. wlp194s0 no wireless extensions. MachineType: Dell Inc. Dell Pro Max 14 MC14255 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1020-oem root=UUID=881d0e73-6adc-444d-90b2-9491672e82b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.17.0-1020-oem N/A linux-backports-modules-6.17.0-1020-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2025 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0WT010 dmi.board.vendor: Dell Inc. dmi.board.version: D01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd09/09/2025:br1.4:efr1.3:svnDellInc.:pnDellProMax14MC14255:pvr:rvnDellInc.:rn0WT010:rvrD01:cvnDellInc.:ct10:cvr:sku0D80: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 MC14255 dmi.product.sku: 0D80 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158229/+subscriptions
[Bug 2161004] Re: [SRU] HPE: Fix for UBSAN array-index-out-of-bounds
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161004 Title: [SRU] HPE: Fix for UBSAN array-index-out-of-bounds Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux source package in Stonking: Fix Committed Bug description: [ Impact ] When UBSAN is enabled, multiple array-index-out-of-bounds messages are printed: [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:276:23 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:277:32 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:282:16 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.515850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1344:23 [ 0.519851] [ T1] index 1 is out of range for type '<unknown> [1]' ... [ 0.603850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1345:32 [ 0.607850] [ T1] index 1 is out of range for type '<unknown> [1]' ... [ 0.691850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1353:20 [ 0.695850] [ T1] index 1 is out of range for type '<unknown> [1]' One-element arrays have been deprecated: [ Fix ] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=21433d3e3ca14d20f9b0c2237b3d3a1355af7907 [ Test Plan ] Installed 24.04. apt upgrade to install the latest kernel (6.8.0-136). Reboot with 6.8.0-136. Confirmed UBSAN warning messages (same as bug description). Installed lp_2161004_ubsan_array_index deb packages. Reboot with new kernel Confirmed no UBSAM warning messages. Kernel without the fix (July 1 build date): [ 0.000000] Linux version 6.8.0-136-generic (buildd@lcy02-amd64-041) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #136-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 21:53:05 UTC 2026 (Ubuntu 6.8.0-136.136-generic 6.8.12) Kernel with the fix (July 16 build date): [ 0.000000] Linux version 6.8.0-136-generic (root@buildnoble) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #136 SMP PREEMPT_DYNAMIC Thu Jul 16 20:05:25 UTC 2026 (Ubuntu 6.8.0-136.136-generic 6.8.12) [ Where problems could occur ] The regression risk is low [ Other Info ] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/ubsan_array_index To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161004/+subscriptions
[Bug 2167019] [NEW] MT7925 Wi-Fi: silent data-path packet loss on associated link after pc-kernel 7.0.0-31.31
Public bug reported: The pc-kernel snap refresh from 7.0.0-28.28 (rev 3672) to 7.0.0-31.31 (rev 3699) breaks Wi-Fi data traffic on a MediaTek MT7925 [14c3:7925] (Filogic 360). The distinguishing symptom is that connection management keeps working while the data path does not. The card scans, authenticates, completes the WPA 4-way handshake and obtains its DHCP lease -- the same address every time -- then sits in the "activated" state looking healthy while almost no traffic completes. DNS resolution fails essentially continuously. No firmware crash, watchdog reset, or driver error is logged at any point. The link reports itself as connected with strong signal throughout, which makes this easy to misdiagnose as a DNS, VPN, or upstream network problem. Reverting to 7.0.0-28.28 restores full function immediately and reproducibly. [KEY EVIDENCE: FAILURE WHILE THE LINK IS PROVABLY STABLE] On a 12-minute boot of 7.0.0-31 there is a window from 12:21:11 to 12:29:20 -- just over eight minutes -- during which the interface was continuously associated, with ZERO deauthentication events and the DHCP lease held. Within that stable window there were 12 distinct DNS resolution failures, roughly one per minute, spread evenly across it. This rules out reconnection churn as the cause. The link was up, authenticated and addressed, and traffic still did not pass. The packet loss is the primary fault; the disconnects are secondary. [DNS FAILURES, BAD VS GOOD KERNEL] boot kernel duration "Temporary failure NoDnsConnectivity in name resolution" ---- ---------------- -------- ------------------ ----------------- -4 7.0.0-28-generic 16h 09m 0 0 -1 7.0.0-31-generic 12m 42 12 Zero failures in sixteen hours on the old kernel; 42 in twelve minutes on the new. [VERSIONS] GOOD BAD snap revision pc-kernel rev 3672 pc-kernel rev 3699 version 7.0.0-28.28 7.0.0-31.31 kernel 7.0.0-28-generic 7.0.0-31-generic MT7925 HW/SW build 20260106153007a 20260605184651a MT7925 WM firmware 20260106153120 20260605184805 PRIME SUSPECT: the kernel snap carries the MT7925 firmware blobs, and 7.0.0-31 bumps them from a 2026-01-06 build to a 2026-06-05 build. Given that association and control-plane exchanges succeed while bulk data silently fails, a firmware-side RX/TX data-path fault (aggregation, offload, or data-path key handling) seems more likely than a change in the mt7925e/mt76 driver code. These two should be bisected independently. [REPRODUCTION] 1. On MT7925 hardware, run pc-kernel 7.0.0-28.28 -- Wi-Fi is stable. 2. snap refresh pc-kernel to 7.0.0-31.31 (rev 3699). Reboot. 3. Associate to a 5 GHz AP. Association, 4-way handshake and DHCP all succeed; the interface reaches "activated" and holds a valid lease. 4. Attempt normal use. Traffic largely does not complete; DNS fails repeatedly while the link continues to report itself as connected. 5. snap revert pc-kernel to rev 3672 and reboot -- problem disappears entirely. Performed twice on this machine (two separate boots of 7.0.0-31, two reverts). [DISCONNECTS, CORRECTLY ATTRIBUTED] Six deauthentications occurred on the 12-minute boot, but they are not all spontaneous. By the NetworkManager state-change reason recorded at the same instant: 12:20:12 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:21:04 activated -> deactivating ('new-activation') operator reconnect 12:21:06 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:29:20 activated -> deactivating ('new-activation') operator reconnect 12:29:21 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:30:25 activated -> deactivating ('unmanaged') shutdown for reboot So three spontaneous interface resets in 12 minutes, not six; the rest were the operator manually reconnecting to try to recover, plus shutdown. The 16-hour 7.0.0-28 boot recorded two deauthentications in total. The spontaneous ones show the supplicant returning to "internal-starting", indicating the interface was re-initialised underneath userspace rather than roamed by choice -- consistent with a driver- or firmware-level reset. [HEALTHY BASELINE ON 7.0.0-28, FOR CONTRAST] ping 172.16.96.1 (gateway) 20 packets, 0% loss, rtt 2.203/2.825/6.265 ms ping 1.1.1.1 20 packets, 0% loss, rtt 7.042/9.424/15.675 ms ping 8.8.8.8 20 packets, 0% loss, rtt 7.739/10.719/15.754 ms signal -46 dBm rx bitrate 258.0 MBit/s HE-MCS 10 HE-NSS 2 tx bitrate 286.7 MBit/s HE-MCS 11 HE-NSS 2 tx retries 6 (of 9429 tx packets) tx failed 0 beacon loss 0 Signal is strong and error counters are essentially zero, so this is not a weak-signal or RF-congestion problem that merely coincided with the update. [CAVEATS FOR ANYONE REPRODUCING] 1. THE LOSS PERCENTAGE WAS NOT MEASURED. I observed roughly 80% packet loss while running 7.0.0-31, severe enough to make the machine unusable, but no ping statistics or interface counters were captured during either 7.0.0-31 boot and those counters do not survive a reboot. Treat 80% as a reported magnitude, not a measurement. What the logs independently establish is the 42 DNS failures, the 12 failures inside a provably stable 8-minute window, and the three spontaneous interface resets -- all specific to 7.0.0-31. 2. DNS ON THIS HOST IS DoH THROUGH A CLOUDFLARE WARP TUNNEL (operation_mode: WarpWithDnsOverHttps, tunnel MTU 1280), not plain UDP/53. DNS therefore depends on the tunnel, which depends on the Wi-Fi data path -- which is why DNS failure is such a visible symptom here. A machine without WARP may present less dramatically, as general packet loss rather than near-total DNS failure. Do not assume the absence of total DNS failure means the bug is absent; test the data path directly. The most useful capture on 7.0.0-31, while associated and stable, is: ping -c 200 -i 0.2 <gateway> # on-link, bypasses both tunnel and DNS ip -s link show wlp194s0 iw dev wlp194s0 station dump [IMPACT] linux-image-generic-hwe-26.04 currently has candidate 7.0.0-31.31 in resolute-updates, so this is the version being handed out. Any MT7925 (Filogic 360) system taking the update is likely to hit this. The MT7925 is common in current AMD laptops. The silent nature of the failure makes it worse than an outright breakage: the card reports itself as connected with a valid lease and good signal, so affected users are likely to blame their router, ISP, or VPN rather than the kernel. [CURRENT MITIGATION] snap revert pc-kernel # back to rev 3672 / 7.0.0-28.28 snap refresh --hold pc-kernel # prevents automatic re-update Both revisions are held; rev 3699 is retained but disabled, so it remains available for further testing without a re-download. [REQUESTED] 1. Confirm whether the MT7925 firmware bump (2026-01-06 -> 2026-06-05) is the cause, independent of the mt76/mt7925e driver changes in 7.0.0-31. 2. If so, consider reverting the firmware blob or gating it pending a fix. 3. Investigate why the data path fails silently while association, EAPOL and DHCP all succeed -- the absence of any logged error is itself a defect. [SYSTEM] Ubuntu 26.04.1 LTS (resolute), Ubuntu Core / snap-delivered kernel, x86_64 Wi-Fi: MEDIATEK MT7925 802.11be 160MHz 2x2 PCIe [Filogic 360] [14c3:7925] Subsystem: Lenovo [17aa:e025], PCI c2:00.0, driver mt7925e (mt76) AP: ch 116 (5580 MHz), 20 MHz, WPA2/3 Full diagnostics attached (mt7925-diagnostics.txt). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "regression-update resolute mt7925" https://bugs.launchpad.net/bugs/2167019/+attachment/5999324/+files/mt7925-diagnostics.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167019 Title: MT7925 Wi-Fi: silent data-path packet loss on associated link after pc-kernel 7.0.0-31.31 Status in linux package in Ubuntu: New Bug description: The pc-kernel snap refresh from 7.0.0-28.28 (rev 3672) to 7.0.0-31.31 (rev 3699) breaks Wi-Fi data traffic on a MediaTek MT7925 [14c3:7925] (Filogic 360). The distinguishing symptom is that connection management keeps working while the data path does not. The card scans, authenticates, completes the WPA 4-way handshake and obtains its DHCP lease -- the same address every time -- then sits in the "activated" state looking healthy while almost no traffic completes. DNS resolution fails essentially continuously. No firmware crash, watchdog reset, or driver error is logged at any point. The link reports itself as connected with strong signal throughout, which makes this easy to misdiagnose as a DNS, VPN, or upstream network problem. Reverting to 7.0.0-28.28 restores full function immediately and reproducibly. [KEY EVIDENCE: FAILURE WHILE THE LINK IS PROVABLY STABLE] On a 12-minute boot of 7.0.0-31 there is a window from 12:21:11 to 12:29:20 -- just over eight minutes -- during which the interface was continuously associated, with ZERO deauthentication events and the DHCP lease held. Within that stable window there were 12 distinct DNS resolution failures, roughly one per minute, spread evenly across it. This rules out reconnection churn as the cause. The link was up, authenticated and addressed, and traffic still did not pass. The packet loss is the primary fault; the disconnects are secondary. [DNS FAILURES, BAD VS GOOD KERNEL] boot kernel duration "Temporary failure NoDnsConnectivity in name resolution" ---- ---------------- -------- ------------------ ----------------- -4 7.0.0-28-generic 16h 09m 0 0 -1 7.0.0-31-generic 12m 42 12 Zero failures in sixteen hours on the old kernel; 42 in twelve minutes on the new. [VERSIONS] GOOD BAD snap revision pc-kernel rev 3672 pc-kernel rev 3699 version 7.0.0-28.28 7.0.0-31.31 kernel 7.0.0-28-generic 7.0.0-31-generic MT7925 HW/SW build 20260106153007a 20260605184651a MT7925 WM firmware 20260106153120 20260605184805 PRIME SUSPECT: the kernel snap carries the MT7925 firmware blobs, and 7.0.0-31 bumps them from a 2026-01-06 build to a 2026-06-05 build. Given that association and control-plane exchanges succeed while bulk data silently fails, a firmware-side RX/TX data-path fault (aggregation, offload, or data-path key handling) seems more likely than a change in the mt7925e/mt76 driver code. These two should be bisected independently. [REPRODUCTION] 1. On MT7925 hardware, run pc-kernel 7.0.0-28.28 -- Wi-Fi is stable. 2. snap refresh pc-kernel to 7.0.0-31.31 (rev 3699). Reboot. 3. Associate to a 5 GHz AP. Association, 4-way handshake and DHCP all succeed; the interface reaches "activated" and holds a valid lease. 4. Attempt normal use. Traffic largely does not complete; DNS fails repeatedly while the link continues to report itself as connected. 5. snap revert pc-kernel to rev 3672 and reboot -- problem disappears entirely. Performed twice on this machine (two separate boots of 7.0.0-31, two reverts). [DISCONNECTS, CORRECTLY ATTRIBUTED] Six deauthentications occurred on the 12-minute boot, but they are not all spontaneous. By the NetworkManager state-change reason recorded at the same instant: 12:20:12 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:21:04 activated -> deactivating ('new-activation') operator reconnect 12:21:06 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:29:20 activated -> deactivating ('new-activation') operator reconnect 12:29:21 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:30:25 activated -> deactivating ('unmanaged') shutdown for reboot So three spontaneous interface resets in 12 minutes, not six; the rest were the operator manually reconnecting to try to recover, plus shutdown. The 16-hour 7.0.0-28 boot recorded two deauthentications in total. The spontaneous ones show the supplicant returning to "internal-starting", indicating the interface was re-initialised underneath userspace rather than roamed by choice -- consistent with a driver- or firmware-level reset. [HEALTHY BASELINE ON 7.0.0-28, FOR CONTRAST] ping 172.16.96.1 (gateway) 20 packets, 0% loss, rtt 2.203/2.825/6.265 ms ping 1.1.1.1 20 packets, 0% loss, rtt 7.042/9.424/15.675 ms ping 8.8.8.8 20 packets, 0% loss, rtt 7.739/10.719/15.754 ms signal -46 dBm rx bitrate 258.0 MBit/s HE-MCS 10 HE-NSS 2 tx bitrate 286.7 MBit/s HE-MCS 11 HE-NSS 2 tx retries 6 (of 9429 tx packets) tx failed 0 beacon loss 0 Signal is strong and error counters are essentially zero, so this is not a weak-signal or RF-congestion problem that merely coincided with the update. [CAVEATS FOR ANYONE REPRODUCING] 1. THE LOSS PERCENTAGE WAS NOT MEASURED. I observed roughly 80% packet loss while running 7.0.0-31, severe enough to make the machine unusable, but no ping statistics or interface counters were captured during either 7.0.0-31 boot and those counters do not survive a reboot. Treat 80% as a reported magnitude, not a measurement. What the logs independently establish is the 42 DNS failures, the 12 failures inside a provably stable 8-minute window, and the three spontaneous interface resets -- all specific to 7.0.0-31. 2. DNS ON THIS HOST IS DoH THROUGH A CLOUDFLARE WARP TUNNEL (operation_mode: WarpWithDnsOverHttps, tunnel MTU 1280), not plain UDP/53. DNS therefore depends on the tunnel, which depends on the Wi-Fi data path -- which is why DNS failure is such a visible symptom here. A machine without WARP may present less dramatically, as general packet loss rather than near-total DNS failure. Do not assume the absence of total DNS failure means the bug is absent; test the data path directly. The most useful capture on 7.0.0-31, while associated and stable, is: ping -c 200 -i 0.2 <gateway> # on-link, bypasses both tunnel and DNS ip -s link show wlp194s0 iw dev wlp194s0 station dump [IMPACT] linux-image-generic-hwe-26.04 currently has candidate 7.0.0-31.31 in resolute-updates, so this is the version being handed out. Any MT7925 (Filogic 360) system taking the update is likely to hit this. The MT7925 is common in current AMD laptops. The silent nature of the failure makes it worse than an outright breakage: the card reports itself as connected with a valid lease and good signal, so affected users are likely to blame their router, ISP, or VPN rather than the kernel. [CURRENT MITIGATION] snap revert pc-kernel # back to rev 3672 / 7.0.0-28.28 snap refresh --hold pc-kernel # prevents automatic re-update Both revisions are held; rev 3699 is retained but disabled, so it remains available for further testing without a re-download. [REQUESTED] 1. Confirm whether the MT7925 firmware bump (2026-01-06 -> 2026-06-05) is the cause, independent of the mt76/mt7925e driver changes in 7.0.0-31. 2. If so, consider reverting the firmware blob or gating it pending a fix. 3. Investigate why the data path fails silently while association, EAPOL and DHCP all succeed -- the absence of any logged error is itself a defect. [SYSTEM] Ubuntu 26.04.1 LTS (resolute), Ubuntu Core / snap-delivered kernel, x86_64 Wi-Fi: MEDIATEK MT7925 802.11be 160MHz 2x2 PCIe [Filogic 360] [14c3:7925] Subsystem: Lenovo [17aa:e025], PCI c2:00.0, driver mt7925e (mt76) AP: ch 116 (5580 MHz), 20 MHz, WPA2/3 Full diagnostics attached (mt7925-diagnostics.txt). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167019/+subscriptions
[Bug 2167015] [NEW] System hangs on poweroff since kernel 7.0.0 series (regression) on ThinkPad L14 Gen1 AMD
Public bug reported: Since upgrading to kernel 7.0.0-28-generic (and confirmed also in 7.0.0-30 and 7.0.0-31), my system no longer powers off cleanly. This is a clear regression: kernel 6.17.0-40-generic works reliably on the exact same hardware/install. Hardware: Lenovo ThinkPad L14 Gen 1 AMD (Type 20U5/20U6), AMD Ryzen 5 PRO 4650U, BIOS R19ET56W (1.40). Distro: Linux Mint (based on Ubuntu 24.04 / noble, HWE kernel stack) Symptom: When shutting down, all systemd services stop cleanly and the log reaches "Reached target poweroff.target", "Syncing filesystems and block devices", "Sending SIGTERM to remaining processes" - then the journal stops. The screen goes black, but the fans keep spinning and the power LED stays on. The system never actually powers off; it requires a hard power-button hold to turn off. Tested and confirmed: - Broken: 7.0.0-28-generic, 7.0.0-30-generic, 7.0.0-31-generic - Working: 6.17.0-40-generic, 6.17.0-35-generic (both shut down cleanly every time) No custom kernel parameters were needed on the working kernels (default "quiet splash"). Testing with acpi=force / reboot=acpi / acpi_osi=Linux on the broken kernel did not help and even caused reboot to hang as well. This looks like a regression in ACPI/power-management handling introduced somewhere between 6.17.0-40 and 7.0.0-28. Steps to reproduce: 1. Boot into kernel 7.0.0-31-generic (or 7.0.0-28/30) 2. Run "sudo poweroff" or shut down via the desktop menu 3. Observe: screen turns black, fans keep running, power LED stays on, system never actually powers off Expected result: System powers off completely. Actual result: System hangs indefinitely until a hard power-button shutdown is performed. ** 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/2167015 Title: System hangs on poweroff since kernel 7.0.0 series (regression) on ThinkPad L14 Gen1 AMD Status in linux package in Ubuntu: New Bug description: Since upgrading to kernel 7.0.0-28-generic (and confirmed also in 7.0.0-30 and 7.0.0-31), my system no longer powers off cleanly. This is a clear regression: kernel 6.17.0-40-generic works reliably on the exact same hardware/install. Hardware: Lenovo ThinkPad L14 Gen 1 AMD (Type 20U5/20U6), AMD Ryzen 5 PRO 4650U, BIOS R19ET56W (1.40). Distro: Linux Mint (based on Ubuntu 24.04 / noble, HWE kernel stack) Symptom: When shutting down, all systemd services stop cleanly and the log reaches "Reached target poweroff.target", "Syncing filesystems and block devices", "Sending SIGTERM to remaining processes" - then the journal stops. The screen goes black, but the fans keep spinning and the power LED stays on. The system never actually powers off; it requires a hard power-button hold to turn off. Tested and confirmed: - Broken: 7.0.0-28-generic, 7.0.0-30-generic, 7.0.0-31-generic - Working: 6.17.0-40-generic, 6.17.0-35-generic (both shut down cleanly every time) No custom kernel parameters were needed on the working kernels (default "quiet splash"). Testing with acpi=force / reboot=acpi / acpi_osi=Linux on the broken kernel did not help and even caused reboot to hang as well. This looks like a regression in ACPI/power-management handling introduced somewhere between 6.17.0-40 and 7.0.0-28. Steps to reproduce: 1. Boot into kernel 7.0.0-31-generic (or 7.0.0-28/30) 2. Run "sudo poweroff" or shut down via the desktop menu 3. Observe: screen turns black, fans keep running, power LED stays on, system never actually powers off Expected result: System powers off completely. Actual result: System hangs indefinitely until a hard power-button shutdown is performed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167015/+subscriptions
[Bug 2167012] [NEW] System performs hard reset shortly after boot with kernel 7.0.0-31-generic
Public bug reported: Environment Hardware: XMG Focus 17 M25, NVIDIA RTX 5070 Ti (full 140-150W variant) Kernel (broken): linux-image-7.0.0-31-generic Kernel (working): linux-image-7.0.0-30-generic GPU driver: nvidia-driver-580-open, version 580.173.02, DKMS-built cleanly for both kernel versions Desktop environments installed: GNOME, KDE Plasma, XFCE Symptom Machine reboots abruptly with no warning while running kernel 7.0.0-31 journalctl -b -1 ends without any clean shutdown/reboot log entries Occurred multiple times in short succession (boots lasting ~2-3 minutes each) shortly after a kernel/driver update occurred on a freshly booted, idle system (ruled out thermal throttling via sensors / kernel thermal zone logs, which showed nothing abnormal) Under GNOME (Wayland) and KDE Plasma, the system crashed Under XFCE (X11, minimal), the system ran stably on the same kernel Downgraded/pinned to linux-image-7.0.0-30-generic (apt-mark hold on linux-image-generic-hwe-26.04, linux-generic-hwe-26.04, linux-headers- generic-hwe-26.04). System has been stable since. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Sep 10 21:06:00 2026 InstallationDate: Installed on 2026-08-28 (13 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: SchenkerTechnologiesGmbH XMG FOCUS 17 (M25) ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash intel_idle.max_cstate=1 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: 7.9 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.09RTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNx dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: N/A dmi.ec.firmware.release: 9.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.09RTR4:bd03/19/2026:br7.9:efr9.4:svnSchenkerTechnologiesGmbH:pnXMGFOCUS17(M25):pvrNotApplicable:rvnNB01:rnV3xxSNx:rvrNotApplicable:cvnSchenkerTechnologiesGmbH:ct10:cvrN/A:skuXFO17M25:pfa: dmi.product.name: XMG FOCUS 17 (M25) dmi.product.sku: XFO17M25 dmi.product.version: Not Applicable dmi.sys.vendor: SchenkerTechnologiesGmbH ** 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/2167012 Title: System performs hard reset shortly after boot with kernel 7.0.0-31-generic Status in linux package in Ubuntu: New Bug description: Environment Hardware: XMG Focus 17 M25, NVIDIA RTX 5070 Ti (full 140-150W variant) Kernel (broken): linux-image-7.0.0-31-generic Kernel (working): linux-image-7.0.0-30-generic GPU driver: nvidia-driver-580-open, version 580.173.02, DKMS-built cleanly for both kernel versions Desktop environments installed: GNOME, KDE Plasma, XFCE Symptom Machine reboots abruptly with no warning while running kernel 7.0.0-31 journalctl -b -1 ends without any clean shutdown/reboot log entries Occurred multiple times in short succession (boots lasting ~2-3 minutes each) shortly after a kernel/driver update occurred on a freshly booted, idle system (ruled out thermal throttling via sensors / kernel thermal zone logs, which showed nothing abnormal) Under GNOME (Wayland) and KDE Plasma, the system crashed Under XFCE (X11, minimal), the system ran stably on the same kernel Downgraded/pinned to linux-image-7.0.0-30-generic (apt-mark hold on linux-image-generic-hwe-26.04, linux-generic-hwe-26.04, linux-headers- generic-hwe-26.04). System has been stable since. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Sep 10 21:06:00 2026 InstallationDate: Installed on 2026-08-28 (13 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: SchenkerTechnologiesGmbH XMG FOCUS 17 (M25) ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash intel_idle.max_cstate=1 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: 7.9 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.09RTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNx dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: N/A dmi.ec.firmware.release: 9.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.09RTR4:bd03/19/2026:br7.9:efr9.4:svnSchenkerTechnologiesGmbH:pnXMGFOCUS17(M25):pvrNotApplicable:rvnNB01:rnV3xxSNx:rvrNotApplicable:cvnSchenkerTechnologiesGmbH:ct10:cvrN/A:skuXFO17M25:pfa: dmi.product.name: XMG FOCUS 17 (M25) dmi.product.sku: XFO17M25 dmi.product.version: Not Applicable dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167012/+subscriptions