Lines Matching +full:skip +full:- +full:power +full:- +full:up

12 	# echo reboot > /sys/power/disk
13 # echo disk > /sys/power/state
19 because some problems only show up on a second attempt at suspending and
21 modes causes the PM core to skip some platform-related callbacks which on ACPI
26 # echo platform > /sys/power/disk
27 # echo disk > /sys/power/state
35 # echo shutdown > /sys/power/disk
36 # echo disk > /sys/power/state
38 (it is similar to the "reboot" mode, but it requires you to press the power
45 ----------------------------
49 there is the file /sys/power/pm_test that can be used to make the hibernation
53 - test the freezing of processes
56 - test the freezing of processes and suspending of devices
59 - test the freezing of processes, suspending of devices and platform
63 - test the freezing of processes, suspending of devices, platform
67 - test the freezing of processes, suspending of devices, platform global
77 /sys/power/pm_test (eg. "devices" to test the freezing of processes and
82 # echo devices > /sys/power/pm_test
83 # echo platform > /sys/power/disk
84 # echo disk > /sys/power/state
89 /sys/power/pm_test , then after suspending devices the kernel will additionally
95 Writing "none" to /sys/power/pm_test causes the kernel to switch to the normal
96 hibernation/suspend operations. Also, when open for reading, /sys/power/pm_test
97 contains a space-separated list of all available tests (including "none" that
106 and "processors" up to "core" (repeat the test on each level a couple of times
120 - if the test fails, unload a half of the drivers currently loaded and repeat
123 - if the test succeeds, load a half of the drivers you have unloaded most
149 the problem is most probably hardware-related and serious, so it should be
158 --------------------------------
168 - if there are n modules loaded and the attempt to suspend and resume fails,
171 - if there are n modules loaded and the attempt to suspend and resume succeeds,
178 ---------------------------------------------
180 /sys/power/disk generally tells the kernel what to do after creating a
185 # echo test_resume > /sys/power/disk
186 # echo disk > /sys/power/state
204 ---------------------
215 use the PM_TRACE mechanism documented in Documentation/power/s2ram.rst .
225 into /sys/power/pm_test (available if the kernel is compiled with
233 Among other things, the testing with the help of /sys/power/pm_test may allow
248 # mount -t debugfs none /sys/kernel/debug
261 last_failed_errno: -16
262 -16