From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: Nigel Cunningham
<ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Machines self-power-up with 2.6.9-rc3 (evo N620c, ASUS, ...)
Date: Wed, 20 Oct 2004 17:03:04 -0700 [thread overview]
Message-ID: <4176FCB8.3060103@root.org> (raw)
In-Reply-To: <20041020225639.GD29863-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
Pavel Machek wrote:
>>>I'm seeing bad problem with N620c notebook (and have reports of more
>>>machines behaving like this, for example ASUS L8400C.) If I shutdown
>>>machine with lid closed, opening lid will power the machine up. Ouch.
>>>2.6.7 behaves okay.
>>
>>:> Some people would love to have the machine power up when they open
>>the lid! Wish my XE3 would do that!
This problem sounds like a wake GPE is enabled for the lid switch and
that it has a _PRW that indicates it can wake the system from S5. If
this is the case, just disabled the GPE.
> :-). 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.
--
Nate
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-21 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 19:15 Machines self-power-up with 2.6.9-rc3 (evo N620c, ASUS, ...) Pavel Machek
[not found] ` <20041020191531.GC21315-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-20 22:15 ` Hiroshi 2 Itoh
[not found] ` <OF014FB65F.1C41FFC8-ON49256F33.007639BA-49256F33.0079C800-JE5g2YyFxFHQT0dZR+AlfA@public.gmane.org>
2004-10-20 22:59 ` Pavel Machek
2004-10-20 22:31 ` [ACPI] " Nigel Cunningham
[not found] ` <1098311478.4989.100.camel-r49W/1Cwd2ff0s6lnCXPXw0QcLn3kwYh@public.gmane.org>
2004-10-20 22:56 ` Pavel Machek
[not found] ` <20041020225639.GD29863-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-21 0:03 ` Nate Lawson [this message]
[not found] ` <4176FCB8.3060103-Y6VGUYTwhu0@public.gmane.org>
2004-10-21 1:53 ` Li Shaohua
[not found] ` <1098323602.6132.51.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2004-10-21 10:37 ` Pavel Machek
[not found] ` <20041021103729.GA1088-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-22 0:35 ` Li Shaohua
[not found] ` <1098405352.28250.2.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
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=4176FCB8.3060103@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox