From: Li Shaohua <shaohua.li@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Nate Lawson <nate@root.org>,
Nigel Cunningham <ncunningham@linuxmail.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Machines self-power-up with 2.6.9-rc3 (evo N620c, ASUS, ...)
Date: Fri, 22 Oct 2004 08:35:52 +0800 [thread overview]
Message-ID: <1098405352.28250.2.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20041021103729.GA1088@elf.ucw.cz>
On Thu, 2004-10-21 at 18:37, Pavel Machek wrote:
> Hi!
>
> > > > :-). Well for some other people it powers up when they unplug AC
> > > > power, and *that* is nasty. I'd like my machine to stay powered down
> > > > when I tell it so.
> > >
> > > This is likely a similar GPE problem. The GPE for the EC fires even
> > > in
> > > S5. I think the EC GPE should be disabled in the suspend method.
> > It could be the wakeup GPE issue, but must note Pavel's system suffer
> > the problem even with acpi=off. Could you please try boot your system
> > with acpi=off, and then reboot with acpi=off, what's the result? I
> > expected the wakeup GPE is disabled by the BIOS in this case.
> > Anyway, the DSDT can tell us the wakeup GPE info.
>
> You want me to boot with acpi=off twice and see if machine powers down
> okay in second case?
Yes, indeed.
>
> Compressed DSDT is attached.
The dmesg shows your system can be waked up by Lid from S4 but not S5.
But there is another device (looks like the LPC bridge) can wakeup your
system from S5.
Thanks,
Shaohua
next prev parent reply other threads:[~2004-10-22 0:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 19:15 Pavel Machek
2004-10-20 22:15 ` [ACPI] " Hiroshi 2 Itoh
2004-10-20 22:59 ` Pavel Machek
2004-10-20 22:31 ` Nigel Cunningham
2004-10-20 22:56 ` Pavel Machek
2004-10-21 0:03 ` Nate Lawson
2004-10-21 1:53 ` Li Shaohua
2004-10-21 10:37 ` Pavel Machek
2004-10-22 0:35 ` Li Shaohua [this message]
2004-10-22 7:53 ` Pavel Machek
2004-10-21 10:19 ` Pavel Machek
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=1098405352.28250.2.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nate@root.org \
--cc=ncunningham@linuxmail.org \
--cc=pavel@ucw.cz \
/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®