----- Original Message -----
> From: John <da_audioph...@yahoo.com>
> To: "Ronciak, John" <john.ronc...@intel.com>; "Kirsher, Jeffrey T"
> <jeffrey.t.kirs...@intel.com>; "Brandeburg, Jesse"
> <jesse.brandeb...@intel.com>; "Allan, Bruce W" <bruce.w.al...@intel.com>;
> "Wyborny, Carolyn" <carolyn.wybo...@intel.com>; "Skidmore, Donald C"
> <donald.c.skidm...@intel.com>; "Rose, Gregory V" <gregory.v.r...@intel.com>;
> "Duyck, Alexander H" <alexander.h.du...@intel.com>; "Williams, Mitch A"
> <mitch.a.willi...@intel.com>
> Cc: "e1000-devel@lists.sourceforge.net" <e1000-devel@lists.sourceforge.net>
> Sent: Wednesday, March 5, 2014 2:57 PM
> Subject: Re: [BUG] e1000e: box will not stay off after a shutdown if WOL is
> enabled in the BIOS
>>> This is very odd. I booted into Windows to verify what settings it
>>> uses for this NIC relating to WOL. What I found:
>>> [x] Wake on Magic Packet
>>> [x] Wake on Pattern Match
>>> [x] Wake of Magic Packet from power off state
>>>
>>> I shutdown from Windows and again, it went down and did not wake up.
> I
>>> booted into Linux. I verified the exact same output from `ethtool
>>> eno1` as I posted above. I then issued a `shutdown -h now` and the
> box
>>> went down and stayed down. I woke it up with a `wol
> xx:xx:xx:xx:xx:xx`
>>> and then shut it down again. It stayed off this time. I repeated 10
>>> times and found that 2 our of the 10 times, it woke back up. Can
>>> anyone explain to me what is going on with this and do you believe
> that
>>> it is related to the Linux kernel driver for this NIC?
>>
>> I don't think so as the filter would be programmed to the HW from the
> driver
>> settings the same way each time. Could it be that when the system woke up
> that
>> there was a packet received from the network that caused this to happen?
> Is
>> this on a completely isolated network or is there lots of traffic on it?
>
>
> It is a home LAN of only a few machines. If I pull the network cable, then
> shutdown from the local machine, the box will go down, and then wake up again
> all by itself suggesting that it isn't spurious network traffic causing it.
> What I can't seem to get past is that if I boot the box to windows, and
> shutdown from there, I do not see this problem. If I boot the box to Linux,
> I
> do see the problem. Very difficult to troubleshoot.
>
On version 3.16.1 currently and am still experiencing this issue. Just
wondering if anyone has a suggestion beyond what has been made already. What I
can't seems to reconcile, is that shutting the box down from Windows, allows it
to go down and stay down. Shutting it down from Linux does not.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
