From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@zip.com.au>,
kernel list <linux-kernel@vger.kernel.org>
Subject: [patch] suspend: update warnings
Date: Mon, 22 Aug 2005 10:15:28 +0200 [thread overview]
Message-ID: <20050822081528.GA4418@elf.ucw.cz> (raw)
Update suspend documentation. Warnings were a bit overstated, and did
not point out important stuff.
---
commit 790df7223ac29afec81e7201adc879973311f27e
tree 97fa2017f8f5aded0c44cfc75ba4903fbdb7f0a4
parent 63393fcbf056a6fd68142a49ed4e1258560dce2c
author <pavel@amd.(none)> Mon, 22 Aug 2005 10:13:51 +0200
committer <pavel@amd.(none)> Mon, 22 Aug 2005 10:13:51 +0200
Documentation/power/swsusp.txt | 60 ++++++++++++++++++++++++++++++++--------
Documentation/power/video.txt | 9 +++++-
2 files changed, 56 insertions(+), 13 deletions(-)
diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
--- a/Documentation/power/swsusp.txt
+++ b/Documentation/power/swsusp.txt
@@ -1,22 +1,20 @@
-From kernel/suspend.c:
+Some warnings, first.
* BIG FAT WARNING *********************************************************
*
- * If you have unsupported (*) devices using DMA...
- * ...say goodbye to your data.
- *
* If you touch anything on disk between suspend and resume...
* ...kiss your data goodbye.
*
- * If your disk driver does not support suspend... (IDE does)
- * ...you'd better find out how to get along
- * without your data.
- *
- * If you change kernel command line between suspend and resume...
- * ...prepare for nasty fsck or worse.
+ * If you do resume from initrd after your filesystems are mounted...
+ * ...bye bye root partition.
+ * [this is actually same case as above]
*
- * If you change your hardware while system is suspended...
- * ...well, it was not good idea.
+ * If you have unsupported (*) devices using DMA, you may have some
+ * problems. If your disk driver does not support suspend... (IDE does),
+ * it may cause some problems, too. If you change kernel command line
+ * between suspend and resume, it may do something wrong. If you change
+ * your hardware while system is suspended... well, it was not good idea;
+ * but it wil probably only crash.
*
* (*) suspend/resume support is needed to make it safe.
--
if you have sharp zaurus hardware you don't need... you know my address
next reply other threads:[~2005-08-22 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 8:15 Pavel Machek [this message]
2005-08-22 22:41 ` [patch] suspend: update warnings Jiri Slaby
2005-08-22 23:32 ` Nigel Cunningham
2005-08-23 12:50 ` Pavel Machek
2005-08-23 12:53 ` Nigel Cunningham
2005-08-23 12:58 ` Pavel Machek
2005-08-23 15:05 ` Dave Jones
2005-08-23 20:53 ` Nigel Cunningham
2005-08-24 1:15 ` Dave Jones
2005-08-23 12:57 ` Christoph Hellwig
2005-08-23 13:00 ` Pavel Machek
2005-08-23 13:02 ` Christoph Hellwig
2005-08-29 5:57 ` Stefan Seyfried
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=20050822081528.GA4418@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
/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