Laptop wakes up from suspend itself after about one minute

[as]

Laptop wakes up from suspend itself after about one minute.
It didn't take place never before.
I didn't change anything in the system, computer, network, peripherals etc. I just updated system today.

After suspending computer, everything seems to be fine (suspend light in laptop lid tells me this). But after about one minute computer wakes up. And it should happen only after pushing power button on docking station.

This is yet another bug I'm reporting today, related to suspend. I think the upgrade is the reason of it.

OS: Ubuntu 22.04.1 LTS x86_64
Host: 20T6000TPB ThinkPad E14 Gen 2
Kernel: 5.15.0-48-generic
Uptime: 30 mins
Packages: 4521 (dpkg), 58 (brew), 13 (flatpak), 83 (snap)
Shell: zsh 5.8.1
Resolution: 4384x2466
DE: GNOME 42.4
WM: Mutter
WM Theme: Adwaita
Theme: Yaru-dark [GTK2/3]
Icons: Yaru [GTK2/3]
Terminal: mate-terminal
Terminal Font: Monospace 10
CPU: AMD Ryzen 5 4500U with Radeon Graphics (6) @ 2.375GHz
GPU: AMD ATI 05:00.0 Renoir
Memory: 6074MiB / 23255MiB

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-48-generic 5.15.0-48.54
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: as 7081 F.... pulseaudio
 /dev/snd/controlC1: as 7081 F.... pulseaudio
 /dev/snd/controlC0: as 7081 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 26 17:41:16 2022
InstallationDate: Installed on 2020-12-06 (659 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: LENOVO 20T6000TPB
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-48-generic N/A
 linux-backports-modules-5.15.0-48-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2021
dmi.bios.release: 1.16
dmi.bios.vendor: LENOVO
dmi.bios.version: R1AET40W (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20T6000TPB
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias: dmi:bvnLENOVO:bvrR1AET40W(1.16):bd09/06/2021:br1.16:efr1.16:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20T6000TPB
dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

What's the value of `/sys/power/wakeup_irq`?

[as (ip413as3)]

I don't have `/sys/power/wakeup_irq`.

sudo ls /sys/power/wakeup_irq
ls: cannot access '/sys/power/wakeup_irq': No such file or directory

But, I do have /sys/power/pm_wakeup_irq, and I can't read value of it.

sudo ls -la /sys/power/pm_wakeup_irq
-r--r--r-- 1 root root 4096 Sep 27 16:43 /sys/power/pm_wakeup_irq

sudo cat /sys/power/pm_wakeup_irq
cat: /sys/power/pm_wakeup_irq: No data available

[as (ip413as3)]

Other files from /sys/power/

for file in /sys/power/*; do echo $file; cat $file; done
/sys/power/disk
[platform] shutdown reboot suspend test_resume
/sys/power/image_size
9723527168
/sys/power/mem_sleep
s2idle [deep]
/sys/power/pm_async
1
/sys/power/pm_debug_messages
0
/sys/power/pm_freeze_timeout
20000
/sys/power/pm_print_times
0
/sys/power/pm_test
[none] core processors platform devices freezer
/sys/power/pm_trace
0
/sys/power/pm_trace_dev_match
/sys/power/pm_wakeup_irq
cat: /sys/power/pm_wakeup_irq: No data available
/sys/power/reserved_size
1048576
/sys/power/resume
0:0
/sys/power/resume_offset
0
/sys/power/state
freeze mem disk
/sys/power/suspend_stats
cat: /sys/power/suspend_stats: Is a directory
/sys/power/sync_on_suspend
1
/sys/power/wake_lock

/sys/power/wake_unlock

/sys/power/wakeup_count
502

[as (ip413as3)]

Strange thing, suspend seems to work now, after one full day, and a couple of restarts.