Hi Ross, thanks for the reply.

I can't go back to 7.0.0-31: it was removed by the apt cleanup on
2026-10-02 when -38 was installed. As written in comment #2, the loop
started on 2026-09-30, right after the release upgrade from 24.04 to 26.04,
while still running 7.0.0-34. That same kernel had run loop-free on 24.04
for about a day before the upgrade.

Your firmware idea fits that timeline: the release upgrade also upgraded
linux-firmware from 20240318.git3b128b60.0ubuntu3.1 to
20260319.git217ca6e4.1ubuntu (see /var/log/dist-upgrade/history.log). I can
try to test with the older linux-firmware if you tell me how to get it, or
run any other test you suggest.

Ross Porter <[email protected]> ezt írta (időpont: 2026. okt. 5.,
H, 0:00):

> Hi,
>
> Thanks for filing a bug report. Does the problem go away if you go back
> to the 7.0.0-31 kernel? If it still occurs on -31 it might instead be
> caused by one of the linux-firmware packages being upgraded.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2169388
>
> Title:
>   ThinkBook 16 G8 IAL (21SK): s2idle suspend/resume loop after lid
>   close, wake IRQ 9 (ACPI GPE 0x6D), ~20%/h battery drain
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Hardware: Lenovo ThinkBook 16 G8 IAL (21SK), Intel Meteor Lake, BIOS
> RKCN20WW
>   OS: Ubuntu 26.04.1 LTS
>   Kernels: 7.0.0-31 (no problem seen), 7.0.0-34 (problem), 7.0.0-38
> (problem)
>
>   Problem:
>   After closing the lid, the laptop enters suspend (PM: suspend entry
> (s2idle)), wakes up after ~2 s (PM: suspend exit), is suspended again by
> logind ~30 s later, and this repeats until the lid is opened. This gives
> ~117 suspend entries per hour and a battery drain of ~20%/h (65% -> 20% in
> 2 hours).
>
>   The problem is intermittent. Of 4 lid closes between 2026-09-30 and
>   2026-10-01 on kernel 7.0.0-34, two looped (2026-09-30 ~21:05-22:10 and
>   2026-10-01 19:23-00:18), two suspended normally. The loop also
>   occurred on 7.0.0-38 (evening of 2026-10-02).
>
>   History:
>   - 7.0.0-31: ~3 weeks of daily use, never more than 3 suspend entries per
> hour.
>   - 7.0.0-34 installed 2026-09-27, first loop seen 2026-09-30.
>   - 7.0.0-38 installed 2026-10-02, loop continued.
>   - The loops happened on battery, not on AC.
>
>   Findings:
>   - /sys/power/pm_wakeup_irq = 9 (ACPI SCI) after the premature wake-up.
>   - During ~3-4 min of lid-closed s2idle,
> /sys/firmware/acpi/interrupts/gpe6D rose by ~9200 events; gpe6E (the EC
> GPE, "ACPI: EC: GPE=0x6e") rose by ~270.
>   - Workaround: kernel parameter acpi_mask_gpe=0x6D. With it, a lid-closed
> suspend lasted 5h15m with a single suspend entry and 6% battery drain.
> Disabling gpe6D via sysfs did not persist across suspend; only the kernel
> parameter held.
>
>   Usage pattern: the laptop is suspended every night with the lid
>   closed; during the day the lid is closed at every study break (every
>   1-1.5 h).
>
>   Unrelated, probably noise: an fwupd UEFI dbx update (20260402 ->
>   20260707) failed with "expected 20260707 and got (null)".
>
>   Please tell me what additional information I should collect.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 26.04
>   Package: linux-image-7.0.0-38-generic 7.0.0-38.38
>   ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14
>   Uname: Linux 7.0.0-38-generic x86_64
>   ApportVersion: 2.34.1-0ubuntu0.1
>   Architecture: amd64
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  pilu       4464 F.... pipewire
>                         pilu       4470 F.... wireplumber
>    /dev/snd/seq:        pilu       4464 F.... pipewire
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Oct  3 10:06:26 2026
>   InstallationDate: Installed on 2025-12-16 (290 days ago)
>   InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64
> (20250805.1)
>   MachineType: LENOVO 21SK
>   ProcEnviron:
>    LANG=en_US.UTF-8
>    PATH=(custom, no user)
>    SHELL=/bin/bash
>    TERM=xterm-256color
>    XDG_RUNTIME_DIR=<set>
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic
> root=UUID=aae6094b-c046-479c-97da-6c5624645338 ro quiet splash
> acpi_mask_gpe=0x6D
> 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: Upgraded to resolute on 2026-09-30 (3 days ago)
>   dmi.bios.date: 06/06/2025
>   dmi.bios.release: 1.20
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: RKCN20WW
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: LNVNB161216
>   dmi.board.vendor: LENOVO
>   dmi.board.version: NO DPK
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: ThinkBook 16 G8 IAL
>   dmi.ec.firmware.release: 1.14
>   dmi.modalias:
> dmi:bvnLENOVO:bvrRKCN20WW:bd06/06/2025:br1.20:efr1.14:svnLENOVO:pn21SK:pvrThinkBook16G8IAL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrThinkBook16G8IAL:skuLENOVO_MT_21SK_BU_idea_FM_ThinkBook16G8IAL:pfaThinkBook16G8IAL:
>   dmi.product.family: ThinkBook 16 G8 IAL
>   dmi.product.name: 21SK
>   dmi.product.sku: LENOVO_MT_21SK_BU_idea_FM_ThinkBook 16 G8 IAL
>   dmi.product.version: ThinkBook 16 G8 IAL
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169388/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169388

Title:
  ThinkBook 16 G8 IAL (21SK): s2idle suspend/resume loop after lid
  close, wake IRQ 9 (ACPI GPE 0x6D), ~20%/h battery drain

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to