From: Eckehardt Luhm <bselu@web.de>
To: andrewm@uow.edu.au, linux-kernel@vger.kernel.org
Subject: WOL problems with 3COM905C and suspend to disk
Date: Thu, 16 Feb 2006 14:44:06 +0100 [thread overview]
Message-ID: <503052906@web.de> (raw)
Hello,
I'm experiencing problems using Wake On LAN with the 3c59x-driver of kernel
2.6.11.
The driver is loaded correctly with enable_wol=1. When going to suspend with
issuing "echo disk > /sys/power/state" vortex_down() seems to be called (I
added some debug outputs there). That's fine, because of the function
acpi_set_WOL() being called preparing the NIC for WOL.
Unfortunately right before the PC eventually goes down, the vortex driver
seems to be opened again. Adding some printk's to the driver I was able to
observe that after vortex_down() is called, and right before the RAM image
is saved to disk, vortex_up() is called. That's bad, because that disables
WOL. Then the power goes off and it's not possible to wake the PC by WOL.
I can exclude all kinds of hardware problems, because I managed to get it
working using a workaround. I added a global variable "vortex_down_called"
which is 0 by default. In vortex_down() I set it to 1 once acpi_set_WOL()
is called. Inside vortex_up() I first query this variable. If it's 0 the
function is executed normally. When it's 1 I return immediately not
executing vortex_up().
With this workaround WOL works fine after the suspend, the PC awakes as
expected. Of course I have to reload the 3c59x module once the PC has
resumed. Actually I don't like that workaround. Can you tell me, who is
re-opening the driver once it has been closed for suspend? What can I do
to make WOL work correctly?
Best regards, Ecke
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
reply other threads:[~2006-02-16 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=503052906@web.de \
--to=bselu@web.de \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome