Hi HO, would it be possible for you or someone else with affected
hardware to test this kernel? Here's the link:
https://people.canonical.com/~cremfuelled/LP2118955/.

If this works I can send a patch that would fix the issue for Ubuntu
kernels, which would allow you to uninstall the unsupported mainline
kernel if you so desire.

You can install the test kernel with:
$ sudo dpkg -i linux-image-unsigned-6.14.0-* linux-modules-6.14.0-*

And then, after a reboot and testing, you can remove it from your system with:
$ sudo dpkg -P linux-image-unsigned-6.14.0-* linux-modules-6.14.0-*

Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.14 in Ubuntu.
https://bugs.launchpad.net/bugs/2118955

Title:
  [s2idle] Suspend fails on Acer Nitro ANV15-41 when keyboard controller
  is active

Status in linux-hwe-6.14 package in Ubuntu:
  Triaged
Status in linux-hwe-6.14 source package in Noble:
  Triaged
Status in linux-hwe-6.14 source package in Plucky:
  Triaged

Bug description:
  Confirmed through multiple different experiments, the laptop fails to
  suspend to s2idle due to an issue directly tied to the activity state
  of the keyboard's low-level hardware controller. The failure is 100%
  reproducible.

  If a suspend is initiated within approximately **20-30 seconds of the
  last keyboard key press**, the suspend fails. The system attempts to
  enter suspend for a few seconds and then immediately wakes up. The key
  indicator of failure in the kernel log is the message `kernel: amd_pmc
  ... Last suspend didn't reach deepest state`, indicating the hardware
  failed to enter its sleep state.

  This behavior strongly suggests that the keyboard's controller (likely
  the Embedded Controller or EC) has an internal activity timer. If the
  OS requests a system-wide suspend while this timer is still active,
  the controller's firmware fails to handle the suspend signal
  correctly, causing the entire process to abort.

  The keyboard backlight serves as a useful visual indicator of this 
controller's active state:
  - If the backlight is configured in BIOS settings to "Never" time out, the 
controller remains permanently active, and **suspend fails 100% of the time.**
  - If the backlight is allowed to time out, suspend will succeed reliably 
**only after** the timeout period has passed.

  Critically, even disabling the backlight entirely using the shortcut
  ALT+F11 does not fix the issue. I believe this is because the bug lies
  with the EC's core activity timer which happens to have the same
  timeout as the keyboard's backlight.

  EDIT: I forgot to mention, this issue occurs despite me upgrading to
  the latest bios version provided by the manufacturer (v1.18).

  ### Steps to Reproduce
  1. Press any key on the keyboard to trigger the controller's active state.
  2. Immediately (within ~10 seconds) run sudo systemctl suspend.
  3. **Observe Failure:** The system will wake up immediately.
  4. After waking, wait for 30 seconds without pressing the keyboard, allowing 
the controller to return to an idle state.
  5. Run sudo systemctl suspend again.
  6. **Observe Success:** The system will now suspend correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.14.0-24-generic 6.14.0-24.24~24.04.3
  ProcVersionSignature: Ubuntu 6.14.0-24.24~24.04.3-generic 6.14.6
  Uname: Linux 6.14.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC2:  edllt      2496 F.... wireplumber
   /dev/snd/controlC0:  edllt      2496 F.... wireplumber
   /dev/snd/controlC1:  edllt      2496 F.... wireplumber
   /dev/snd/seq:        edllt      2492 F.... pipewire
  CRDA: N/A
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 29 03:29:57 2025
  InstallationDate: Installed on 2025-07-20 (8 days ago)
  InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 
(20250215)
  MachineType: Acer Nitro ANV15-41
  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=/boot/vmlinuz-6.14.0-24-generic 
root=UUID=006e355c-90b4-4948-858d-60a40874317a ro nvidia-drm.modeset=1 
nvidia.NVreg_PreserveVideoMemoryAllocations=1
  RelatedPackageVersions:
   linux-restricted-modules-6.14.0-24-generic N/A
   linux-backports-modules-6.14.0-24-generic  N/A
   linux-firmware                             20240318.git3b128b60-0ubuntu2.14
  SourcePackage: linux-hwe-6.14
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2025
  dmi.bios.release: 1.18
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Sportage_RBH
  dmi.board.vendor: RB
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrV1.18:bd07/02/2025:br1.18:efr1.9:svnAcer:pnNitroANV15-41:pvrV1.18:rvnRB:rnSportage_RBH:rvrV1.18:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
  dmi.product.family: Acer Nitro V 15
  dmi.product.name: Nitro ANV15-41
  dmi.product.sku: 0000000000000000
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.14/+bug/2118955/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to