https://bugzilla.kernel.org/show_bug.cgi?id=216516 --- Comment #12 from Mario Limonciello (AMD) (mario.limonciello@xxxxxxx) --- > Compiled with CONFIG_AMD_PMC. > Going to s2idle two times. > (first time just for a few seconds) It looks better to me now. > After less than 8 hours in s2idle the battery went from 60 % to 0 % !!! > That's why there's no second wakeup. > (system was down because battery was drained) I suspect one of two things happened: 1) A spurious event actually woke up the SOC the second time but it never re-entered. 2) You entered back to back and didn't get into the deepest state due to a timing issue. I know of a potential patch I can offer you for this, but we need to confirm the root cause before I write it up. > With S3 the battery will loose less than 5 % charge in the same time. > And the notebook is brand new. So there should be no battery degradation. > ... just did another s2idle test and battery went from 67 % to 58 % in one > hour. It's up to the OEM's design how quickly it will lose battery over Modern Standby/s2idle, it has a lot of factors involved. I'll describe some additional debugging tactics later in this response. > I think you exaggerate a little. > I'm just enabling existing OEM code! > Also I wouldn't say this is patching the firmware, because it's just the ACPI > data, not the BIOS software. > Just changing the existing "if" statement. > See: comment #5 > I'm pretty sure there's a way to enable this OEM code without recompiling the > ACPI data. Probably by setting the MSCE variable with a hidden BIOS option or > something else I haven't found yet. What you're seeing in there is a remnant of AGESA reference code. I see the same thing in AMD's reference designs and in other OEM designs. There is definitely OEM effort involved with enabling S3, and like I said there are lots of other firmware components involved that are invisible to the OS. The other thing I want to point out - if they use Modern Standby in Windows, this is the path that has gotten lots of validation. A non-validated path is likely to have unique bugs. > s2idle just should be more energy efficient. > S3 is using less than 1 % battery per hour. So if there's a way to get s2idle > down to 2 % per hour that would be a good solution. For most mobile designs the power consumption is better for s2idle than S3. I suspect you're hitting a bug with wakeups, or s2idle re-entries. For the next step in debugging, please do all of the following: 0) 6.0-rc6 kernel 1) Add to your kernel command line: acpi.dyndbg='file drivers/acpi/x86/s2idle.c +p' amd_pmc.dyndbg='+p' 2) set /sys/power/pm_print_times to 1. 3) set /sys/power/pm_debug_messages to 1 With all those debugging things put in place, run a sample where you put it to sleep for a short period of time (say 10 minutes), and then wakeup and share the log. Please note how you woke up the system. Hopefully based upon that log it will be clearer what is causing your increased power consumption. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
