From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Michael Frank <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Still problems with ACPI sleep state
Date: Fri, 25 Jun 2004 23:30:35 -0700 (PDT) [thread overview]
Message-ID: <20040625232835.R6228@root.org> (raw)
In-Reply-To: <opr96uc8fj4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
[context recovered]
On Sat, 26 Jun 2004, Michael Frank wrote:
> On Fri, 25 Jun 2004 21:15:21 -0700 (PDT), Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org> wrote:
> > On Fri, 25 Jun 2004, Herman Sheremetyev wrote:
> >> Try booting with acpi_sleep=s3_bios, I had the same problem on my Asus
> >> M6N and that made the LCD come back on after an S3 resume.
> >>
> >> -Herman
> >
> > Could someone familiar with Linux let me know what s3_bios does
> > differently from a normal S3?
> >
> > -Nate
>
> The suspend is performed in the BIOS without OS interaction.
>
> BIOS grabs CPU/its state, suspends devices, saves state, powers down
> and on powerup restores state, resumes devices, releases its state/CPU.
>
> (more or less)
>
> In short, BIOS does all the work. Used to be like that before ACPI.
> And few systems do it now like that...
I could use a bit more technical response. For instance, are SLP_TYP_A/B
written to a different register? If so, which? Does the system
transition to legacy mode (disabling ACPI), trigger APM suspend, then
re-enable ACPI on resume? What caveats are there?
-Nate
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-06-26 6:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 13:47 Still problems with ACPI sleep state Lars Amsel
[not found] ` <200406251547.21050.mailinglisten-Ztphx+FISXizQB+pC5nmwQ@public.gmane.org>
2004-06-25 14:12 ` Herman Sheremetyev
[not found] ` <1088172763.1918.1.camel-O4LVqDAXoJg@public.gmane.org>
2004-06-26 4:15 ` Nate Lawson
[not found] ` <opr96uc8fj4evsfm@smtp.pacific.net.th>
[not found] ` <opr96uc8fj4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-26 6:30 ` Nate Lawson [this message]
[not found] ` <20040625232835.R6228-Y6VGUYTwhu0@public.gmane.org>
2004-06-26 10:26 ` Michael Frank
2004-06-26 14:55 ` Stefan Seyfried
[not found] ` <20040626145551.GA2146-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-06-29 21:31 ` Pavel Machek
[not found] ` <20040625211440.P5510-Y6VGUYTwhu0@public.gmane.org>
2004-06-26 13:00 ` Matthew Garrett
[not found] ` <1088254830.4302.1.camel-myFlNLNQP+Q@public.gmane.org>
2004-06-26 19:03 ` Nate Lawson
[not found] ` <20040626120209.Y12968-Y6VGUYTwhu0@public.gmane.org>
2004-06-29 21:33 ` Pavel Machek
[not found] ` <20040629213316.GN698-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-07-01 19:42 ` Nate Lawson
[not found] ` <20040701123732.C48321-Y6VGUYTwhu0@public.gmane.org>
2004-07-02 11:29 ` Matthew Garrett
2004-07-02 12:48 ` Pavel Machek
2004-06-25 21:13 ` 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=20040625232835.R6228@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.