From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Very strange issues with ethernet wake on lan
Date: Mon, 17 Aug 2009 12:16:28 +0300 [thread overview]
Message-ID: <1250500588.4301.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1250394174.32268.13.camel@localhost.localdomain>
On Sun, 2009-08-16 at 06:42 +0300, Maxim Levitsky wrote:
> Hi,
>
> I have recently put back the davicom dm9009 ethernet card into my
> computer.
>
> Some long time ago, I have written its suspend/resume routines.
> Now I see that few things have changed, like I need to enable wake in
> sysfs or better patch the code to do so, some nice helpers like
> pci_prepare_to_sleep have arrived, etc.
>
>
> I narrowed the strange issue down to following situation:
>
> I reload dmfe.ko (and networkmanager is disabled)
> I don't ifup the device, thus pretty much no hardware initialization
> takes place (but this appears not to matter anyway)
>
> I then suspend the system, and WOL doesn't work (I have patched the
> driver to enable WOL automaticly)
>
> I then, suspend again. WOL works, and continues to work as long as I
> don't reload the driver. If I do, same situation repeats.
>
> Also, after a boot, WOL works, so a reload cycle triggers that issue.
>
> And most importantly, if I don't do a
>
> pci_set_power_state(pci_dev, pci_choose_state (pci_dev, state));
>
> in .suspend, then WOL always works.
>
> and I have even tried to set state manually to PCI_D3hot or PCI_D3cold,
>
> I also tried to use pci_save_state
>
>
> I also have 2 copies of this card, and both have this issue.
> I also tried 2 pci slots.
>
> Kernel is vanilla 2.6.31-rc5
Bisect reveals:
44e4e66eeae5338b3ca0b28f8352e60bf18d5ba8 is first bad commit
commit 44e4e66eeae5338b3ca0b28f8352e60bf18d5ba8
Author: Rafael J. Wysocki <rjw@sisk.pl>
Date: Mon Jul 7 03:32:52 2008 +0200
PCI: rework pci_set_power_state function to call platform first
Rework pci_set_power_state() so that the platform callback is
invoked before the native mechanism, if necessary. Also, make
the function check if the device is power manageable by the
platform before invoking the platform callback.
This may matter if the device dependent on additional power
resources controlled by the platform is being put into D0, in which
case those power resources must be turned on before we attempt to
handle the device itself.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@suse.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Note that probably this device has no acpi entries, because it is an
addon card, bios knows nothing about it
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-08-17 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 3:42 Very strange issues with ethernet wake on lan Maxim Levitsky
2009-08-17 9:16 ` Maxim Levitsky [this message]
2009-08-17 12:02 ` Rafael J. Wysocki
2009-08-17 18:30 ` Rafael J. Wysocki
2009-08-20 9:16 ` Maxim Levitsky
2009-09-29 20:28 ` Rafael J. Wysocki
2009-10-10 21:37 ` Maxim Levitsky
2009-10-10 21:45 ` 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=1250500588.4301.5.camel@localhost.localdomain \
--to=maximlevitsky@gmail.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).