Lines Matching full:resume

11    If you touch anything on disk between suspend and resume...
14    If you do resume from initrd after your filesystems are mounted...
22    between suspend and resume, it may do something wrong. If you change
26    ( ) suspend/resume support is needed to make it safe.
29    they won't be accessible after resume and you may lose data, as though
35   You need to append resume=/dev/your_swap_partition to kernel command
36   line or specify it using /sys/power/resume.
39   If using a swapfile you can also specify a resume offset using
57   support. For suspend and resume to work, make sure your disk drivers
59   suspend/resume with modular disk drivers, see FAQ, but you probably
68 - The resume process checks for the presence of the resume device,
72 - The resume process may be triggered in two ways:
74   1) During lateinit:  If resume=/dev/your_swap_partition is specified on
75      the kernel command line, lateinit runs the resume process.  If the
76      resume device has not been probed yet, the resume process fails and
79      the init script by using the /sys/power/resume file.  It is vital
102 powerdowns.  You must explicitly specify the swap partition to resume from with
103 `resume=` kernel option. If signature is found it loads and restores saved
140   resume.
267   after resume. swapoff -a; swapon -a may also be useful.
274   That's correct. We need to resume them if we want to write image to
289       resume(): devices are woken up so that we can write image to swap
297       **Resume part**
304       but with resume-from-initrd, no one knows)
313       resume(): devices are woken up so that system can continue
323   protect from leaking sensitive data after resume from suspend.
328   data to swap to be able to resume later on. Without suspend encryption
330   that after resume your sensitive data are accessible to all
332   for suspend. If you don't need swap after resume these data can remain
339   encrypt the data written to disk. When, during resume, the data was
346   from a failed or aborted resume is erased from the swap device.
351   resume.
357   Generally, yes, you can.  However, it requires you to use the "resume=" and
358   "resume_offset=" kernel command line parameters, so the resume from a swap
402   /sys/power/resume file from initrd. Be sure not to mount
477   to resume on its own.  You need an initramfs that can recognize the resume
481     echo -n "$major:$minor" > /sys/power/resume
491   suspend to disk (and resume) is much slower on 2.6.16 compared to
497   after resume).