Lines Matching refs:and

1 Debugging hibernation and suspend
11 and the system should create a hibernation image, reboot, resume and get back to
15 because some problems only show up on a second attempt at suspending and
16 resuming the system.]  Moreover, hibernating in the "reboot" and "shutdown"
24 which is the default and recommended mode of hibernation.
50 - test the freezing of processes and suspending of devices
53 - test the freezing of processes, suspending of devices and platform
58   global control methods(*) and the disabling of nonboot CPUs
62   control methods(*), the disabling of nonboot CPUs and suspending of
66     and are only tested if the hibernation mode is set to "platform"
69 /sys/power/pm_test (eg. "devices" to test the freezing of processes and
70 suspending devices) and issue the standard hibernation commands.  For example,
80 parameter), resume devices and thaw processes.  If "platform" is written to
84 configurable number of seconds and invoke the platform (eg. ACPI) global
94 one and the "core" level tests the hardware and drivers as deeply as possible
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
111 - if the test fails, unload a half of the drivers currently loaded and repeat
115 recently and repeat.
123 configuration for the drivers that can be compiled as modules (and test again
133 work (of course, this only may be an issue on SMP systems) and the problem
135 off and on using the /sys/devices/system/cpu/cpu*/online sysfs attributes and
140 the problem is most probably hardware-related and serious, so it should be
151 "init=/bin/bash" command line parameter and attempt to hibernate in the
152 "reboot", "shutdown" and "platform" modes.  If that does not work, there
153 probably is a problem with a driver statically compiled into the kernel and you
155 individually.  Otherwise, there is a problem with a modular driver and you can
156 find it by loading a half of the modules you normally use and binary searching
158 - if there are n modules loaded and the attempt to suspend and resume fails,
159 unload n/2 of the modules and try again (that would probably involve rebooting
161 - if there are n modules loaded and the attempt to suspend and resume succeeds,
162 load n/2 modules more and try again.
165 before hibernation, and please report the problem with it(them).
170 configuration and compiling more drivers as modules is not practical or some
173 you can boot the kernel with the 'no_console_suspend' parameter and try to log
183 tool available from http://suspend.sf.net and documented at
201 "init=/bin/bash" and test s2ram in the minimal configuration.  In that case,
205 you run s2ram), and please report the problems with them.
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