Lines Matching refs:you

6 To check if hibernation works, you can try to hibernate in the "reboot" mode:
12 the command prompt where you have started the transition.  If that happens,
13 hibernation is most likely to work correctly.  Still, you need to repeat the
19 to hibernate or resume in the "reboot" mode, you should try the "platform" mode:
33 (it is similar to the "reboot" mode, but it requires you to press the power
36 If neither "platform" nor "shutdown" hibernation mode works, you will need to
41 To find out why hibernation fails on your system, you can use a special testing
72 you should do the following:
93 Generally, as you can see, each test level is more "invasive" than the previous
96 the "platform" test will fail as well and so on.  Thus, as a rule of thumb, you
110 you can carry out a binary search according to the rules:
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
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
134 should be reported.  In that case you can also try to switch the nonboot CPUs
150 If all of the hibernation test modes work, you can boot the system with the
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
164 Again, if you find the offending module(s), it(they) must be unloaded every time
171 modules cannot be unloaded, you can use one of the more advanced debugging
173 you can boot the kernel with the 'no_console_suspend' parameter and try to log
174 kernel messages using the serial console.  This may provide you with some
191 particular, the "core" test allows you to test everything except for the actual
196 you to identify drivers that fail to suspend or resume their devices.  They
199 Next, you can follow the instructions at S2RAM_LINK to test the system, but if
200 it does not work "out of the box", you may need to boot it with
202 you may be able to search for failing drivers by following the procedure
203 analogous to the one described in section 1.  If you find some failing drivers,
204 you will have to unload them every time before an STR transition (ie. before
205 you run s2ram), and please report the problems with them.