From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux PM <linux-pm@osdl.org>
Subject: [PATCH] swsusp: documentation update
Date: Sun, 5 Feb 2006 09:03:48 +0100 [thread overview]
Message-ID: <200602050903.48678.rjw@sisk.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
Hi,
This patch updates the swsusp documentation to reflect the recent change
that prevented the kernel from setting to console loglevel to 10
unconditionally during suspend. It also removes one obsolete paragraph.
Please review.
Greetings,
Rafael
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Documentation/power/swsusp.txt | 15 ++++++++-------
1 files changed, 8 insertions(+), 7 deletions(-)
Index: linux-2.6.16-rc1-mm5/Documentation/power/swsusp.txt
===================================================================
--- linux-2.6.16-rc1-mm5.orig/Documentation/power/swsusp.txt 2006-02-03 21:26:42.000000000 +0100
+++ linux-2.6.16-rc1-mm5/Documentation/power/swsusp.txt 2006-02-05 08:49:07.000000000 +0100
@@ -33,12 +33,13 @@ echo N > /sys/power/image_size
before suspend (it is limited to 500 MB by default).
-Encrypted suspend image:
-------------------------
-If you want to store your suspend image encrypted with a temporary
-key to prevent data gathering after resume you must compile
-crypto and the aes algorithm into the kernel - modules won't work
-as they cannot be loaded at resume time.
+Kernel messages during suspend
+------------------------------
+If you want to see any kernel messages on the virtual terminal the kernel
+switches to during suspend, you have to set the kernel console loglevel to
+at least 4 (KERN_WARNING), for example by doing
+
+# echo 4 > /proc/sys/kernel/printk
Article about goals and implementation of Software Suspend for Linux
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2006-02-05 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 8:03 Rafael J. Wysocki [this message]
2006-02-05 8:18 ` [PATCH] swsusp: documentation update Rafael J. Wysocki
2006-02-05 11:16 ` 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=200602050903.48678.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@osdl.org \
--cc=pavel@suse.cz \
/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