Lines Matching refs:test

14 test at least a couple of times in a row for confidence.  [This is necessary,
44 core run in a test mode.  There are 5 test modes available:
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
61 - test the freezing of processes, suspending of devices, platform global
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,
90 represents the normal functionality) in which the current test level is
93 Generally, as you can see, each test level is more "invasive" than the previous
95 without creating a hibernation image.  Obviously, if the "devices" test fails,
96 the "platform" test will fail as well and so on.  Thus, as a rule of thumb, you
97 should try the test modes starting from "freezer", through "devices", "platform"
98 and "processors" up to "core" (repeat the test on each level a couple of times
101 If the "freezer" test fails, there is a task that cannot be frozen (in that case
103 dmesg obtained after the failing test).  Failure at this level usually means
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,
111 - if the test fails, unload a half of the drivers currently loaded and repeat
113 have been loaded before the test),
114 - if the test succeeds, load a half of the drivers you have unloaded most
121 It is also possible that the "devices" test will still fail after you have
123 configuration for the drivers that can be compiled as modules (and test again
127 If the "platform" test fails, there is a problem with the handling of the
132 If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
138 If the "core" test fails, which means that suspending of the system/platform
150 If all of the hibernation test modes work, you can boot the system with the
188 CONFIG_PM_DEBUG set) the suspend code will work in the test mode corresponding
189 to given string.  The STR test modes are defined in the same way as for
191 particular, the "core" test allows you to test everything except for the actual
199 Next, you can follow the instructions at S2RAM_LINK to test the system, but if
201 "init=/bin/bash" and test s2ram in the minimal configuration.  In that case,