From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Suspend, followed by immediate resume
Date: Sat, 3 May 2008 14:50:19 +0200 [thread overview]
Message-ID: <200805031450.19960.rjw@sisk.pl> (raw)
In-Reply-To: <200805031432.12250.rjw@sisk.pl>
On Saturday, 3 of May 2008, Rafael J. Wysocki wrote:
> On Saturday, 3 of May 2008, Jay Cliburn wrote:
> > On Sat, 3 May 2008 01:49:44 +0200
> > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > > On Friday, 2 of May 2008, Jay Cliburn wrote:
> > [...]
> > > > I poked around in BIOS and changed the behavior somewhat. There's a
> > > > BIOS setting called "Suspend Mode" with three options:
> > > >
> > > > S1 (POS) only
> > > > S3 only
> > > > Auto
> > > >
> > > > When set to "S3 only" or "Auto," the machine spontaneously resumes
> > > > following a suspend. When set to "S1 (POS) only" the machine stays
> > > > asleep.
> > > >
> > > > What is "POS" an acronym for?
> > >
> > > No idea.
> >
> > Wikipedia to the rescue. http://en.wikipedia.org/wiki/Acpi
> >
> > S1 == POS == Power On Standby
> >
> > I don't think I want to use this mode. The cpu fan runs continuously at
> > max while suspended and the system won't resume; I have to whack it
> > with the reset button to get it going again (with a reboot).
>
> That's bad.
>
> > > > Does it make sense to leave the thing set to "S1 only?"
> > >
> > > I guess it does. Still, can you please post a boot log with it set
> > > this way?
> >
> > Okay, it's attached.
>
> Well, it says all ACPI sleep states are supported.
>
> > BTW, I'm still using the modified version of acpi_pm_enter().
>
> That shouldn't matter a lot, I think you can remove the comment.
BTW, have you tested it with init=/bin/bash already?
Rafael
next prev parent reply other threads:[~2008-05-03 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 2:44 Suspend, followed by immediate resume Jay Cliburn
2008-05-02 15:00 ` Alan Stern
2008-05-02 16:39 ` Jay Cliburn
2008-05-02 16:47 ` Alan Stern
2008-05-02 16:49 ` Rafael J. Wysocki
2008-05-02 16:57 ` Jay Cliburn
2008-05-02 16:59 ` Rafael J. Wysocki
2008-05-02 17:29 ` Jay Cliburn
2008-05-02 17:41 ` Rafael J. Wysocki
2008-05-02 18:10 ` Jay Cliburn
2008-05-02 23:49 ` Rafael J. Wysocki
2008-05-03 2:05 ` Jay Cliburn
2008-05-03 12:32 ` Rafael J. Wysocki
2008-05-03 12:50 ` Rafael J. Wysocki [this message]
2008-05-03 12:58 ` Jay Cliburn
2008-05-03 13:09 ` Rafael J. Wysocki
2008-05-03 13:35 ` Jay Cliburn
2008-05-03 22:48 ` Rafael J. Wysocki
2008-05-14 19:19 ` Pavel Machek
2008-05-14 14:43 ` Pavel Machek
2008-05-14 14:42 ` Pavel Machek
2008-05-15 2:04 ` Zhang Rui
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=200805031450.19960.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jacliburn@bellsouth.net \
--cc=linux-pm@lists.linux-foundation.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