https://bugzilla.kernel.org/show_bug.cgi?id=218265
Bug ID: 218265
Summary: Immediate wake after S2 suspend, intermittently, with
all /proc/acpi/wakeup sources disabled
Product: ACPI
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Power-Sleep-Wake
Assignee: acpi_power-sleep-w...@kernel-bugs.osdl.org
Reporter: hau...@keteu.org
Regression: No
Created attachment 305599
--> https://bugzilla.kernel.org/attachment.cgi?id=305599&action=edit
dmesg from suspend which immediately wakes
On a new Lenovo Thinkpad P16s with kernel 6.6.6, suspend is immediately
followed by wake, about half of the time. (If sleep lasts for three seconds,
it will last indefinitely.) There is no apparent difference between lid close,
`zzz`, and `loginctl suspend`. I see nothing suspicious in dmesg, and I see no
difference in the messages between the fail case (immediate wake-up) and the
success case (wake-up later).
All ACPI wake sources are already set to "disabled" in /proc/acpi/wakeup. All
potential wake options, like wake on LAN, are disabled in the BIOS.
Observability is poor because I know of no way to log or trace the actual wake
event. E.g. even with "everything" disabled, the laptop's touchpad or keyboard
still wake the system, but I only know that by human observation, not proper
logging. Is there some way to make the kernel log the wake source?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
