Commit a11975b1 authored by Pavel Machek's avatar Pavel Machek Committed by Linus Torvalds

[PATCH] swsusp: Documentation update

Documentation update.
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent 13a82a1e
...@@ -15,10 +15,18 @@ From kernel/suspend.c: ...@@ -15,10 +15,18 @@ From kernel/suspend.c:
* If you change kernel command line between suspend and resume... * If you change kernel command line between suspend and resume...
* ...prepare for nasty fsck or worse. * ...prepare for nasty fsck or worse.
* *
* (*) pm interface support is needed to make it safe. * (*) suspend/resume support is needed to make it safe.
You need to append resume=/dev/your_swap_partition to kernel command You need to append resume=/dev/your_swap_partition to kernel command
line. Then you suspend by echo 4 > /proc/acpi/sleep. line. Then you suspend by
echo shutdown > /sys/power/disk; echo disk > /sys/power/state
. If you feel ACPI works pretty well on your system, you might try
echo platform > /sys/power/disk; echo disk > /sys/power/state
Article about goals and implementation of Software Suspend for Linux Article about goals and implementation of Software Suspend for Linux
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...@@ -32,42 +40,24 @@ saves the state of the machine to a filesystem or to a partition and switches ...@@ -32,42 +40,24 @@ saves the state of the machine to a filesystem or to a partition and switches
to standby mode. Later resuming the machine the saved state is loaded back to to standby mode. Later resuming the machine the saved state is loaded back to
ram and the machine can continue its work. It has two real benefits. First we ram and the machine can continue its work. It has two real benefits. First we
save ourselves the time machine goes down and later boots up, energy costs save ourselves the time machine goes down and later boots up, energy costs
real high when running from batteries. The other gain is that we don't have to are real high when running from batteries. The other gain is that we don't have to
interrupt our programs so processes that are calculating something for a long interrupt our programs so processes that are calculating something for a long
time shouldn't need to be written interruptible. time shouldn't need to be written interruptible.
Using the code swsusp saves the state of the machine into active swaps and then reboots or
powerdowns. You must explicitly specify the swap partition to resume from with
You have two ways to use this code. The first one is is with a patched
SysVinit (my patch is against 2.76 and available at my home page). You
might call 'swsusp' or 'shutdown -z <time>'. Next way is to echo 4 >
/proc/acpi/sleep.
Either way it saves the state of the machine into active swaps and then
reboots. You must explicitly specify the swap partition to resume from with
``resume='' kernel option. If signature is found it loads and restores saved ``resume='' kernel option. If signature is found it loads and restores saved
state. If the option ``noresume'' is specified as a boot parameter, it skips state. If the option ``noresume'' is specified as a boot parameter, it skips
the resuming. the resuming.
In the meantime while the system is suspended you should not touch any of the In the meantime while the system is suspended you should not add/remove any
hardware! of the hardware, write to the filesystems, etc.
About the code
Things to implement
- We should only make a copy of data related to kernel segment, since any
process data won't be changed.
- Should make more sanity checks. Or are these enough?
Not so important ideas for implementing Sleep states summary
====================
- If a real time process is running then don't suspend the machine. There are three different interfaces you can use, /proc/acpi should
- Support for adding/removing hardware while suspended? work like this:
- We should not free pages at the beginning so aggressively, most of them
go there anyway..
Sleep states summary (thanx, Ducrot)
====================================
In a really perfect world: In a really perfect world:
echo 1 > /proc/acpi/sleep # for standby echo 1 > /proc/acpi/sleep # for standby
...@@ -79,7 +69,6 @@ echo 5 > /proc/acpi/sleep # for shutdown unfriendly the system ...@@ -79,7 +69,6 @@ echo 5 > /proc/acpi/sleep # for shutdown unfriendly the system
and perhaps and perhaps
echo 4b > /proc/acpi/sleep # for suspend to disk via s4bios echo 4b > /proc/acpi/sleep # for suspend to disk via s4bios
Frequently Asked Questions Frequently Asked Questions
========================== ==========================
...@@ -123,21 +112,7 @@ advance. That means that the limitation goes away in practice. ...@@ -123,21 +112,7 @@ advance. That means that the limitation goes away in practice.
Q: Does linux support ACPI S4? Q: Does linux support ACPI S4?
A: No. A: Yes. That's what echo platform > /sys/power/disk does.
When swsusp was created, ACPI was not too widespread, so we tried to
avoid using ACPI-specific stuff. ACPI also is/was notoriously
buggy. These days swsusp works on APM-only i386 machines and even
without any power managment at all. Some versions also work on PPC.
That means that machine does not enter S4 on suspend-to-disk, but
simply enters S5. That has few advantages, you can for example boot
windows on next boot, and return to your Linux session later. You
could even have few different Linuxes on your box (not sharing any
partitions), and switch between them.
It also has disadvantages. On HP nx5000, if you unplug power cord
while machine is suspended-to-disk, Linux will fail to notice that.
Q: My machine doesn't work with ACPI. How can I use swsusp than ? Q: My machine doesn't work with ACPI. How can I use swsusp than ?
...@@ -162,6 +137,8 @@ int main() ...@@ -162,6 +137,8 @@ int main()
return 0; return 0;
} }
Also /sys/ interface should be still present.
Q: What is 'suspend2'? Q: What is 'suspend2'?
A: suspend2 is 'Software Suspend 2', a forked implementation of A: suspend2 is 'Software Suspend 2', a forked implementation of
...@@ -175,17 +152,22 @@ should be sent to the mailing list available through the suspend2 ...@@ -175,17 +152,22 @@ should be sent to the mailing list available through the suspend2
website, and not to the Linux Kernel Mailing List. We are working website, and not to the Linux Kernel Mailing List. We are working
toward merging suspend2 into the mainline kernel. toward merging suspend2 into the mainline kernel.
Q: Kernel thread must voluntarily freeze itself (call 'refrigerator'). But Q: A kernel thread must voluntarily freeze itself (call 'refrigerator').
I found some kernel threads don't do it, and they don't freeze, and I found some kernel threads that don't do it, and they don't freeze
so the system can't sleep. Is this a known behavior? so the system can't sleep. Is this a known behavior?
A: All such kernel threads need to be fixed, one by one. Select place A: All such kernel threads need to be fixed, one by one. Select the
where it is safe to be frozen (no kernel semaphores should be held at place where the thread is safe to be frozen (no kernel semaphores
that point and it must be safe to sleep there), and add: should be held at that point and it must be safe to sleep there), and
add:
if (current->flags & PF_FREEZE) if (current->flags & PF_FREEZE)
refrigerator(PF_FREEZE); refrigerator(PF_FREEZE);
If the thread is needed for writing the image to storage, you should
instead set the PF_NOFREEZE process flag when creating the thread.
Q: What is the difference between between "platform", "shutdown" and Q: What is the difference between between "platform", "shutdown" and
"firmware" in /sys/power/disk? "firmware" in /sys/power/disk?
......
...@@ -17,15 +17,18 @@ There are three types of systems where video works after S3 resume: ...@@ -17,15 +17,18 @@ There are three types of systems where video works after S3 resume:
* systems where video state is preserved over S3. (Athlon HP Omnibook xe3s) * systems where video state is preserved over S3. (Athlon HP Omnibook xe3s)
* systems that initialize video card into vga text mode and where BIOS
works well enough to be able to set video mode. Use
acpi_sleep=s3_mode on these. (Toshiba 4030cdt)
* systems where it is possible to call video bios during S3 * systems where it is possible to call video bios during S3
resume. Unfortunately, it is not correct to call video BIOS at that resume. Unfortunately, it is not correct to call video BIOS at that
point, but it happens to work on some machines. Use point, but it happens to work on some machines. Use
acpi_sleep=s3_bios (Athlon64 desktop system) acpi_sleep=s3_bios (Athlon64 desktop system)
* systems that initialize video card into vga text mode and where BIOS
works well enough to be able to set video mode. Use
acpi_sleep=s3_mode on these. (Toshiba 4030cdt)
* on some systems s3_bios kicks video into text mode, and
acpi_sleep=s3_bios,s3_mode is needed (Toshiba Satellite P10-554)
* radeon systems, where X can soft-boot your video card. You'll need * radeon systems, where X can soft-boot your video card. You'll need
patched X, and plain text console (no vesafb or radeonfb), see patched X, and plain text console (no vesafb or radeonfb), see
http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. (Acer TM 800) http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. (Acer TM 800)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment