[Bug 2159589] [NEW] Bluetooth turns back on automatically after being turned off in GNOME

Public bug reported: On Ubuntu 26.04 LTS, Bluetooth cannot remain turned off. When I turn Bluetooth off using either GNOME Quick Settings or Settings, it turns off briefly but then automatically turns itself back on. The Bluetooth controller confirms this behavior: immediately after turning it off, bluetoothctl show reports: Powered: no PowerState: off After a short time, without any user action, it changes back to: Powered: yes PowerState: on The Bluetooth adapter is a MediaTek device, USB ID 0e8d:e025, on a Lenovo ThinkPad P16s Gen 4 AMD. The kernel log also showed errors during the Bluetooth power-off sequence, including: Bluetooth: hci0: command 0x2039 tx timeout Bluetooth: hci0: failed to reset (-19) Bluetooth: hci0: Error when powering off device on rfkill (-110) Expected behavior: When Bluetooth is turned off in GNOME Quick Settings or Settings, it should remain off until the user turns it on again. Actual behavior: Bluetooth turns itself back on automatically after being turned off. This occurs consistently after a fresh installation of Ubuntu 26.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:09:07 2026 InstallationDate: Installed on 2026-07-05 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21RX001LGE ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2025 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: R2XET35W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21RX001LGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrR2XET35W(1.15):bd08/29/2025:br1.15:efr1.8:svnLENOVO:pn21RX001LGE:pvrThinkPadP16sGen4AMD:rvnLENOVO:rn21RX001LGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21RX_BU_Think_FM_ThinkPadP16sGen4AMD:pfaThinkPadP16sGen4AMD: dmi.product.family: ThinkPad P16s Gen 4 AMD dmi.product.name: 21RX001LGE dmi.product.sku: LENOVO_MT_21RX_BU_Think_FM_ThinkPad P16s Gen 4 AMD dmi.product.version: ThinkPad P16s Gen 4 AMD dmi.sys.vendor: LENOVO ** 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/2159589 Title: Bluetooth turns back on automatically after being turned off in GNOME Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 LTS, Bluetooth cannot remain turned off. When I turn Bluetooth off using either GNOME Quick Settings or Settings, it turns off briefly but then automatically turns itself back on. The Bluetooth controller confirms this behavior: immediately after turning it off, bluetoothctl show reports: Powered: no PowerState: off After a short time, without any user action, it changes back to: Powered: yes PowerState: on The Bluetooth adapter is a MediaTek device, USB ID 0e8d:e025, on a Lenovo ThinkPad P16s Gen 4 AMD. The kernel log also showed errors during the Bluetooth power-off sequence, including: Bluetooth: hci0: command 0x2039 tx timeout Bluetooth: hci0: failed to reset (-19) Bluetooth: hci0: Error when powering off device on rfkill (-110) Expected behavior: When Bluetooth is turned off in GNOME Quick Settings or Settings, it should remain off until the user turns it on again. Actual behavior: Bluetooth turns itself back on automatically after being turned off. This occurs consistently after a fresh installation of Ubuntu 26.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:09:07 2026 InstallationDate: Installed on 2026-07-05 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21RX001LGE ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2025 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: R2XET35W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21RX001LGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrR2XET35W(1.15):bd08/29/2025:br1.15:efr1.8:svnLENOVO:pn21RX001LGE:pvrThinkPadP16sGen4AMD:rvnLENOVO:rn21RX001LGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21RX_BU_Think_FM_ThinkPadP16sGen4AMD:pfaThinkPadP16sGen4AMD: dmi.product.family: ThinkPad P16s Gen 4 AMD dmi.product.name: 21RX001LGE dmi.product.sku: LENOVO_MT_21RX_BU_Think_FM_ThinkPad P16s Gen 4 AMD dmi.product.version: ThinkPad P16s Gen 4 AMD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159589/+subscriptions

[Bug 2158934] Re: Regression related to IOMMU grouping

** Description changed: Title: Regression: PCI commit 7a126c1b6cfa ("Enable ACS after configuring IOMMU for OF platforms") merges IOMMU groups on AMD x86, breaks VFIO passthrough — needs revert 817daf163312 backported Package: linux (Ubuntu) — noble, 6.8 kernel Is this a regression? Yes. Summary Upstream commit 7a126c1b6cfa ("PCI: Enable ACS after configuring IOMMU for OF platforms") was backported into Ubuntu's noble 6.8 kernel in 6.8.0-130.130 (as part of syncing to upstream stable v6.12.75; see changelog entry for LP: #2150809). This commit moves pci_enable_acs() into pci_dma_configure(), which runs on all platforms, not just OF/Device-Tree ones. On AMD x86 systems this changes ACS evaluation timing relative to IOMMU group assignment, causing devices that previously sat in isolated IOMMU groups to merge into one — breaking VFIO PCI passthrough. This is a known upstream regression, already fixed via revert commit 817daf163312 ("PCI: Revert 'Enable ACS after configuring IOMMU for OF platforms'"), bisected and confirmed on AMD-Vi hardware. See: https://forum.level1techs.com/t/iommu-group-regression-in-linux-kernel-6-12-75/247479 The revert is absent from Ubuntu's noble 6.8 changelogs from 6.8.0-130.130 through 6.8.0-134.134. Impact VFIO PCI passthrough fails with: vfio 0000:0b:00.0: group 2 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. Reproduction (my system) 6.8.0-124-generic (pre-regression): two AMD 1022:1453 GPP bridges, each with a downstream NVIDIA GP107 GPU, sit in separate IOMMU groups (16 and 17). 6.8.0-134-generic (regressed): the same two bridges and both GPUs merge into a single IOMMU group. Both kernels use identical cmdline (amd_iommu iommu=pt) and identical vfio-pci binding via /etc/modprobe.d/vfio.conf (subsystem-ID matched). System info CPU/chipset: AMD Family 17h (Zen), AMD 400-series chipset GPUs: 2x NVIDIA GP107 [GTX 1050 Ti] (10de:1c82) + audio functions (10de:0fb9) Working: 6.8.0-124-generic (6.8.0-124.124) Broken: 6.8.0-134-generic (6.8.0-134.134) Requested fix Backport 817daf163312 into the noble 6.8 stable branch. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-134-generic 6.8.0-134.134 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC1: macro 2576 F.... wireplumber - /dev/snd/controlC0: macro 2576 F.... wireplumber - /dev/snd/seq: macro 2574 F.... pipewire +  USER PID ACCESS COMMAND +  /dev/snd/controlC1: macro 2576 F.... wireplumber +  /dev/snd/controlC0: macro 2576 F.... wireplumber +  /dev/snd/seq: macro 2574 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jul 1 17:29:33 2026 InstallationDate: Installed on 2018-10-20 (2811 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-134-generic root=UUID=6eb14018-7030-43e9-bfbd-634e324040e2 ro quiet splash amd_iommu=on iommu=pt vt.handoff=7 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-134-generic N/A - linux-backports-modules-6.8.0-134-generic N/A - linux-firmware 20240318.git3b128b60-0ubuntu2.27 +  linux-restricted-modules-6.8.0-134-generic N/A +  linux-backports-modules-6.8.0-134-generic N/A +  linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI) 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.:bvr1001:bd09/27/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158934 Title: Regression related to IOMMU grouping Status in linux package in Ubuntu: Confirmed Bug description: Title: Regression: PCI commit 7a126c1b6cfa ("Enable ACS after configuring IOMMU for OF platforms") merges IOMMU groups on AMD x86, breaks VFIO passthrough — needs revert 817daf163312 backported Package: linux (Ubuntu) — noble, 6.8 kernel Is this a regression? Yes. Summary Upstream commit 7a126c1b6cfa ("PCI: Enable ACS after configuring IOMMU for OF platforms") was backported into Ubuntu's noble 6.8 kernel in 6.8.0-130.130 (as part of syncing to upstream stable v6.12.75; see changelog entry for LP: #2150809). This commit moves pci_enable_acs() into pci_dma_configure(), which runs on all platforms, not just OF/Device-Tree ones. On AMD x86 systems this changes ACS evaluation timing relative to IOMMU group assignment, causing devices that previously sat in isolated IOMMU groups to merge into one — breaking VFIO PCI passthrough. This is a known upstream regression, already fixed via revert commit 817daf163312 ("PCI: Revert 'Enable ACS after configuring IOMMU for OF platforms'"), bisected and confirmed on AMD-Vi hardware. See: https://forum.level1techs.com/t/iommu-group-regression-in-linux-kernel-6-12-75/247479 The revert is absent from Ubuntu's noble 6.8 changelogs from 6.8.0-130.130 through 6.8.0-134.134. Impact VFIO PCI passthrough fails with: vfio 0000:0b:00.0: group 2 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. Reproduction (my system) 6.8.0-124-generic (pre-regression): two AMD 1022:1453 GPP bridges, each with a downstream NVIDIA GP107 GPU, sit in separate IOMMU groups (16 and 17). 6.8.0-134-generic (regressed): the same two bridges and both GPUs merge into a single IOMMU group. Both kernels use identical cmdline (amd_iommu iommu=pt) and identical vfio-pci binding via /etc/modprobe.d/vfio.conf (subsystem-ID matched). System info CPU/chipset: AMD Family 17h (Zen), AMD 400-series chipset GPUs: 2x NVIDIA GP107 [GTX 1050 Ti] (10de:1c82) + audio functions (10de:0fb9) Working: 6.8.0-124-generic (6.8.0-124.124) Broken: 6.8.0-134-generic (6.8.0-134.134) Requested fix Backport 817daf163312 into the noble 6.8 stable branch. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-134-generic 6.8.0-134.134 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: macro 2576 F.... wireplumber  /dev/snd/controlC0: macro 2576 F.... wireplumber  /dev/snd/seq: macro 2574 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jul 1 17:29:33 2026 InstallationDate: Installed on 2018-10-20 (2811 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-134-generic root=UUID=6eb14018-7030-43e9-bfbd-634e324040e2 ro quiet splash amd_iommu=on iommu=pt vt.handoff=7 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-134-generic N/A  linux-backports-modules-6.8.0-134-generic N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI) 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.:bvr1001:bd09/27/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158934/+subscriptions

[Bug 2150258] Re: Froze on the desktop - second after boot...

Hey everyone, just wanted to confirm I'm running into this exact same issue on my rig. My system completely crashes to a black screen right after the boot logo. My logs show the same firmware mismatch line: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched Just in case it helps the developers, here are my specs: - Intel i9-11900K - Gigabyte Z590 Vision G - PowerColor Hellhound RX 9060 XT (16GB) - 32GB RAM Rolling back to my older kernel fixes the crash immediately and everything boots fine. Subscribing to the thread to keep an eye out for an update. Thanks! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150258 Title: Froze on the desktop - second after boot... Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: amdgpu SMU driver if version not matched (0x3d vs 0x40) causes KWin renderD128 race on boot — kernel 7.0.0-14, RX 7900 XTX 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: unknown CurrentDesktop: KDE Date: Fri Apr 24 20:24:33 2026 InstallationDate: Installed on 2025-12-01 (144 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: ASRock B650 PG Lightning ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=UUID=c181da8b-1a21-45b9-98a7-e4c5768b8838 ro rootflags=subvol=@ lockdown=integrity quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-22 (2 days ago) dmi.bios.date: 02/10/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.10 dmi.board.asset.tag: Default string dmi.board.name: B650 PG Lightning dmi.board.vendor: ASRock dmi.board.version: Default string 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.:bvr4.10:bd02/10/2026:br5.41:svnASRock:pnB650PGLightning:pvrDefaultstring:rvnASRock:rnB650PGLightning:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650 PG Lightning dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150258/+subscriptions

[Bug 2150258] Re: Froze on the desktop - second after boot...

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/2150258 Title: Froze on the desktop - second after boot... Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: amdgpu SMU driver if version not matched (0x3d vs 0x40) causes KWin renderD128 race on boot — kernel 7.0.0-14, RX 7900 XTX 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: unknown CurrentDesktop: KDE Date: Fri Apr 24 20:24:33 2026 InstallationDate: Installed on 2025-12-01 (144 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: ASRock B650 PG Lightning ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=UUID=c181da8b-1a21-45b9-98a7-e4c5768b8838 ro rootflags=subvol=@ lockdown=integrity quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-22 (2 days ago) dmi.bios.date: 02/10/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.10 dmi.board.asset.tag: Default string dmi.board.name: B650 PG Lightning dmi.board.vendor: ASRock dmi.board.version: Default string 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.:bvr4.10:bd02/10/2026:br5.41:svnASRock:pnB650PGLightning:pvrDefaultstring:rvnASRock:rnB650PGLightning:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650 PG Lightning dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150258/+subscriptions

[Bug 2159581] [NEW] Audio regression: No internal speaker sound over sof-soundwire (headphone jack works) on Intel Panther Lake layout

Public bug reported: SoundWire subsystem detects internal endpoints cleanly as "Speakers - sof-soundwire". Userspace audio mixers fluctuate dynamically showing active playback, but the physical internal speaker amplifiers remain completely silent. The onboard headphone jack (HDA) works flawlessly. System is running Ubuntu 26.04 with kernel 7.0.0-generic. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: fpm 4351 F.... wireplumber /dev/snd/seq: fpm 4331 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:06:12 2026 InstallationDate: Installed on 2026-07-04 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. Prestige 16 AI+ C3MTG ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=51afb7b2-3a6b-47e2-bef2-80c2eea73664 ro quiet splash xe.force_probe=b080 xe.enable_psr=0 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/25/2026 dmi.bios.release: 1.21 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E2622IMS.115 dmi.board.asset.tag: Default string dmi.board.name: MS-2622 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE2622IMS.115:bd03/25/2026:br1.21:svnMicro-StarInternationalCo.,Ltd.:pnPrestige16AI+C3MTG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-2622:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku2622.1:pfaPrestige: dmi.product.family: Prestige dmi.product.name: Prestige 16 AI+ C3MTG dmi.product.sku: 2622.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** 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/2159581 Title: Audio regression: No internal speaker sound over sof-soundwire (headphone jack works) on Intel Panther Lake layout Status in linux package in Ubuntu: New Bug description: SoundWire subsystem detects internal endpoints cleanly as "Speakers - sof-soundwire". Userspace audio mixers fluctuate dynamically showing active playback, but the physical internal speaker amplifiers remain completely silent. The onboard headphone jack (HDA) works flawlessly. System is running Ubuntu 26.04 with kernel 7.0.0-generic. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: fpm 4351 F.... wireplumber /dev/snd/seq: fpm 4331 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:06:12 2026 InstallationDate: Installed on 2026-07-04 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. Prestige 16 AI+ C3MTG ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=51afb7b2-3a6b-47e2-bef2-80c2eea73664 ro quiet splash xe.force_probe=b080 xe.enable_psr=0 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/25/2026 dmi.bios.release: 1.21 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E2622IMS.115 dmi.board.asset.tag: Default string dmi.board.name: MS-2622 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE2622IMS.115:bd03/25/2026:br1.21:svnMicro-StarInternationalCo.,Ltd.:pnPrestige16AI+C3MTG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-2622:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku2622.1:pfaPrestige: dmi.product.family: Prestige dmi.product.name: Prestige 16 AI+ C3MTG dmi.product.sku: 2622.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159581/+subscriptions

[Bug 2158286] Temporary Fix, if you don't need NFC or I2C

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

[Bug 2159568] Re: [Lenovo LOQ, Raptor Lake-S + RTX 5050] Internal panel stays black after suspend/resume (S3) — i915 eDP link fails to recover, unlike on cold boot

** Description changed: SUMMARY After suspending the laptop (via systemctl suspend or lid close) and resuming, the internal display never comes back on. The system is otherwise fully functional — confirmed via SSH that networking, the GNOME session, and the GPU are all alive and responsive. The backlight is physically on, but no image is displayed. Only a hard reboot recovers the display. HARDWARE - Laptop: Lenovo LOQ - CPU/iGPU: Intel Raptor Lake-S, UHD Graphics [8086:a78b] (rev 04) - dGPU: NVIDIA GeForce RTX 5050 Max-Q (GB207M) [10de:2dd8] (rev a1),   hybrid/Optimus graphics - Secure Boot: enabled SOFTWARE - Ubuntu 26.04 LTS (Resolute Raccoon) - Kernel: 7.0.0-27-generic (also reproduces on 7.0.0-22-generic) - Display server: Wayland, GNOME Shell (mutter 50.1), GDM - nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1 - PRIME mode: on-demand (default) STEPS TO REPRODUCE 1. Boot normally (panel works fine). 2. Suspend: `systemctl suspend`, or close the lid. 3. Wake the system (open lid / press a key). EXPECTED Panel lights up and shows the lock screen / desktop, same as after a normal cold boot. ACTUAL Screen stays completely black. Backlight is on (confirmed via /sys/class/backlight/*/actual_brightness). The rest of the system is fully alive: SSH'd in and confirmed networking, GNOME session, and GPU are all responsive; `nvidia-smi` works; gnome-shell process is running normally. ROOT CAUSE (as far as I could trace it) Every single boot — cold or resumed — logs this i915 message:   i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to   retrieve link info, disabling eDP On a cold boot, i915 evidently recovers from this before GDM starts, and the panel works normally. After an S3 resume, it does NOT recover: I confirmed via /sys/class/drm/ that the real internal panel connector never comes back under the i915 (or nvidia-drm) device — instead, `card0` remains bound to the `simple-framebuffer` driver (the generic EFI/firmware fallback framebuffer), which is what continues to "own" the panel indefinitely, with no active KMS scanout ever taking over. This matches the visible symptom exactly: the panel is electrically powered (backlight on) but nothing is being drawn to it because no real GPU driver has claimed the output. WHAT I'VE RULED OUT - NVIDIA/PRIME as the cause: reproduced identically with   `sudo prime-select intel` (NVIDIA driver fully unloaded,   `nvidia-smi` returning "couldn't communicate with the NVIDIA   driver"). Bug persists with NVIDIA completely out of the picture,   so this is purely an i915/Intel-side issue. - Panel power-saving states: tried `i915.enable_psr=0   i915.enable_dc=0` kernel parameters — no change in behavior. - A hung/crashed GPU: no Xid errors, no i915 GPU hang messages, no   kernel oops/BUG in dmesg around the resume window. The kernel and   compositor both report healthy state; the panel output is just   never actually reclaimed from simple-framebuffer. ADDITIONAL NOTES - Suspend mode in use is real S3 ("deep"), not s2idle   (/sys/power/mem_sleep shows "s2idle [deep]"). - Attempting to force a re-probe via `sudo chvt 3 && sudo chvt 1`   did not recover the panel. - Will attach dmesg output spanning a full suspend/resume cycle. Note: I found this to be the same issue in latest Fedora and CachyOS ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 - AudioDevicesInUse: -  USER PID ACCESS COMMAND -  /dev/snd/controlC2: zizo 4608 F.... wireplumber -  /dev/snd/controlC0: zizo 4608 F.... wireplumber -  /dev/snd/controlC1: zizo 4608 F.... wireplumber -  /dev/snd/seq: zizo 4587 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 17:07:28 2026 InstallationDate: Installed on 2026-06-20 (14 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83JE ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 lsm=capability,landlock,yama,apparmor,ima,evm resume=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 resume_offset=113035264 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2025 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R3CN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LOQ 15IRX10 dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR3CN44WW:bd01/15/2025:br1.44:efr1.44:svnLENOVO:pn83JE:pvrLOQ15IRX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLOQ15IRX10:skuLENOVO_MT_83JE_BU_idea_FM_LOQ15IRX10:pfaLOQ15IRX10: dmi.product.family: LOQ 15IRX10 dmi.product.name: 83JE dmi.product.sku: LENOVO_MT_83JE_BU_idea_FM_LOQ 15IRX10 dmi.product.version: LOQ 15IRX10 dmi.sys.vendor: LENOVO -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159568 Title: [Lenovo LOQ, Raptor Lake-S + RTX 5050] Internal panel stays black after suspend/resume (S3) — i915 eDP link fails to recover, unlike on cold boot Status in linux package in Ubuntu: New Bug description: SUMMARY After suspending the laptop (via systemctl suspend or lid close) and resuming, the internal display never comes back on. The system is otherwise fully functional — confirmed via SSH that networking, the GNOME session, and the GPU are all alive and responsive. The backlight is physically on, but no image is displayed. Only a hard reboot recovers the display. HARDWARE - Laptop: Lenovo LOQ - CPU/iGPU: Intel Raptor Lake-S, UHD Graphics [8086:a78b] (rev 04) - dGPU: NVIDIA GeForce RTX 5050 Max-Q (GB207M) [10de:2dd8] (rev a1),   hybrid/Optimus graphics - Secure Boot: enabled SOFTWARE - Ubuntu 26.04 LTS (Resolute Raccoon) - Kernel: 7.0.0-27-generic (also reproduces on 7.0.0-22-generic) - Display server: Wayland, GNOME Shell (mutter 50.1), GDM - nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1 - PRIME mode: on-demand (default) STEPS TO REPRODUCE 1. Boot normally (panel works fine). 2. Suspend: `systemctl suspend`, or close the lid. 3. Wake the system (open lid / press a key). EXPECTED Panel lights up and shows the lock screen / desktop, same as after a normal cold boot. ACTUAL Screen stays completely black. Backlight is on (confirmed via /sys/class/backlight/*/actual_brightness). The rest of the system is fully alive: SSH'd in and confirmed networking, GNOME session, and GPU are all responsive; `nvidia-smi` works; gnome-shell process is running normally. ROOT CAUSE (as far as I could trace it) Every single boot — cold or resumed — logs this i915 message:   i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to   retrieve link info, disabling eDP On a cold boot, i915 evidently recovers from this before GDM starts, and the panel works normally. After an S3 resume, it does NOT recover: I confirmed via /sys/class/drm/ that the real internal panel connector never comes back under the i915 (or nvidia-drm) device — instead, `card0` remains bound to the `simple-framebuffer` driver (the generic EFI/firmware fallback framebuffer), which is what continues to "own" the panel indefinitely, with no active KMS scanout ever taking over. This matches the visible symptom exactly: the panel is electrically powered (backlight on) but nothing is being drawn to it because no real GPU driver has claimed the output. WHAT I'VE RULED OUT - NVIDIA/PRIME as the cause: reproduced identically with   `sudo prime-select intel` (NVIDIA driver fully unloaded,   `nvidia-smi` returning "couldn't communicate with the NVIDIA   driver"). Bug persists with NVIDIA completely out of the picture,   so this is purely an i915/Intel-side issue. - Panel power-saving states: tried `i915.enable_psr=0   i915.enable_dc=0` kernel parameters — no change in behavior. - A hung/crashed GPU: no Xid errors, no i915 GPU hang messages, no   kernel oops/BUG in dmesg around the resume window. The kernel and   compositor both report healthy state; the panel output is just   never actually reclaimed from simple-framebuffer. ADDITIONAL NOTES - Suspend mode in use is real S3 ("deep"), not s2idle   (/sys/power/mem_sleep shows "s2idle [deep]"). - Attempting to force a re-probe via `sudo chvt 3 && sudo chvt 1`   did not recover the panel. - Will attach dmesg output spanning a full suspend/resume cycle. Note: I found this to be the same issue in latest Fedora and CachyOS ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 17:07:28 2026 InstallationDate: Installed on 2026-06-20 (14 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83JE ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 lsm=capability,landlock,yama,apparmor,ima,evm resume=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 resume_offset=113035264 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2025 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R3CN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LOQ 15IRX10 dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR3CN44WW:bd01/15/2025:br1.44:efr1.44:svnLENOVO:pn83JE:pvrLOQ15IRX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLOQ15IRX10:skuLENOVO_MT_83JE_BU_idea_FM_LOQ15IRX10:pfaLOQ15IRX10: dmi.product.family: LOQ 15IRX10 dmi.product.name: 83JE dmi.product.sku: LENOVO_MT_83JE_BU_idea_FM_LOQ 15IRX10 dmi.product.version: LOQ 15IRX10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159568/+subscriptions

[Bug 2158539] Re: Hard freezes on 7.0.0-22 and -27 with X670E/Ryzen; AMD xHCI controller not ready at resume (-19)

Follow-up — 2026-07-04: mitigation held for 5 days; an accidental revert reproduced the freeze After my last comment I disabled PCI runtime power management on the xHCI controllers by setting each xhci_hcd controller's power/control to on (i.e. runtime PM off — the controllers never runtime-suspend, so there is no suspend→resume cycle to fail). With that mitigation in effect the system ran stable for ~5 days, including its normal workload — the longest clean stretch since this bug was filed. I accidentally reverted the mitigation today. I was moving some files and so systemd lost its target to apply the fix on boot, and next boot the unit failed and the controllers fell back to power/control=auto (runtime PM re-enabled). Shortly after that revert, a USB hotplug (attaching an Android device for adb) — a controller resume/enumerate event on a CPU-side xHCI controller [1022:15b6]/[1022:15b7] — triggered the hard freeze again. The right global fix is not simply abandoning power management but this does localize the fault to xHCI runtime suspend -> resume on these specific AMD Raphael/Granite Ridge CPU-root-complex controllers, which fail to come back after "Controller not ready at resume -19" The right fix is probably a PCI/xHCI quirk for these device IDs (disabling runtime suspend or D3cold for the affected controllers) similar to other existing XHCI_* quirks for other vendors, not sure. Happy to test whatever would help narrow it if that's helpful. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158539 Title: Hard freezes on 7.0.0-22 and -27 with X670E/Ryzen; AMD xHCI controller not ready at resume (-19) Status in linux package in Ubuntu: New Bug description: After unattended-upgrade installed linux-image-7.0.0-27-generic on 2026-06-27, this system began hard-freezing with no clean shutdown and no panic in the journal. The prior kernel, 7.0.0-22-generic, is currently being tested as a workaround. Hardware: - ASUS ROG STRIX X670E-A GAMING WIFI, BIOS 3603 03/09/2026 - AMD Ryzen platform - Dual NVIDIA GeForce RTX 4090 - GNOME Wayland session Kernel/driver: - Bad kernel: 7.0.0-27-generic - Previously stable kernel: 7.0.0-22-generic - NVIDIA driver: 595.71.05, nvidia-driver-595-open - Kernel cmdline: pcie_aspm=off quiet splash Timeline: - 2026-06-27 06:14-06:15: unattended-upgrade installed 7.0.0-27 - 2026-06-27 08:06:35: first post-update boot froze; journal stopped abruptly - 2026-06-27 16:13:40: second boot froze; journal stopped abruptly - No systemd shutdown records for the failed boots Relevant warning on affected boot: Unpatched return thunk in use. This should not happen! WARNING: arch/x86/kernel/cpu/bugs.c:3736 at __warn_thunk Call trace includes: warn_thunk_thunk nvidia_init_module+0x29/0x740 [nvidia] Negative evidence: - No OOM, kernel panic, MCE, NVMe I/O error, SMART media error, thermal trip, or watchdog trace found. - NVMe SMART passed: media errors 0, error log entries 0. - Temperatures after reboot were not alarming. A later, separate GNOME Shell crash after reboot produced repeated: NVRM: VM: invalid mmap context ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 17:12:43 2026 InstallationDate: Installed on 2024-07-15 (713 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=5e50224a-2fb6-4607-84e3-9d99dee45bcb ro pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-24 (65 days ago) dmi.bios.date: 03/09/2026 dmi.bios.release: 36.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-A GAMING WIFI 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.:bvr3603:bd03/09/2026:br36.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158539/+subscriptions

[Bug 2159568] Re: [Lenovo LOQ, Raptor Lake-S + RTX 5050] Internal panel stays black after suspend/resume (S3) — i915 eDP link fails to recover, unlike on cold boot

** Description changed: SUMMARY After suspending the laptop (via systemctl suspend or lid close) and resuming, the internal display never comes back on. The system is otherwise fully functional — confirmed via SSH that networking, the GNOME session, and the GPU are all alive and responsive. The backlight is physically on, but no image is displayed. Only a hard reboot recovers the display. HARDWARE - Laptop: Lenovo LOQ - CPU/iGPU: Intel Raptor Lake-S, UHD Graphics [8086:a78b] (rev 04) - dGPU: NVIDIA GeForce RTX 5050 Max-Q (GB207M) [10de:2dd8] (rev a1), - hybrid/Optimus graphics +   hybrid/Optimus graphics - Secure Boot: enabled SOFTWARE - Ubuntu 26.04 LTS (Resolute Raccoon) - Kernel: 7.0.0-27-generic (also reproduces on 7.0.0-22-generic) - Display server: Wayland, GNOME Shell (mutter 50.1), GDM - nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1 - PRIME mode: on-demand (default) STEPS TO REPRODUCE 1. Boot normally (panel works fine). 2. Suspend: `systemctl suspend`, or close the lid. 3. Wake the system (open lid / press a key). EXPECTED Panel lights up and shows the lock screen / desktop, same as after a normal cold boot. ACTUAL Screen stays completely black. Backlight is on (confirmed via /sys/class/backlight/*/actual_brightness). The rest of the system is fully alive: SSH'd in and confirmed networking, GNOME session, and GPU are all responsive; `nvidia-smi` works; gnome-shell process is running normally. ROOT CAUSE (as far as I could trace it) Every single boot — cold or resumed — logs this i915 message: - i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to - retrieve link info, disabling eDP +   i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to +   retrieve link info, disabling eDP On a cold boot, i915 evidently recovers from this before GDM starts, and the panel works normally. After an S3 resume, it does NOT recover: I confirmed via /sys/class/drm/ that the real internal panel connector never comes back under the i915 (or nvidia-drm) device — instead, `card0` remains bound to the `simple-framebuffer` driver (the generic EFI/firmware fallback framebuffer), which is what continues to "own" the panel indefinitely, with no active KMS scanout ever taking over. This matches the visible symptom exactly: the panel is electrically powered (backlight on) but nothing is being drawn to it because no real GPU driver has claimed the output. WHAT I'VE RULED OUT - NVIDIA/PRIME as the cause: reproduced identically with - `sudo prime-select intel` (NVIDIA driver fully unloaded, - `nvidia-smi` returning "couldn't communicate with the NVIDIA - driver"). Bug persists with NVIDIA completely out of the picture, - so this is purely an i915/Intel-side issue. +   `sudo prime-select intel` (NVIDIA driver fully unloaded, +   `nvidia-smi` returning "couldn't communicate with the NVIDIA +   driver"). Bug persists with NVIDIA completely out of the picture, +   so this is purely an i915/Intel-side issue. - Panel power-saving states: tried `i915.enable_psr=0 - i915.enable_dc=0` kernel parameters — no change in behavior. +   i915.enable_dc=0` kernel parameters — no change in behavior. - A hung/crashed GPU: no Xid errors, no i915 GPU hang messages, no - kernel oops/BUG in dmesg around the resume window. The kernel and - compositor both report healthy state; the panel output is just - never actually reclaimed from simple-framebuffer. +   kernel oops/BUG in dmesg around the resume window. The kernel and +   compositor both report healthy state; the panel output is just +   never actually reclaimed from simple-framebuffer. ADDITIONAL NOTES - Suspend mode in use is real S3 ("deep"), not s2idle - (/sys/power/mem_sleep shows "s2idle [deep]"). +   (/sys/power/mem_sleep shows "s2idle [deep]"). - Attempting to force a re-probe via `sudo chvt 3 && sudo chvt 1` - did not recover the panel. +   did not recover the panel. - Will attach dmesg output spanning a full suspend/resume cycle. - Note: I found this to be the same issue in latest Fedora and CachyOS - - Note: I'm not very technical on this (LLMs helped with this) and I'll - really appreciate the support on this, thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC2: zizo 4608 F.... wireplumber - /dev/snd/controlC0: zizo 4608 F.... wireplumber - /dev/snd/controlC1: zizo 4608 F.... wireplumber - /dev/snd/seq: zizo 4587 F.... pipewire +  USER PID ACCESS COMMAND +  /dev/snd/controlC2: zizo 4608 F.... wireplumber +  /dev/snd/controlC0: zizo 4608 F.... wireplumber +  /dev/snd/controlC1: zizo 4608 F.... wireplumber +  /dev/snd/seq: zizo 4587 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 17:07:28 2026 InstallationDate: Installed on 2026-06-20 (14 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83JE ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> +  LANG=en_US.UTF-8 +  PATH=(custom, no user) +  SHELL=/bin/bash +  TERM=xterm-256color +  XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 lsm=capability,landlock,yama,apparmor,ima,evm resume=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 resume_offset=113035264 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2025 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R3CN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LOQ 15IRX10 dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR3CN44WW:bd01/15/2025:br1.44:efr1.44:svnLENOVO:pn83JE:pvrLOQ15IRX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLOQ15IRX10:skuLENOVO_MT_83JE_BU_idea_FM_LOQ15IRX10:pfaLOQ15IRX10: dmi.product.family: LOQ 15IRX10 dmi.product.name: 83JE dmi.product.sku: LENOVO_MT_83JE_BU_idea_FM_LOQ 15IRX10 dmi.product.version: LOQ 15IRX10 dmi.sys.vendor: LENOVO -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159568 Title: [Lenovo LOQ, Raptor Lake-S + RTX 5050] Internal panel stays black after suspend/resume (S3) — i915 eDP link fails to recover, unlike on cold boot Status in linux package in Ubuntu: New Bug description: SUMMARY After suspending the laptop (via systemctl suspend or lid close) and resuming, the internal display never comes back on. The system is otherwise fully functional — confirmed via SSH that networking, the GNOME session, and the GPU are all alive and responsive. The backlight is physically on, but no image is displayed. Only a hard reboot recovers the display. HARDWARE - Laptop: Lenovo LOQ - CPU/iGPU: Intel Raptor Lake-S, UHD Graphics [8086:a78b] (rev 04) - dGPU: NVIDIA GeForce RTX 5050 Max-Q (GB207M) [10de:2dd8] (rev a1),   hybrid/Optimus graphics - Secure Boot: enabled SOFTWARE - Ubuntu 26.04 LTS (Resolute Raccoon) - Kernel: 7.0.0-27-generic (also reproduces on 7.0.0-22-generic) - Display server: Wayland, GNOME Shell (mutter 50.1), GDM - nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1 - PRIME mode: on-demand (default) STEPS TO REPRODUCE 1. Boot normally (panel works fine). 2. Suspend: `systemctl suspend`, or close the lid. 3. Wake the system (open lid / press a key). EXPECTED Panel lights up and shows the lock screen / desktop, same as after a normal cold boot. ACTUAL Screen stays completely black. Backlight is on (confirmed via /sys/class/backlight/*/actual_brightness). The rest of the system is fully alive: SSH'd in and confirmed networking, GNOME session, and GPU are all responsive; `nvidia-smi` works; gnome-shell process is running normally. ROOT CAUSE (as far as I could trace it) Every single boot — cold or resumed — logs this i915 message:   i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to   retrieve link info, disabling eDP On a cold boot, i915 evidently recovers from this before GDM starts, and the panel works normally. After an S3 resume, it does NOT recover: I confirmed via /sys/class/drm/ that the real internal panel connector never comes back under the i915 (or nvidia-drm) device — instead, `card0` remains bound to the `simple-framebuffer` driver (the generic EFI/firmware fallback framebuffer), which is what continues to "own" the panel indefinitely, with no active KMS scanout ever taking over. This matches the visible symptom exactly: the panel is electrically powered (backlight on) but nothing is being drawn to it because no real GPU driver has claimed the output. WHAT I'VE RULED OUT - NVIDIA/PRIME as the cause: reproduced identically with   `sudo prime-select intel` (NVIDIA driver fully unloaded,   `nvidia-smi` returning "couldn't communicate with the NVIDIA   driver"). Bug persists with NVIDIA completely out of the picture,   so this is purely an i915/Intel-side issue. - Panel power-saving states: tried `i915.enable_psr=0   i915.enable_dc=0` kernel parameters — no change in behavior. - A hung/crashed GPU: no Xid errors, no i915 GPU hang messages, no   kernel oops/BUG in dmesg around the resume window. The kernel and   compositor both report healthy state; the panel output is just   never actually reclaimed from simple-framebuffer. ADDITIONAL NOTES - Suspend mode in use is real S3 ("deep"), not s2idle   (/sys/power/mem_sleep shows "s2idle [deep]"). - Attempting to force a re-probe via `sudo chvt 3 && sudo chvt 1`   did not recover the panel. - Will attach dmesg output spanning a full suspend/resume cycle. Note: I found this to be the same issue in latest Fedora and CachyOS ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: zizo 4608 F.... wireplumber  /dev/snd/controlC0: zizo 4608 F.... wireplumber  /dev/snd/controlC1: zizo 4608 F.... wireplumber  /dev/snd/seq: zizo 4587 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 17:07:28 2026 InstallationDate: Installed on 2026-06-20 (14 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83JE ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 lsm=capability,landlock,yama,apparmor,ima,evm resume=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 resume_offset=113035264 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2025 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R3CN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LOQ 15IRX10 dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR3CN44WW:bd01/15/2025:br1.44:efr1.44:svnLENOVO:pn83JE:pvrLOQ15IRX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLOQ15IRX10:skuLENOVO_MT_83JE_BU_idea_FM_LOQ15IRX10:pfaLOQ15IRX10: dmi.product.family: LOQ 15IRX10 dmi.product.name: 83JE dmi.product.sku: LENOVO_MT_83JE_BU_idea_FM_LOQ 15IRX10 dmi.product.version: LOQ 15IRX10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159568/+subscriptions

[Bug 2159568] [NEW] [Lenovo LOQ, Raptor Lake-S + RTX 5050] Internal panel stays black after suspend/resume (S3) — i915 eDP link fails to recover, unlike on cold boot

Public bug reported: SUMMARY After suspending the laptop (via systemctl suspend or lid close) and resuming, the internal display never comes back on. The system is otherwise fully functional — confirmed via SSH that networking, the GNOME session, and the GPU are all alive and responsive. The backlight is physically on, but no image is displayed. Only a hard reboot recovers the display. HARDWARE - Laptop: Lenovo LOQ - CPU/iGPU: Intel Raptor Lake-S, UHD Graphics [8086:a78b] (rev 04) - dGPU: NVIDIA GeForce RTX 5050 Max-Q (GB207M) [10de:2dd8] (rev a1), hybrid/Optimus graphics - Secure Boot: enabled SOFTWARE - Ubuntu 26.04 LTS (Resolute Raccoon) - Kernel: 7.0.0-27-generic (also reproduces on 7.0.0-22-generic) - Display server: Wayland, GNOME Shell (mutter 50.1), GDM - nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1 - PRIME mode: on-demand (default) STEPS TO REPRODUCE 1. Boot normally (panel works fine). 2. Suspend: `systemctl suspend`, or close the lid. 3. Wake the system (open lid / press a key). EXPECTED Panel lights up and shows the lock screen / desktop, same as after a normal cold boot. ACTUAL Screen stays completely black. Backlight is on (confirmed via /sys/class/backlight/*/actual_brightness). The rest of the system is fully alive: SSH'd in and confirmed networking, GNOME session, and GPU are all responsive; `nvidia-smi` works; gnome-shell process is running normally. ROOT CAUSE (as far as I could trace it) Every single boot — cold or resumed — logs this i915 message: i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to retrieve link info, disabling eDP On a cold boot, i915 evidently recovers from this before GDM starts, and the panel works normally. After an S3 resume, it does NOT recover: I confirmed via /sys/class/drm/ that the real internal panel connector never comes back under the i915 (or nvidia-drm) device — instead, `card0` remains bound to the `simple-framebuffer` driver (the generic EFI/firmware fallback framebuffer), which is what continues to "own" the panel indefinitely, with no active KMS scanout ever taking over. This matches the visible symptom exactly: the panel is electrically powered (backlight on) but nothing is being drawn to it because no real GPU driver has claimed the output. WHAT I'VE RULED OUT - NVIDIA/PRIME as the cause: reproduced identically with `sudo prime-select intel` (NVIDIA driver fully unloaded, `nvidia-smi` returning "couldn't communicate with the NVIDIA driver"). Bug persists with NVIDIA completely out of the picture, so this is purely an i915/Intel-side issue. - Panel power-saving states: tried `i915.enable_psr=0 i915.enable_dc=0` kernel parameters — no change in behavior. - A hung/crashed GPU: no Xid errors, no i915 GPU hang messages, no kernel oops/BUG in dmesg around the resume window. The kernel and compositor both report healthy state; the panel output is just never actually reclaimed from simple-framebuffer. ADDITIONAL NOTES - Suspend mode in use is real S3 ("deep"), not s2idle (/sys/power/mem_sleep shows "s2idle [deep]"). - Attempting to force a re-probe via `sudo chvt 3 && sudo chvt 1` did not recover the panel. - Will attach dmesg output spanning a full suspend/resume cycle. Note: I found this to be the same issue in latest Fedora and CachyOS Note: I'm not very technical on this (LLMs helped with this) and I'll really appreciate the support on this, thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: zizo 4608 F.... wireplumber /dev/snd/controlC0: zizo 4608 F.... wireplumber /dev/snd/controlC1: zizo 4608 F.... wireplumber /dev/snd/seq: zizo 4587 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 17:07:28 2026 InstallationDate: Installed on 2026-06-20 (14 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83JE ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 lsm=capability,landlock,yama,apparmor,ima,evm resume=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 resume_offset=113035264 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2025 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R3CN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LOQ 15IRX10 dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR3CN44WW:bd01/15/2025:br1.44:efr1.44:svnLENOVO:pn83JE:pvrLOQ15IRX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLOQ15IRX10:skuLENOVO_MT_83JE_BU_idea_FM_LOQ15IRX10:pfaLOQ15IRX10: dmi.product.family: LOQ 15IRX10 dmi.product.name: 83JE dmi.product.sku: LENOVO_MT_83JE_BU_idea_FM_LOQ 15IRX10 dmi.product.version: LOQ 15IRX10 dmi.sys.vendor: LENOVO ** 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/2159568 Title: [Lenovo LOQ, Raptor Lake-S + RTX 5050] Internal panel stays black after suspend/resume (S3) — i915 eDP link fails to recover, unlike on cold boot Status in linux package in Ubuntu: New Bug description: SUMMARY After suspending the laptop (via systemctl suspend or lid close) and resuming, the internal display never comes back on. The system is otherwise fully functional — confirmed via SSH that networking, the GNOME session, and the GPU are all alive and responsive. The backlight is physically on, but no image is displayed. Only a hard reboot recovers the display. HARDWARE - Laptop: Lenovo LOQ - CPU/iGPU: Intel Raptor Lake-S, UHD Graphics [8086:a78b] (rev 04) - dGPU: NVIDIA GeForce RTX 5050 Max-Q (GB207M) [10de:2dd8] (rev a1), hybrid/Optimus graphics - Secure Boot: enabled SOFTWARE - Ubuntu 26.04 LTS (Resolute Raccoon) - Kernel: 7.0.0-27-generic (also reproduces on 7.0.0-22-generic) - Display server: Wayland, GNOME Shell (mutter 50.1), GDM - nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1 - PRIME mode: on-demand (default) STEPS TO REPRODUCE 1. Boot normally (panel works fine). 2. Suspend: `systemctl suspend`, or close the lid. 3. Wake the system (open lid / press a key). EXPECTED Panel lights up and shows the lock screen / desktop, same as after a normal cold boot. ACTUAL Screen stays completely black. Backlight is on (confirmed via /sys/class/backlight/*/actual_brightness). The rest of the system is fully alive: SSH'd in and confirmed networking, GNOME session, and GPU are all responsive; `nvidia-smi` works; gnome-shell process is running normally. ROOT CAUSE (as far as I could trace it) Every single boot — cold or resumed — logs this i915 message: i915 0000:00:02.0: [drm] [ENCODER:506:DDI A/PHY A] failed to retrieve link info, disabling eDP On a cold boot, i915 evidently recovers from this before GDM starts, and the panel works normally. After an S3 resume, it does NOT recover: I confirmed via /sys/class/drm/ that the real internal panel connector never comes back under the i915 (or nvidia-drm) device — instead, `card0` remains bound to the `simple-framebuffer` driver (the generic EFI/firmware fallback framebuffer), which is what continues to "own" the panel indefinitely, with no active KMS scanout ever taking over. This matches the visible symptom exactly: the panel is electrically powered (backlight on) but nothing is being drawn to it because no real GPU driver has claimed the output. WHAT I'VE RULED OUT - NVIDIA/PRIME as the cause: reproduced identically with `sudo prime-select intel` (NVIDIA driver fully unloaded, `nvidia-smi` returning "couldn't communicate with the NVIDIA driver"). Bug persists with NVIDIA completely out of the picture, so this is purely an i915/Intel-side issue. - Panel power-saving states: tried `i915.enable_psr=0 i915.enable_dc=0` kernel parameters — no change in behavior. - A hung/crashed GPU: no Xid errors, no i915 GPU hang messages, no kernel oops/BUG in dmesg around the resume window. The kernel and compositor both report healthy state; the panel output is just never actually reclaimed from simple-framebuffer. ADDITIONAL NOTES - Suspend mode in use is real S3 ("deep"), not s2idle (/sys/power/mem_sleep shows "s2idle [deep]"). - Attempting to force a re-probe via `sudo chvt 3 && sudo chvt 1` did not recover the panel. - Will attach dmesg output spanning a full suspend/resume cycle. Note: I found this to be the same issue in latest Fedora and CachyOS Note: I'm not very technical on this (LLMs helped with this) and I'll really appreciate the support on this, thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: zizo 4608 F.... wireplumber /dev/snd/controlC0: zizo 4608 F.... wireplumber /dev/snd/controlC1: zizo 4608 F.... wireplumber /dev/snd/seq: zizo 4587 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 17:07:28 2026 InstallationDate: Installed on 2026-06-20 (14 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83JE ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 lsm=capability,landlock,yama,apparmor,ima,evm resume=UUID=e500acb9-7646-4972-acfa-579d662fd7e4 resume_offset=113035264 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2025 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R3CN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LOQ 15IRX10 dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR3CN44WW:bd01/15/2025:br1.44:efr1.44:svnLENOVO:pn83JE:pvrLOQ15IRX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLOQ15IRX10:skuLENOVO_MT_83JE_BU_idea_FM_LOQ15IRX10:pfaLOQ15IRX10: dmi.product.family: LOQ 15IRX10 dmi.product.name: 83JE dmi.product.sku: LENOVO_MT_83JE_BU_idea_FM_LOQ 15IRX10 dmi.product.version: LOQ 15IRX10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159568/+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

Yes, sound works fine on Pop OS with 6.18.7-760061807 -- 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 2159008] Re: System freeze on ASUS Zenbook UX3404VA (i9 13900H) login screen in 26.04 LTS

** 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/2159008 Title: System freeze on ASUS Zenbook UX3404VA (i9 13900H) login screen in 26.04 LTS Status in linux package in Ubuntu: New Bug description: Dear Ubuntu Developers / Kernel Team, I am writing to report a critical issue I am encountering with Ubuntu 26.04 LTS on my ASUS Zenbook UX3404VA (Intel Core i9 13900H, Iris Xe Graphics). The Issue: Upon installing Ubuntu 26.04 LTS, the system freezes consistently immediately after the user authentication stage. The screen stops responding entirely, although the keyboard remains responsive (no kernel panic). This behavior does not occur in Ubuntu 25.10, where all hardware components function correctly. System Details: Laptop: ASUS Zenbook UX3404VA Processor: Intel Core i9-13900H (Raptor Lake) Graphics: Intel Iris Xe Graphics OS Version: Ubuntu 26.04 LTS (Freeze observed) / Ubuntu 25.10 (Stable) Environment: Default GNOME/Wayland Troubleshooting Attempted: Verified that Ubuntu 25.10 is completely stable on the same hardware. The freeze specifically occurs at the transition from the login manager to the desktop session, suggesting a potential regression in the xe vs i915 driver handling or a Wayland/Mutter incompatibility in the 26.04 kernel. The issue appears to be related to GPU hardware acceleration during session initialization. I would appreciate it if you could investigate this regression, as it affects the stability of the latest LTS release on this specific laptop model. Please let me know if you need any specific logs (e.g., journalctl -b -1) or debug information to help pinpoint the cause. Thank you for your hard work and support. Best regards, Ali Beheshti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159008/+subscriptions

[Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM

This issue is not being referenced in out hint database. Closing it. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. ------------------------------ This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test'  BUILD_HEAD=4671e4ba  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF  enabling apic  paging enabled  cr0 = 80010011  cr3 = 477000  cr4 = 20  Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron:  TERM=xterm-256color  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions