Lines Matching full:test

18 test at least a couple of times in a row for confidence.  [This is necessary,
44 a) Test modes of hibernation
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
77 /sys/power/pm_test (eg. "devices" to test the freezing of processes and
79 to use the "devices" test mode along with the "platform" mode of hibernation,
98 represents the normal functionality) in which the current test level is
101 Generally, as you can see, each test level is more "invasive" than the previous
103 without creating a hibernation image.  Obviously, if the "devices" test fails,
104 the "platform" test will fail as well and so on.  Thus, as a rule of thumb, you
105 should try the test modes starting from "freezer", through "devices", "platform"
106 and "processors" up to "core" (repeat the test on each level a couple of times
109 If the "freezer" test fails, there is a task that cannot be frozen (in that case
111 dmesg obtained after the failing test).  Failure at this level usually means
115 If the "devices" test fails, most likely there is a driver that cannot suspend
117 after the test, so please take that into consideration).  To find this driver,
120 - if the test fails, unload a half of the drivers currently loaded and repeat
122   have been loaded before the test),
123 - if the test succeeds, load a half of the drivers you have unloaded most
130 It is also possible that the "devices" test will still fail after you have
132 configuration for the drivers that can be compiled as modules (and test again
136 If the "platform" test fails, there is a problem with the handling of the
141 If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
147 If the "core" test fails, which means that suspending of the system/platform
160 If all of the hibernation test modes work, you can boot the system with the
191 That test can be used to check if failures to resume from hibernation are
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
229 particular, the "core" test allows you to test everything except for the actual
237 Next, you can follow the instructions at S2RAM_LINK to test the system, but if
239 "init=/bin/bash" and test s2ram in the minimal configuration.  In that case,