Lines Matching refs:of

14 test at least a couple of times in a row for confidence.  [This is necessary,
24 which is the default and recommended mode of hibernation.
26 Unfortunately, the "platform" mode of hibernation does not work on some systems
27 with broken BIOSes. In such cases the "shutdown" mode of hibernation might
39 a) Test modes of hibernation
47 - test the freezing of processes
50 - test the freezing of processes and suspending of devices
53 - test the freezing of processes, suspending of devices and platform
57 - test the freezing of processes, suspending of devices, platform
58 global control methods(*) and the disabling of nonboot CPUs
61 - test the freezing of processes, suspending of devices, platform global
62 control methods(*), the disabling of nonboot CPUs and suspending of
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,
84 configurable number of seconds and invoke the platform (eg. ACPI) global
89 contains a space-separated list of all available tests (including "none" that
96 the "platform" test will fail as well and so on. Thus, as a rule of thumb, you
98 and "processors" up to "core" (repeat the test on each level a couple of times
102 it usually is possible to identify the offending task by analysing the output of
111 - if the test fails, unload a half of the drivers currently loaded and repeat
114 - if the test succeeds, load a half of the drivers you have unloaded most
117 Once you have found the failing driver (there can be more than just one of
127 If the "platform" test fails, there is a problem with the handling of the
129 of hibernation is not likely to work. You can try the "shutdown" mode, but that
132 If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
133 work (of course, this only may be an issue on SMP systems) and the problem
138 If the "core" test fails, which means that suspending of the system/platform
143 A failure of any of the "platform", "processors" or "core" tests may cause your
150 If all of the hibernation test modes work, you can boot the system with the
156 find it by loading a half of the modules you normally use and binary searching
159 unload n/2 of the modules and try again (that would probably involve rebooting
171 modules cannot be unloaded, you can use one of the more advanced debugging
175 information about the reasons of the suspend (resume) failure. Alternatively,
192 invocation of the platform firmware in order to put the system into the sleep
195 Among other things, the testing with the help of /sys/power/pm_test may allow
200 it does not work "out of the box", you may need to boot it with
208 example of its output.
226 Field success means the success number of suspend to RAM, and field fail means
227 the failure number. Others are the failure number of different steps of suspend
229 failed step of suspend.