summaryrefslogtreecommitdiffstats
path: root/Documentation/power/basic-pm-debugging.txt
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-08-13 02:54:04 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-08-13 02:54:04 +0200
commit947d2c2cd3340d11a1737d3f4781170cc3a4b74f (patch)
treea0a21bb89fad010a7fba3c0e99da85a117a4d1ef /Documentation/power/basic-pm-debugging.txt
parent62822e2ec4ad091ba31f823f577ef80db52e3c2c (diff)
downloadtalos-obmc-linux-947d2c2cd3340d11a1737d3f4781170cc3a4b74f.tar.gz
talos-obmc-linux-947d2c2cd3340d11a1737d3f4781170cc3a4b74f.zip
PM / sleep: Update some system sleep documentation
Update some documentation related to system sleep to document new features and remove outdated information from it. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by: Pavel Machek <pavel@ucw.cz> Reviewed-by: Chen Yu <yu.c.chen@intel.com>
Diffstat (limited to 'Documentation/power/basic-pm-debugging.txt')
-rw-r--r--Documentation/power/basic-pm-debugging.txt27
1 files changed, 26 insertions, 1 deletions
diff --git a/Documentation/power/basic-pm-debugging.txt b/Documentation/power/basic-pm-debugging.txt
index b96098ccfe69..708f87f78a75 100644
--- a/Documentation/power/basic-pm-debugging.txt
+++ b/Documentation/power/basic-pm-debugging.txt
@@ -164,7 +164,32 @@ load n/2 modules more and try again.
Again, if you find the offending module(s), it(they) must be unloaded every time
before hibernation, and please report the problem with it(them).
-c) Advanced debugging
+c) Using the "test_resume" hibernation option
+
+/sys/power/disk generally tells the kernel what to do after creating a
+hibernation image. One of the available options is "test_resume" which
+causes the just created image to be used for immediate restoration. Namely,
+after doing:
+
+# echo test_resume > /sys/power/disk
+# echo disk > /sys/power/state
+
+a hibernation image will be created and a resume from it will be triggered
+immediately without involving the platform firmware in any way.
+
+That test can be used to check if failures to resume from hibernation are
+related to bad interactions with the platform firmware. That is, if the above
+works every time, but resume from actual hibernation does not work or is
+unreliable, the platform firmware may be responsible for the failures.
+
+On architectures and platforms that support using different kernels to restore
+hibernation images (that is, the kernel used to read the image from storage and
+load it into memory is different from the one included in the image) or support
+kernel address space randomization, it also can be used to check if failures
+to resume may be related to the differences between the restore and image
+kernels.
+
+d) Advanced debugging
In case that hibernation does not work on your system even in the minimal
configuration and compiling more drivers as modules is not practical or some
OpenPOWER on IntegriCloud