summaryrefslogtreecommitdiffstats
path: root/Documentation/power/swsusp.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/power/swsusp.txt')
-rw-r--r--Documentation/power/swsusp.txt13
1 files changed, 11 insertions, 2 deletions
diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
index f732a8321e8a..8cc17ca71813 100644
--- a/Documentation/power/swsusp.txt
+++ b/Documentation/power/swsusp.txt
@@ -410,8 +410,17 @@ Documentation/usb/persist.txt.
410 410
411Q: Can I suspend-to-disk using a swap partition under LVM? 411Q: Can I suspend-to-disk using a swap partition under LVM?
412 412
413A: No. You can suspend successfully, but you'll not be able to 413A: Yes and No. You can suspend successfully, but the kernel will not be able
414resume. uswsusp should be able to work with LVM. See suspend.sf.net. 414to resume on its own. You need an initramfs that can recognize the resume
415situation, activate the logical volume containing the swap volume (but not
416touch any filesystems!), and eventually call
417
418echo -n "$major:$minor" > /sys/power/resume
419
420where $major and $minor are the respective major and minor device numbers of
421the swap volume.
422
423uswsusp works with LVM, too. See http://suspend.sourceforge.net/
415 424
416Q: I upgraded the kernel from 2.6.15 to 2.6.16. Both kernels were 425Q: I upgraded the kernel from 2.6.15 to 2.6.16. Both kernels were
417compiled with the similar configuration files. Anyway I found that 426compiled with the similar configuration files. Anyway I found that