Lines Matching +full:suspend +full:- +full:mode
2 Debugging hibernation and suspend
7 1. Testing hibernation (aka suspend to disk or STD)
10 To check if hibernation works, you can try to hibernate in the "reboot" mode::
21 modes causes the PM core to skip some platform-related callbacks which on ACPI
23 fails to hibernate or resume in the "reboot" mode, you should try the
24 "platform" mode::
29 which is the default and recommended mode of hibernation.
31 Unfortunately, the "platform" mode of hibernation does not work on some systems
32 with broken BIOSes. In such cases the "shutdown" mode of hibernation might
38 (it is similar to the "reboot" mode, but it requires you to press the power
41 If neither "platform" nor "shutdown" hibernation mode works, you will need to
45 ----------------------------
50 core run in a test mode. There are 5 test modes available:
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
74 and are only tested if the hibernation mode is set to "platform"
79 to use the "devices" test mode along with the "platform" mode of hibernation,
86 Then, the kernel will try to freeze processes, suspend devices, wait a few
87 seconds (5 by default, but configurable by the suspend.pm_test_delay module
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
115 If the "devices" test fails, most likely there is a driver that cannot suspend
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
137 platform (eg. ACPI) firmware on your system. In that case the "platform" mode
138 of hibernation is not likely to work. You can try the "shutdown" mode, but that
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 ---------------------------------------------
204 ---------------------
212 information about the reasons of the suspend (resume) failure. Alternatively,
217 2. Testing suspend to RAM (STR)
221 tool available from http://suspend.sf.net and documented at
226 CONFIG_PM_DEBUG set) the suspend code will work in the test mode corresponding
234 you to identify drivers that fail to suspend or resume their devices. They
245 There is a debugfs entry which shows the suspend to RAM statistics. Here is an
248 # mount -t debugfs none /sys/kernel/debug
261 last_failed_errno: -16
262 -16
263 last_failed_step: suspend
264 suspend
266 Field success means the success number of suspend to RAM, and field fail means
267 the failure number. Others are the failure number of different steps of suspend
269 failed step of suspend.