https://bugzilla.kernel.org/show_bug.cgi?id=216516 --- Comment #22 from kolAflash (kolAflash@xxxxxxxxxxxx) --- (In reply to Mario Limonciello (AMD) from comment #21) > > --> And closing the notebook lid is what's waking the CPU! > [...] > > 1. Stay in deepest sleep state when closing the lid. (or immediately return > > to deepest sleep) > > When you close the lid we need to know whether the kernel leaves the suspend > loop or not. If it didn't leave the suspend loop then my hypothesis is the > act of going into suspend and then closing the lid causes a Linux specific > race condition that prevents going into the deepest state. That's why I > proposed by usleep_range patch. It will only help with power consumption if > the kernel is still in the s2idle loop. I don't fully understand what you want me to do now. Please clarify. The logs I attached where made with a v6.0-rc7 kernel containing all patches you mentioned in comment 14. Including the usleep_range patch. Does these logs help you? > > 3. Bring the s2idle power consumption further down below 2 % per hour. > > That last usleep_range patch is what I'm most interested in to fix this. If > you run a longer suspend, I suspect it might help with going to sleep from > an EC triggered event for battery life notification. So I should put the notebook to sleep for one hour, without closing the lid? OK, I'll do sleep 10; systemctl start suspend.target just before closing the lid. (then put the notebook into my bag and go home from work) (using the comment 14 patched kernel) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
