diff options
| author | Jens Frederich <jfrederich@gmail.com> | 2013-08-21 21:03:09 -0700 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2013-08-27 10:54:52 +0200 |
| commit | 54d4f25b35007ee15a9ce6b8f644cfaee4cc614b (patch) | |
| tree | d5e3c5173e205ecb033a5d369b3ce6b4492b08e0 | |
| parent | 453f42d3881a545b21d2f6aa15e62c6a9e4901a2 (diff) | |
| download | op-kernel-dev-54d4f25b35007ee15a9ce6b8f644cfaee4cc614b.zip op-kernel-dev-54d4f25b35007ee15a9ce6b8f644cfaee4cc614b.tar.gz | |
power: Documentation: Update s2ram link
The s2ram link is broken because there is a new OpenSuse wiki online.
The page does no longer exist, it was merged in the Suspend_to_RAM
page.
Signed-off-by: Jens Frederich <jfrederich@gmail.com>
Acked-by: Rob Landley <rob@landley.net>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
| -rw-r--r-- | Documentation/power/basic-pm-debugging.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/power/basic-pm-debugging.txt b/Documentation/power/basic-pm-debugging.txt index 262acf5..e9b54de8 100644 --- a/Documentation/power/basic-pm-debugging.txt +++ b/Documentation/power/basic-pm-debugging.txt @@ -179,7 +179,7 @@ use the PM_TRACE mechanism documented in Documentation/power/s2ram.txt . To verify that the STR works, it is generally more convenient to use the s2ram tool available from http://suspend.sf.net and documented at -http://en.opensuse.org/SDB:Suspend_to_RAM. +http://en.opensuse.org/SDB:Suspend_to_RAM (S2RAM_LINK). Namely, after writing "freezer", "devices", "platform", "processors", or "core" into /sys/power/pm_test (available if the kernel is compiled with @@ -194,10 +194,10 @@ Among other things, the testing with the help of /sys/power/pm_test may allow you to identify drivers that fail to suspend or resume their devices. They should be unloaded every time before an STR transition. -Next, you can follow the instructions at http://en.opensuse.org/s2ram to test -the system, but if it does not work "out of the box", you may need to boot it -with "init=/bin/bash" and test s2ram in the minimal configuration. In that -case, you may be able to search for failing drivers by following the procedure +Next, you can follow the instructions at S2RAM_LINK to test the system, but if +it does not work "out of the box", you may need to boot it with +"init=/bin/bash" and test s2ram in the minimal configuration. In that case, +you may be able to search for failing drivers by following the procedure analogous to the one described in section 1. If you find some failing drivers, you will have to unload them every time before an STR transition (ie. before you run s2ram), and please report the problems with them. |
