Lines Matching refs:to
4 1. Testing hibernation (aka suspend to disk or STD)
6 To check if hibernation works, you can try to hibernate in the "reboot" mode:
11 and the system should create a hibernation image, reboot, resume and get back to
13 hibernation is most likely to work correctly. Still, you need to repeat the
17 modes causes the PM core to skip some platform-related callbacks which on ACPI
18 systems might be necessary to make hibernation work. Thus, if your machine fails
19 to hibernate or resume in the "reboot" mode, you should try the "platform" mode:
33 (it is similar to the "reboot" mode, but it requires you to press the power
34 button to make the system resume).
36 If neither "platform" nor "shutdown" hibernation mode works, you will need to
43 there is the file /sys/power/pm_test that can be used to make the hibernation
66 and are only tested if the hibernation mode is set to "platform"
68 To use one of them it is necessary to write the corresponding string to
69 /sys/power/pm_test (eg. "devices" to test the freezing of processes and
71 to use the "devices" test mode along with the "platform" mode of hibernation,
78 Then, the kernel will try to freeze processes, suspend devices, wait a few
80 parameter), resume devices and thaw processes. If "platform" is written to
82 invoke the global control methods (eg. ACPI global control methods) used to
85 methods used to cancel hibernation etc.
87 Writing "none" to /sys/power/pm_test causes the kernel to switch to the normal
98 and "processors" up to "core" (repeat the test on each level a couple of times
99 to make sure that any random factors are avoided).
102 it usually is possible to identify the offending task by analysing the output of
110 you can carry out a binary search according to the rules:
118 them), you have to unload it every time before hibernation. In that case please
119 make sure to report the problem with the driver.
122 unloaded all modules. In that case, you may want to look in your kernel
124 with these drivers compiled as modules). You may also try to use some special
129 of hibernation is not likely to work. You can try the "shutdown" mode, but that
134 should be reported. In that case you can also try to switch the nonboot CPUs
144 system to hang or become unstable, so please beware. Such a failure usually
145 indicates a serious problem that very well may be related to the hardware, but
151 "init=/bin/bash" command line parameter and attempt to hibernate in the
154 can try to compile more drivers as modules, so that they can be tested
158 - if there are n modules loaded and the attempt to suspend and resume fails,
161 - if there are n modules loaded and the attempt to suspend and resume succeeds,
172 techniques to find the problem. First, if there is a serial port in your box,
173 you can boot the kernel with the 'no_console_suspend' parameter and try to log
176 it may be possible to use a FireWire port for debugging with firescope
177 (http://v3.sk/~lkundrak/firescope/). On x86 it is also possible to
180 2. Testing suspend to RAM (STR)
182 To verify that the STR works, it is generally more convenient to use the s2ram
189 to given string. The STR test modes are defined in the same way as for
190 hibernation, so please refer to Section 1 for more information about them. In
191 particular, the "core" test allows you to test everything except for the actual
192 invocation of the platform firmware in order to put the system into the sleep
196 you to identify drivers that fail to suspend or resume their devices. They
199 Next, you can follow the instructions at S2RAM_LINK to test the system, but if
200 it does not work "out of the box", you may need to boot it with
202 you may be able to search for failing drivers by following the procedure
203 analogous to the one described in section 1. If you find some failing drivers,
204 you will have to unload them every time before an STR transition (ie. before
207 There is a debugfs entry which shows the suspend to RAM statistics. Here is an
226 Field success means the success number of suspend to RAM, and field fail means
228 to RAM. suspend_stats just lists the last 2 failed devices, error number and