https://bugzilla.kernel.org/show_bug.cgi?id=216516 --- Comment #23 from Mario Limonciello (AMD) (mario.limonciello@xxxxxxx) --- All of these events are so intermingled, we need to decouple and characterize log events to understand which are issues we're hitting or not. >From what you've described there is at a minimum a firmware bug causing a spurious IRQ1. I suspect this when paired with any other number of wakeup events is causing either a system wakeup or not getting into the deepest state. So your "disabling keyboard wakeup" is probably a good idea until HP can fix that firmware bug. I also hypothesize my patch will help battery life when there are these types of spurious events but I don't really know for sure. So with the same debugging lines I suggested in comment #12 and my patches suggested we need you to issue a suspend and keep track of what you did when so we can correlate it to the events shown. > sleep 10; systemctl start suspend.target > just before closing the lid. That sounds good to me. Then we'll know if the EC had spurious events that woke the system and whether it went back to deepest state and how long. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
