public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Manpreet Singh <Manpreet.Singh-IrU4XInhIXM@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3 resume and Wake events
Date: Fri, 2 Apr 2004 12:31:50 +0200	[thread overview]
Message-ID: <20040402103150.GA677@elf.ucw.cz> (raw)
In-Reply-To: <EB6B0A91B0F6AC44842492A8F6852CDE11AAB6-jfDmLf0o5iKyvBr3IBtpkhUaVx6/PbGo@public.gmane.org>

Hi!

> I am attempting to resume from S3 using a magic packet from an NIC. The NIC
> asserts the PME# and the status bit gets set in the I/O controller, but it
> turns out that the ACPI suspend code in the kernel disables *all* GPEs before
> sleeping and so I can't wake the system up after it goes to sleep.
> 
> Tracing through the code (on the 2.6.4 stock kernel), at one point, the
> function acpi_enter_sleep_state() calls acpi_disable_non_wakeup_gpes() which
> disables all GPEs, even the ones that are potentially the wake-up events like
> the PME_EN bit.

This needs some work. API should be invented to tell the kernel what
GPEs may wake us up.
									Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

      parent reply	other threads:[~2004-04-02 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26  1:34 S3 resume and Wake events Manpreet Singh
     [not found] ` <EB6B0A91B0F6AC44842492A8F6852CDE11AAB6-jfDmLf0o5iKyvBr3IBtpkhUaVx6/PbGo@public.gmane.org>
2004-04-02 10:31   ` Pavel Machek [this message]

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=20040402103150.GA677@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=Manpreet.Singh-IrU4XInhIXM@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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