https://bugzilla.kernel.org/show_bug.cgi?id=197149
Zhang Rui ([email protected]) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |[email protected] Resolution|--- |INVALID Assignee|acpi_power-sleep-wake@kerne |[email protected] |l-bugs.osdl.org | --- Comment #2 from Zhang Rui ([email protected]) --- [ 0.378836] ACPI: (supports S0 S1 S4 S5) S0 is not supported according to the dmesg. For the issue you're seeing, please check /sys/power/mem_sleep, and make sure it returns "s2idle", which means the system actually enters suspend-to-idle when you run "echo mem > /sys/power/state". please refer to this commit for details. commit 406e79385f3223d82272cf2be86bc95cd000a258 Author: Rafael J. Wysocki <[email protected]> AuthorDate: Mon Nov 21 22:45:40 2016 +0100 Commit: Rafael J. Wysocki <[email protected]> CommitDate: Mon Nov 21 22:45:40 2016 +0100 PM / sleep: System sleep state selection interface rework There are systems in which the platform doesn't support any special sleep states, so suspend-to-idle (PM_SUSPEND_FREEZE) is the only available system sleep state. However, some user space frameworks only use the "mem" and (sometimes) "standby" sleep state labels, so the users of those systems need to modify user space in order to be able to use system suspend at all and that may be a pain in practice. Commit 0399d4db3edf (PM / sleep: Introduce command line argument for sleep state enumeration) attempted to address this problem by adding a command line argument to change the meaning of the "mem" string in /sys/power/state to make it trigger suspend-to-idle (instead of suspend-to-RAM). However, there also are systems in which the platform does support special sleep states, but suspend-to-idle is the preferred one anyway (it even may save more energy than the platform-provided sleep states in some cases) and the above commit doesn't help in those cases. For this reason, rework the system sleep state selection interface again (but preserve backwards compatibiliby). Namely, add a new sysfs file, /sys/power/mem_sleep, that will control the system suspend mode triggered by writing "mem" to /sys/power/state (in analogy with what /sys/power/disk does for hibernation). Make it select suspend-to-RAM ("deep" sleep) by default (if supported) and fall back to suspend-to-idle ("s2idle") otherwise and add a new command line argument, mem_sleep_default, allowing that default to be overridden if need be. At the same time, drop the relative_sleep_states command line argument that doesn't make sense any more. Signed-off-by: Rafael J. Wysocki <[email protected]> Tested-by: Mario Limonciello <[email protected]> BTW, please feel free to reopen it if this is not the problem you met. -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
