From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Len Brown <lenb@kernel.org>
Subject: Re: PME# for add-on cards
Date: Wed, 26 Aug 2009 15:50:00 +0300 [thread overview]
Message-ID: <1251291000.1791.7.camel@maxim-laptop> (raw)
In-Reply-To: <200908240112.39424.rjw@sisk.pl>
On Mon, 2009-08-24 at 01:12 +0200, Rafael J. Wysocki wrote:
> Hi,
>
> Recently we've had a bug report indicating that WoL doesn't work with e100,
> although the driver does everything needed to support it. Apparently, the user
> had to echo PCI0 to /proc/acpi/wakeup to make it work.
>
> After some debugging it turned out that PCI0 is the PCI host bridge
> (no-bus:pci0000:00), so apparently echoing PCI0 to /proc/acpi/wakeup causes
> a wake-up GPE to be set up for the host bridge which triggers wake-up once
> eth0 signals PME#.
>
> So, it looks like we need to set up wake-up GPE for a host bridge for PME#
> from add-on cards to work, at least on this particular box.
>
> First, I wonder if that's the case in general (anybody knows?). Second, if
> that is the case, would it be a good idea to set up the host bridge wake-up GPE
> by default?
>
> Rafael
>
This is very known problem (at least for me)
On my desktop, /proc/acpi/wakeup controls all the wakeup sources, and if
disabled, nether addon cards (ethernet) nor internal devices
(usb,ethernet) will wake up the system.
I think that proc/acpi/wakeup should be synced with power/wakeup
attribute.
Also, I would be really happy to see bogus (empty) power/wakeup
attributes be gone.
Also, something is broken in regards to PME from addon cards:
http://www.spinics.net/lists/netdev/msg104460.html
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-08-26 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 23:12 PME# for add-on cards Rafael J. Wysocki
2009-08-24 0:44 ` [linux-pm] " Alan Stern
[not found] ` <20090824094429.GB1134@srcf.ucam.org>
2009-08-24 18:39 ` Rafael J. Wysocki
2009-08-24 19:12 ` Jesse Barnes
2009-08-25 23:42 ` Henrique de Moraes Holschuh
2009-08-27 16:13 ` Jesse Barnes
2009-08-27 19:41 ` Rafael J. Wysocki
2009-08-26 12:50 ` Maxim Levitsky [this message]
2009-08-26 21:26 ` Rafael J. Wysocki
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=1251291000.1791.7.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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