Skip to contentSkip to conversation

suspend: update documentation

PATCH In review Pavel Machek 3 participants 6 messages Jul 12, 2005 Suspend to RAM

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 suspend: update documentation

Update suspend documentation.

---
commit 8972d0ff145879e53416ac77c4cd096fd3cfe227 tree f901592e816f4cfae7383f443b21a13f67a644f8 parent a6500a8820a9b271105fe92e5d3013f7c2875b44 author <pavel@amd.(none)> Tue, 12 Jul 2005 11:04:31 +0200 committer <pavel@amd.(none)> Tue, 12 Jul 2005 11:04:31 +0200

 Documentation/power/swsusp.txt |    7 +++++++
 Documentation/power/video.txt  |    9 ++++++++-
 2 files changed, 15 insertions(+), 1 deletions(-)
Documentation/power/swsusp.txt +7 -0
@@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
 system is shut down or suspended. Additionally use the encrypted
 suspend image to prevent sensitive data from being stolen after
 resume.
+
+Q: Why we cannot suspend to a swap file?
+
+A: Because accessing swap file needs the filesystem mounted, and
+filesystem might do something wrong (like replaying the journal)
+during mount. [Probably could be solved by modifying every filesystem
+to support some kind of "really read-only!" option. Patches welcome.]
Documentation/power/video.txt +8 -1
@@ -46,6 +46,12 @@ There are a few types of systems where v
   POSTing bios works. Ole Rohne has patch to do just that at
   http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2.
 
+(8) on some systems, you can use the video_post utility mentioned here:
+  http://bugzilla.kernel.org/show_bug.cgi?id=3670. Do echo 3 > /sys/power/state
+  && /usr/sbin/video_post - which will initialize the display in console mode.
+  If  you are in X, you can switch to a virtual terminal and back to X using
+  CTRL+ALT+F1 - CTRL+ALT+F7 to get the display working in graphical mode again.
+
 Now, if you pass acpi_sleep=something, and it does not work with your
 bios, you'll get a hard crash during resume. Be careful. Also it is
 safest to do your experiments with plain old VGA console. The vesafb
@@ -64,7 +70,8 @@ Model                           hack (or
 ------------------------------------------------------------------------------
 Acer Aspire 1406LC		ole's late BIOS init (7), turn off DRI
 Acer TM 242FX			vbetool (6)
-Acer TM C300                    vga=normal (only suspend on console, not in X), vbetool (6)
+Acer TM C110			video_post (8)
+Acer TM C300                    vga=normal (only suspend on console, not in X), vbetool (6) or video_post (8)
 Acer TM 4052LCi		        s3_bios (2)
 Acer TM 636Lci			s3_bios vga=normal (2)
 Acer TM 650 (Radeon M7)		vga=normal plus boot-radeon (5) gets text console back
#1 lore raw

On Tue, 12 Jul 2005 11:05:10 +0200 Pavel Machek wrote:

| Update suspend documentation.
| 
| Signed-off-by: Pavel Machek <[email protected]>
| 
| ---
| 
| diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
| --- a/Documentation/power/swsusp.txt
| +++ b/Documentation/power/swsusp.txt
| @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
|  system is shut down or suspended. Additionally use the encrypted
|  suspend image to prevent sensitive data from being stolen after
|  resume.
| +
| +Q: Why we cannot suspend to a swap file?

Q: Why can't we suspend to a swap file?
or
Q: Why can we not suspend to a swap file?

| +
| +A: Because accessing swap file needs the filesystem mounted, and
| +filesystem might do something wrong (like replaying the journal)
| +during mount. [Probably could be solved by modifying every filesystem
| +to support some kind of "really read-only!" option. Patches welcome.]
| diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt
| --- a/Documentation/power/video.txt
| +++ b/Documentation/power/video.txt
| @@ -46,6 +46,12 @@ There are a few types of systems where v
|    POSTing bios works. Ole Rohne has patch to do just that at
|    http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2.
|  
| +(8) on some systems, you can use the video_post utility mentioned here:
| +  http://bugzilla.kernel.org/show_bug.cgi?id=3670. Do echo 3 > /sys/power/state

That attachment is weird for me. It downloads as "attachment.cgi", but
it's a tar.gz file. :( (using firefox if it matters)

| +  && /usr/sbin/video_post - which will initialize the display in console mode.
| +  If  you are in X, you can switch to a virtual terminal and back to X using
| +  CTRL+ALT+F1 - CTRL+ALT+F7 to get the display working in graphical mode again.

---
~Randy

#2 lore raw

Hi.

Quoted 22 lines · randy_dunlap

On Tue, 12 Jul 2005 11:05:10 +0200 Pavel Machek wrote:

| Update suspend documentation.
| 
| Signed-off-by: Pavel Machek <[email protected]>
| 
| ---
| 
| diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
| --- a/Documentation/power/swsusp.txt
| +++ b/Documentation/power/swsusp.txt
| @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
|  system is shut down or suspended. Additionally use the encrypted
|  suspend image to prevent sensitive data from being stolen after
|  resume.
| +
| +Q: Why we cannot suspend to a swap file?

Q: Why can't we suspend to a swap file?
or
Q: Why can we not suspend to a swap file?

Quoted 5 lines
| +
| +A: Because accessing swap file needs the filesystem mounted, and
| +filesystem might do something wrong (like replaying the journal)
| +during mount. [Probably could be solved by modifying every filesystem
| +to support some kind of "really read-only!" option. Patches welcome.]

This is wrong. Suspend2 has supported writing to a swap file for a long time (since 1.0), without requiring the filesystem to be mounted when resuming. We just need to store the bdev and block numbers in the image header.

Regards,

Nigel

Signature · 5 lines
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened. 
#3 lore raw

Hi!

Quoted 26 lines
Quoted 20 lines
| Update suspend documentation.
| 
| Signed-off-by: Pavel Machek <[email protected]>
| 
| ---
| 
| diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
| --- a/Documentation/power/swsusp.txt
| +++ b/Documentation/power/swsusp.txt
| @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
|  system is shut down or suspended. Additionally use the encrypted
|  suspend image to prevent sensitive data from being stolen after
|  resume.
| +
| +Q: Why we cannot suspend to a swap file?

Q: Why can't we suspend to a swap file?
or
Q: Why can we not suspend to a swap file?

Quoted 5 lines
| +
| +A: Because accessing swap file needs the filesystem mounted, and
| +filesystem might do something wrong (like replaying the journal)
| +during mount. [Probably could be solved by modifying every filesystem
| +to support some kind of "really read-only!" option. Patches welcome.]
Quoted 4 lines

This is wrong. Suspend2 has supported writing to a swap file for a long time (since 1.0), without requiring the filesystem to be mounted when resuming. We just need to store the bdev and block numbers in the image header.

Uh, and then you pass something like resume=/dev/hda5@BLOCKID on command line? Okay, that could work.

Does this look fair?

Q: Why can't we suspend to a swap file?

A: Because accessing swap file needs the filesystem mounted, and filesystem might do something wrong (like replaying the journal) during mount.

There are few ways to get that fixed:

1) Probably could be solved by modifying every filesystem to support some kind of "really read-only!" option. Patches welcome.

2) suspend2 gets around that by storing absolute positions in on-disk image, with resume parameter pointing directly to suspend header.

Pavel

Signature · 1 line
teflon -- maybe it is a trademark, but it should not be.
#4 lore raw

Hi.

Quoted 44 lines · Pavel Machek

Hi!

Quoted 26 lines
Quoted 20 lines
| Update suspend documentation.
| 
| Signed-off-by: Pavel Machek <[email protected]>
| 
| ---
| 
| diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
| --- a/Documentation/power/swsusp.txt
| +++ b/Documentation/power/swsusp.txt
| @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
|  system is shut down or suspended. Additionally use the encrypted
|  suspend image to prevent sensitive data from being stolen after
|  resume.
| +
| +Q: Why we cannot suspend to a swap file?

Q: Why can't we suspend to a swap file?
or
Q: Why can we not suspend to a swap file?

Quoted 5 lines
| +
| +A: Because accessing swap file needs the filesystem mounted, and
| +filesystem might do something wrong (like replaying the journal)
| +during mount. [Probably could be solved by modifying every filesystem
| +to support some kind of "really read-only!" option. Patches welcome.]
Quoted 4 lines

This is wrong. Suspend2 has supported writing to a swap file for a long time (since 1.0), without requiring the filesystem to be mounted when resuming. We just need to store the bdev and block numbers in the image header.

Uh, and then you pass something like resume=/dev/hda5@BLOCKID on command line? Okay, that could work.

Does this look fair?

Q: Why can't we suspend to a swap file?

A: Because accessing swap file needs the filesystem mounted, and filesystem might do something wrong (like replaying the journal) during mount.

Quoted 7 lines

There are few ways to get that fixed:

1) Probably could be solved by modifying every filesystem to support some kind of "really read-only!" option. Patches welcome.

2) suspend2 gets around that by storing absolute positions in on-disk image, with resume parameter pointing directly to suspend header.

And a block size. (It affects the interpretation of the block number).

Apart from that, yes.

Regards,

Nigel

Signature · 5 lines
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened. 
#5 lore raw
In reply to randy_dunlap

Hi!

Quoted 10 lines
| diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
| --- a/Documentation/power/swsusp.txt
| +++ b/Documentation/power/swsusp.txt
| @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
|  system is shut down or suspended. Additionally use the encrypted
|  suspend image to prevent sensitive data from being stolen after
|  resume.
| +
| +Q: Why we cannot suspend to a swap file?
Quoted 3 lines

Q: Why can't we suspend to a swap file?
or
Q: Why can we not suspend to a swap file?

Thanks, fixed.

Quoted 15 lines
| +
| +A: Because accessing swap file needs the filesystem mounted, and
| +filesystem might do something wrong (like replaying the journal)
| +during mount. [Probably could be solved by modifying every filesystem
| +to support some kind of "really read-only!" option. Patches welcome.]
| diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt
| --- a/Documentation/power/video.txt
| +++ b/Documentation/power/video.txt
| @@ -46,6 +46,12 @@ There are a few types of systems where v
|    POSTing bios works. Ole Rohne has patch to do just that at
|    http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2.
|  
| +(8) on some systems, you can use the video_post utility mentioned here:
| +  http://bugzilla.kernel.org/show_bug.cgi?id=3670. Do echo 3 > /sys/power/state
Quoted 2 lines

That attachment is weird for me. It downloads as "attachment.cgi", but
it's a tar.gz file. :( (using firefox if it matters)

I think I actually got that file from server somehow, but it was not exactly easy :-(.
Pavel

Signature · 1 line
teflon -- maybe it is a trademark, but it should not be.