Lines Matching refs:resume

5  * If you touch anything on disk between suspend and resume...
8  * If you do resume from initrd after your filesystems are mounted...
15  * between suspend and resume, it may do something wrong. If you change
19  * (*) suspend/resume support is needed to make it safe.
22  * they won't be accessible after resume and you may lose data, as though
27 You need to append resume=/dev/your_swap_partition to kernel command
42 support. For suspend and resume to work, make sure your disk drivers
44 suspend/resume with modular disk drivers, see FAQ, but you probably
53 . The resume process checks for the presence of the resume device,
57 . The resume process may be triggered in two ways:
58   1) During lateinit:  If resume=/dev/your_swap_partition is specified on
59      the kernel command line, lateinit runs the resume process.  If the
60      resume device has not been probed yet, the resume process fails and
63      the init script by using the /sys/power/resume file.  It is vital
84 powerdowns.  You must explicitly specify the swap partition to resume from with
85 ``resume='' kernel option. If signature is found it loads and restores saved
117 resume.
228 after resume. swapoff -a; swapon -a may also be useful.
233 A: That's correct. We need to resume them if we want to write image to
247       resume(): devices are woken up so that we can write image to swap
261 …user processes are stopped (in common case there are none, but with resume-from-initrd, no one kno…
270       resume(): devices are woken up so that system can continue
278 protect from leaking sensitive data after resume from suspend.
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
287 for suspend. If you don't need swap after resume these data can remain
294 encrypt the data written to disk. When, during resume, the data was
301 from a failed or aborted resume is erased from the swap device.
306 resume.
310 A: Generally, yes, you can.  However, it requires you to use the "resume=" and
311 "resume_offset=" kernel command line parameters, so the resume from a swap file
345 /sys/power/resume file from initrd. Be sure not to mount
414 resume. uswsusp should be able to work with LVM. See suspend.sf.net.
418 suspend to disk (and resume) is much slower on 2.6.16 compared to
423 after resume).