apport information ** Tags added: apport-collected zena
** Description changed: **Title** [Noble HWE 7.0][amdgpu][RX 6650 XT] Intermittent poweroff hang; 6.14.0-37 works, 7.0.0-28 and 7.0.0-29 fail **Description** I am experiencing an intermittent shutdown/poweroff hang after moving from the Ubuntu Noble HWE 6.14 kernel to HWE 7.0. The issue is reproducible with both: * linux-image-7.0.0-28-generic 7.0.0-28.28~24.04.1 * linux-image-7.0.0-29-generic 7.0.0-29.29~24.04.2 The same machine shuts down reliably with: * linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 **Hardware** Motherboard: Gigabyte B550M DS3H rev. 1.4 BIOS: FF, 2025-10-28 GPU: AMD Radeon RX 6650 XT (Navi 23), amdgpu driver **Observed behaviour** When the problem occurs, shutdown starts normally and the displays turn off, but the computer does not complete the physical power-off. Reboot does not exhibit the issue. I have never reproduced the problem when rebooting the machine. The issue can also occur with: `sudo poweroff -f` This suggests that the problem is not simply caused by a userspace service failing to stop. **Kernel comparison** 6.14.0-37-generic: Poweroff works reliably. 7.0.0-28-generic: Intermittent poweroff hang. 7.0.0-29-generic: Intermittent poweroff hang. Reboot with the 7.0 kernels: Always works. This therefore appears to be a regression introduced between the Ubuntu HWE 6.14 and HWE 7.0 kernel series. **Shutdown logs** During a failed shutdown, userspace shutdown proceeds normally. Docker completes its shutdown successfully and NetworkManager exits successfully. The journal reaches the final `systemd-shutdown` stage: `systemd-shutdown[1]: Syncing filesystems and block devices.` `systemd-shutdown[1]: Sending SIGTERM to remaining processes...` The journal then stops as expected when systemd-journald is terminated. Shortly before this final shutdown phase, the kernel repeatedly reports messages similar to: `workqueue: drm_fb_helper_damage_work hogged CPU for >10000us, consider switching to WQ_UNBOUND` I do not know whether this DRM warning is causal, but I am mentioning it because it occurs immediately around the shutdown sequence on the affected kernels. **Related AMD shutdown fix** Ubuntu kernel 6.14.0-37 includes the fixes for LP #2115860 (“Poweroff not working consistently”), including several drm/amd shutdown/S5 fixes. However, the relevant shutdown/S5 behaviour appears to already exist in upstream Linux 7.0, so this does not appear to be simply a missing backport of LP #2115860. It may instead be a new regression in the 7.0 kernel series or an interaction exposed by later DRM/AMDGPU changes. **Steps to reproduce** 1. Boot kernel 7.0.0-28-generic or 7.0.0-29-generic. 2. Use the system normally. 3. Request a normal shutdown. 4. Intermittently, the displays turn off but the machine does not complete power-off. The same test has not reproduced the issue under 6.14.0-37-generic. **Expected result** The machine should completely power off. **Actual result** - The shutdown sequence reaches its final stage, but the machine - intermittently remains powered instead of completing power-off. + The shutdown sequence reaches its final stage, but the machine intermittently remains powered instead of completing power-off. + --- + ProblemType: Bug + ApportVersion: 2.28.3-0ubuntu0.1 + Architecture: amd64 + CRDA: N/A + CasperMD5CheckMismatches: ./boot/grub/efi.img + CasperMD5CheckResult: fail + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 22.3 + InstallationDate: Installed on 2026-07-22 (27 days ago) + InstallationMedia: Linux Mint 22.3 "Zena" - Release amd64 20260108 + IwConfig: + lo no wireless extensions. + + enp6s0 no wireless extensions. + + docker0 no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B550M DS3H + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=94102f42-dca2-4dbb-a722-190ea16c6d05 ro amdgpu.runpm=0 systemd.log_level=debug systemd.log_target=kmsg printk.devkmsg=on ignore_loglevel + ProcVersionSignature: Ubuntu 7.0.0-29.29~24.04.2-generic 7.0.12 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-7.0.0-29-generic N/A + linux-backports-modules-7.0.0-29-generic N/A + linux-firmware 20240318.git3b128b60-0ubuntu2.29 + RfKill: + + Tags: zena + Uname: Linux 7.0.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip docker i2c lpadmin ollama plugdev render sambashare sudo users video + _MarkForUpload: True + dmi.bios.date: 10/28/2025 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: FF + dmi.board.asset.tag: Default string + dmi.board.name: B550M DS3H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFF:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB550MB: + dmi.product.family: B550 MB + dmi.product.name: B550M DS3H + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2163945/+attachment/5993152/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2163945 Title: [Noble HWE 7.0][amdgpu][RX 6650 XT] Intermittent poweroff hang; 6.14.0-37 works, 7.0.0-28 and 7.0.0-29 fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163945/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
