netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kamil Iskra <kamil@iskra.name>
To: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: WoL stopped working after power off with 2.6.38 (e1000e specific?)
Date: Sat, 30 Apr 2011 00:45:19 -0500	[thread overview]
Message-ID: <20110430054519.GA9826@scooby.iskra.name> (raw)

[ Note: I'm not on these mailing lists, so be sure to Cc: me if you want
more info from me ]

After upgrading from kernel 2.6.37 to 2.6.38, Wake on LAN after shutdown
stopped working for me on both of my Thinkpad laptops.  Both systems use
the e1000e driver.  One (a T61) has an 82566MM NIC, the other (an X201) an
82577LM.  I'm running 64-bit Gentoo Linux with a custom compiled kernel.
The network driver is built into the kernel.

Wake on LAN still works after suspend (S3), but not after a complete
shutdown (with power supply connected).

I figured the updated e1000e driver in 2.6.38 was probably to blame,
however, after I copied the whole drivers/net/e1000e directory from the
2.6.37 over to the 2.6.38 tree and recompiled, the problem persisted, so I
don't know anymore.

I modified the system shutdown sequence to invoke ifconfig and ethtool
right before the final halt.  According to ifconfig, eth0 is down at that
point.  According to ethtool, WoL is configured correctly ("Wake-on: g").
There is, however, a difference in the output of ethtool between the two
kernel versions.  "Link detected:" shows "yes" with 2.6.37, but "no" with
2.6.38.

A workaround that I found to work was to invoke "ifconfig eth0 up" right
before the halt.

Any suggestions?  Is this new behavior expected or is it a bug?

Kamil

-- 
Kamil Iskra  kamil@iskra.name

             reply	other threads:[~2011-04-30  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30  5:45 Kamil Iskra [this message]
2011-05-02 22:02 ` [E1000-devel] WoL stopped working after power off with 2.6.38 (e1000e specific?) Allan, Bruce W
2011-05-02 22:07   ` Allan, Bruce W
2011-05-03  2:58   ` Kamil Iskra

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=20110430054519.GA9826@scooby.iskra.name \
    --to=kamil@iskra.name \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).