From: Chen Yu <yu.c.chen@intel.com>
To: Linux PM List <linux-pm@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH][RFC] Documentation/: update hibernation debug documentation
Date: Thu, 11 Aug 2016 20:18:11 +0800 [thread overview]
Message-ID: <1470917891-8386-1-git-send-email-yu.c.chen@intel.com> (raw)
Update the description of test_resume mode for hibernation.
Signed-off-by: Chen Yu <yu.c.chen@intel.com>
---
Documentation/power/basic-pm-debugging.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/power/basic-pm-debugging.txt b/Documentation/power/basic-pm-debugging.txt
index b96098c..5f1f228 100644
--- a/Documentation/power/basic-pm-debugging.txt
+++ b/Documentation/power/basic-pm-debugging.txt
@@ -36,6 +36,13 @@ button to make the system resume).
If neither "platform" nor "shutdown" hibernation mode works, you will need to
identify what goes wrong.
+Besides, if all the modes described above work, "test_resume" mode can be used to
+verify if the snapshot data written to swap device can be successfully restored
+to memory:
+# echo test_resume > /sys/power/disk
+# echo disk > /sys/power/state
+If everything goes well, the system will resume back without BIOSes involved in.
+
a) Test modes of hibernation
To find out why hibernation fails on your system, you can use a special testing
--
2.7.4
next reply other threads:[~2016-08-11 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 12:18 Chen Yu [this message]
2016-08-12 6:22 ` [PATCH][RFC] Documentation/: update hibernation debug documentation Pavel Machek
2016-08-12 11:46 ` Chen, Yu C
2016-08-12 11:53 ` Rafael J. Wysocki
2016-08-12 11:55 ` Chen, Yu C
2016-08-12 13:31 ` Rafael J. Wysocki
2016-08-12 21:56 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1470917891-8386-1-git-send-email-yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).