Lines Matching refs:that

12 the command prompt where you have started the transition.  If that happens,
43 there is the file /sys/power/pm_test that can be used to make the hibernation
89 contains a space-separated list of all available tests (including "none" that
99 to make sure that any random factors are avoided).
101 If the "freezer" test fails, there is a task that cannot be frozen (in that case
104 that there is a problem with the tasks freezer subsystem that should be
107 If the "devices" test fails, most likely there is a driver that cannot suspend
109 after the test, so please take that into consideration).  To find this driver,
112 (that would probably involve rebooting the system, so always note what drivers
118 them), you have to unload it every time before hibernation.  In that case please
121 It is also possible that the "devices" test will still fail after you have
122 unloaded all modules. In that case, you may want to look in your kernel
123 configuration for the drivers that can be compiled as modules (and test again
128 platform (eg. ACPI) firmware on your system.  In that case the "platform" mode
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
136 see if that works.
138 If the "core" test fails, which means that suspending of the system/platform
145 indicates a serious problem that very well may be related to the hardware, but
152 "reboot", "shutdown" and "platform" modes.  If that does not work, there
154 can try to compile more drivers as modules, so that they can be tested
159 unload n/2 of the modules and try again (that would probably involve rebooting
169 In case that hibernation does not work on your system even in the minimal
182 To verify that the STR works, it is generally more convenient to use the s2ram
196 you to identify drivers that fail to suspend or resume their devices.  They
201 "init=/bin/bash" and test s2ram in the minimal configuration.  In that case,