Lines Matching +full:suspend +full:- +full:in +full:- +full:wait
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::
18 test at least a couple of times in a row for confidence. [This is necessary,
20 resuming the system.] Moreover, hibernating in the "reboot" and "shutdown"
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
32 with broken BIOSes. In such cases the "shutdown" mode of hibernation might
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
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
91 prepare the platform firmware for hibernation. Next, it will wait a
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
98 represents the normal functionality) in which the current test level is
109 If the "freezer" test fails, there is a task that cannot be frozen (in that case
115 If the "devices" test fails, most likely there is a driver that cannot suspend
116 or resume its device (in the latter case the system may hang or become unstable
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
127 them), you have to unload it every time before hibernation. In that case please
131 unloaded all modules. In that case, you may want to look in your kernel
137 platform (eg. ACPI) firmware on your system. In that case the "platform" mode
143 should be reported. In that case you can also try to switch the nonboot CPUs
149 the problem is most probably hardware-related and serious, so it should be
158 --------------------------------
161 "init=/bin/bash" command line parameter and attempt to hibernate in the
167 in accordance with the algorithm:
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 ---------------------------------------------
189 immediately without involving the platform firmware in any way.
198 load it into memory is different from the one included in the image) or support
204 ---------------------
206 In case that hibernation does not work on your system even in the minimal
209 techniques to find the problem. First, if there is a serial port in your box,
212 information about the reasons of the suspend (resume) failure. Alternatively,
215 use the PM_TRACE mechanism documented in Documentation/power/s2ram.rst .
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
227 to given string. The STR test modes are defined in the same way as for
228 hibernation, so please refer to Section 1 for more information about them. In
230 invocation of the platform firmware in order to put the system into the sleep
234 you to identify drivers that fail to suspend or resume their devices. They
239 "init=/bin/bash" and test s2ram in the minimal configuration. In that case,
241 analogous to the one described in section 1. If you find some failing drivers,
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.