Lines Matching refs:you

5  * If you touch anything on disk between suspend and resume...
8  * If you do resume from initrd after your filesystems are mounted...
12  * If you have unsupported (*) devices using DMA, you may have some
14  * it may cause some problems, too. If you change kernel command line
15  * between suspend and resume, it may do something wrong. If you change
21  * If you have any filesystems on USB devices mounted before software suspend,
22  * they won't be accessible after resume and you may lose data, as though
23  * you have unplugged the USB devices with mounted filesystems on them;
28 line. Then you suspend by
32 . If you feel ACPI works pretty well on your system, you might try
36 . If you would like to write hibernation image to swap and then suspend
37 to RAM (provided your platform supports it), you can try
41 . If you have SATA disks, you'll need recent kernels with SATA suspend
44 suspend/resume with modular disk drivers, see FAQ, but you probably
47 If you want to limit the suspend image size to N bytes, do
90 In the meantime while the system is suspended you should not add/remove any
96 There are three different interfaces you can use, /proc/acpi should
115 A: You bought new UPS for your server. How do you install it without
120 seconds to failure. What do you do? Suspend to disk.
134 * require half of memory to be free during suspend. That way you can
180 Q: I do not understand why you have such strong objections to idea of
184 it's useless for suspend-to-disk. (And I do not see how you could use
185 it for suspend-to-ram, I hope you do not want that).
187 Lets see, so you suggest to
196 you've corrupted data. You'd have to do
205 Which means that you still need that FREEZE state, and you get more
212 A: Doing SUSPEND when you are asked to do FREEZE is always correct,
213 but it may be unnecessarily slow. If you want your driver to stay simple,
214 slowness may not matter to you. It can always be fixed later.
216 For devices like disk it does matter, you do not want to spindown for
280 Think of the following: you suspend while an application is running
287 for suspend. If you don't need swap after resume these data can remain
289 broken in weeks later and sensitive data which you thought were
291 To prevent this situation you should use 'Encrypt suspend image'.
298 you must then take care of is that you call 'mkswap' for the swap
310 A: Generally, yes, you can.  However, it requires you to use the "resume=" and
346 anything, not even read-only mount, or you are going to lose your
351 A: If you want to see any non-error kernel messages on the virtual
352 terminal the kernel switches to during suspend, you have to set the
386 A: That's right ... if you disconnect that device, you may lose data.
387 In fact, even with "-o sync" you can lose data if your programs have
388 information in buffers they haven't written out to a disk you disconnect,
389 or if you disconnect before the device finished saving data you wrote.
413 A: No. You can suspend successfully, but you'll not be able to
426 image.  If you set it to 0 (eg. by echo 0 > /sys/power/image_size as