Lines Matching refs:to
19 * (*) suspend/resume support is needed to make it safe.
27 You need to append resume=/dev/your_swap_partition to kernel command
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
42 support. For suspend and resume to work, make sure your disk drivers
43 are built into kernel -- not modules. [There's way to make
47 If you want to limit the suspend image size to N bytes, do
51 before suspend (it is limited to 500 MB by default).
64 that this be done prior to remounting any filesystems (even as
72 Idea and goals to achieve
75 saves the state of the machine to a filesystem or to a partition and switches
76 to standby mode. Later resuming the machine the saved state is loaded back to
79 are real high when running from batteries. The other gain is that we don't have to
81 time shouldn't need to be written interruptible.
84 powerdowns. You must explicitly specify the swap partition to resume from with
91 of the hardware, write to the filesystems, etc.
101 echo 2 > /proc/acpi/sleep # for suspend to ram
102 echo 3 > /proc/acpi/sleep # for suspend to ram, but with more power conservative
103 echo 4 > /proc/acpi/sleep # for suspend to disk
107 echo 4b > /proc/acpi/sleep # for suspend to disk via s4bios
116 bringing machine down? Suspend to disk, rearrange power cables,
120 seconds to failure. What do you do? Suspend to disk.
126 to its original location as we load it. That would create an
129 it back to it original location. This implies, of course, a maximum
132 There are two solutions to this:
134 * require half of memory to be free during suspend. That way you can
138 between 0-640KB. That way, I'd have to make sure that 0-640KB is free
152 suspend-to-disk which is available as separate patches for 2.4 and 2.6
156 encryption) and arbitrary backends for writing the image (eg to swap
158 should be sent to the mailing list available through the suspend2
159 website, and not to the Linux Kernel Mailing List. We are working
172 shutdown: save state in linux, then tell bios to powerdown
174 platform: save state in linux, then tell bios to powerdown and blink
177 "platform" is actually right thing to do where supported, but
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
191 * Write image to disk
196 you've corrupted data. You'd have to do
209 Q: There don't seem to be any generally useful behavioral
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
219 Q: After resuming, system is paging heavily, leading to very bad interactivity.
230 Q: What happens to devices during swsusp? They seem to be resumed
233 A: That's correct. We need to resume them if we want to write image to
238 running system, user asks for suspend-to-disk
247 resume(): devices are woken up so that we can write image to swap
249 write image to swap
259 running system, user asks for suspend-to-disk
283 data to swap to be able to resume later on. Without suspend encryption
285 that after resume your sensitive data are accessible to all
286 applications having direct access to the swap device which was used
293 During suspend a temporary key is created and this key is used to
294 encrypt the data written to disk. When, during resume, the data was
296 means that all data written to disk during suspend are then
303 As a rule of thumb use encrypted swap to protect your data while your
305 suspend image to prevent sensitive data from being stolen after
308 Q: Can I suspend to a swap file?
310 A: Generally, yes, you can. However, it requires you to use the "resume=" and
319 Q: Does swsusp (to disk) use only one swap partition or can it use
324 Q: If my application(s) causes lots of memory & swap space to be used
326 to be useless to try to suspend to disk while that app is running?
331 Q: What information is useful for debugging suspend-to-disk problems?
335 little as possible modules loaded helps a lot. I also prefer people to
338 usually does the trick. Then it is good idea to try with latest
345 /sys/power/resume file from initrd. Be sure not to mount
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
353 kernel console loglevel to at least 4 (KERN_WARNING), for example by
371 # then try again with image_size set to zero.
383 I suspend to disk, I can lose data unless the filesystem has been mounted
388 information in buffers they haven't written out to a disk you disconnect,
392 to disconnecting all USB devices attached to your system.
396 modes like "suspend-to-RAM" or "standby". (Don't write "disk" to the
402 Remember that it's always a bad idea to unplug a disk drive containing a
404 safest thing is to unmount all filesystems on removable media (such USB,
411 Q: Can I suspend-to-disk using a swap partition under LVM?
414 to resume on its own. You need an initramfs that can recognize the resume
425 Q: I upgraded the kernel from 2.6.15 to 2.6.16. Both kernels were
427 suspend to disk (and resume) is much slower on 2.6.16 compared to
435 image. If you set it to 0 (eg. by echo 0 > /sys/power/image_size as
438 supports LZF compression to speed it up further.