From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: mochel@digitalimplant.org, akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: -mm swsusp: do not default to platform/firmware
Date: Thu, 29 Jul 2004 01:43:52 +0200 [thread overview]
Message-ID: <20040728234352.GA14319@elf.ucw.cz> (raw)
In-Reply-To: <20040728233929.GD16494@elf.ucw.cz>
Hi!
> > > -mm swsusp now defaults to platform/firmware suspend... That's
> > > certainly unexpected, changes behaviour from previous version, and
> > > only works on one of three machines I have here. I'd like the default
> > > to be changed back.
> >
> > You overestimate my knowledge of suspend stuff. AFAICT the current -mm
> > default is to enter ACPI sleep state via the BIOS rather than via Linux's
> > ACPI driver. Correct?
>
> Its actually bit more complex. There are 3 methods:
>
> shutdown: save state in linux, then tell bios to powerdown
>
> platform: save state in linux, then tell bios to powerdown and blink
> "suspended led"
>
> firmware: tell bios to save state itself
>
> "platform" is actually right thing to do, but "shutdown" is most
> reliable.
...could you apply this? I hope it is accurate.
Pavel
--- clean/Documentation/power/swsusp.txt 2004-06-22 12:35:44.000000000 +0200
+++ linux/Documentation/power/swsusp.txt 2004-07-29 01:42:29.000000000 +0200
@@ -199,3 +202,30 @@
should be sent to the mailing list available through the suspend2
website, and not to the Linux Kernel Mailing List. We are working
toward merging suspend2 into the mainline kernel.
+
+Q: Kernel thread must voluntarily freeze itself (call 'refrigerator'). But
+I did found some kernel threads don't do it, and they don't freeze, and
+so the system can't sleep. Is this a known behavior?
+
+A: All such kernel threads need to be fixed, one by one. Select place
+where it is safe to be frozen (no kernel semaphores should be held at
+that point and it must be safe to sleep there), and add:
+
+ if (current->flags & PF_FREEZE)
+ refrigerator(PF_FREEZE);
+
+Q: What is the difference between between "platform", "shutdown" and
+"firmware" in /sys/power/disk?
+
+A:
+
+shutdown: save state in linux, then tell bios to powerdown
+
+platform: save state in linux, then tell bios to powerdown and blink
+ "suspended led"
+
+firmware: tell bios to save state itself [needs BIOS-specific suspend
+ partition, and has very little to do with swsusp]
+
+"platform" is actually right thing to do, but "shutdown" is most
+reliable.
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-07-28 23:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 22:24 Pavel Machek
2004-07-28 23:14 ` Andrew Morton
2004-07-28 23:39 ` Pavel Machek
2004-07-28 23:43 ` Pavel Machek [this message]
2004-07-29 0:30 ` Nigel Cunningham
2004-07-29 7:39 ` Pavel Machek
2004-07-29 7:52 ` Nigel Cunningham
2004-08-02 6:15 ` Patrick Mochel
2004-08-02 15:30 ` Kevin Fenzi
2004-08-03 11:28 ` Karol Kozimor
2004-08-09 19:44 ` Pavel Machek
2004-08-08 17:13 ` Pavel Machek
2004-07-29 5:19 Li, Shaohua
2004-07-29 7:38 ` Pavel Machek
2004-07-29 8:03 ` Nigel Cunningham
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=20040728234352.GA14319@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.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
all inboxes | Powered by JetHome®