I believe this is normal behavior. Please check the systems WoL settings. It's probably set up to wake on any traffic and not set to wake on just "magic packets" (the WoL specific packets). On WoL enabled ports the MAC stays active looking for packets that are filtered looking to match one of its programmed filters. Comparing the behavior to what happens in Windows in the case probably won't match up. As I said, please the WoL setting in the system to see what it is looking for to wake up on.
Thanks. Cheers, John > -----Original Message----- > From: John [mailto:da_audioph...@yahoo.com] > Sent: Wednesday, February 26, 2014 3:23 PM > To: Kirsher, Jeffrey T; Brandeburg, Jesse; Allan, Bruce W; Wyborny, > Carolyn; Skidmore, Donald C; Rose, Gregory V; Duyck, Alexander H; > Ronciak, John; Williams, Mitch A > Cc: da_audioph...@yahoo.com; e1000-devel@lists.sourceforge.net > Subject: [BUG] e1000e: box will not stay off after a shutdown if WOL is > enabled in the BIOS > > Bug: Machine will shutdown cleanly but only stay down for ~5 sec is WOL > is enabled in the BIOS. This only happens when shutting down from > Linux. Shutting down from Windows 7 causes the expected behavior. > > Details: In order to support WOL, my Asus H87I-Plus requires an option > set in the BIOS (Onboard>APM>Power on by PCIE). When I have this > enabled, I can indeed start the machine using the wol magic packet, but > there is an undesired side-effect: when I shutdown the machine, it > stays shut off for about 5 sec and then turns back on all by itself. > This happens with or with a patch cable connected. If I disable the > option in the BIOS, this does not happen... but I am unable to use wol. > > I put Windows 7 on a spare HDD and can verify that if I shutdown from > Windows, the box stays off so this would appear to be a Linux-related > issue. I am making an assumption that it is related to the ethernet > driver and thus my post here. Please cc me on any replies to the list > as I am not subscribed. > > Distro: Arch Linux x86_64 > Kernel version tried: 3.10.32, 3.12.9, 3.13.5, or 3.14-rc4 > Motherboard: Asus H87I-Plus (BIOS 1005) > Processor: Intel i3-4130T > > # lscpi -v > > 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection > I217-V (rev 05) > Subsystem: ASUSTeK Computer Inc. Device 859f > Flags: bus master, fast devsel, latency 0, IRQ 45 > Memory at f7c00000 (32-bit, non-prefetchable) [size=128K] > Memory at f7c3d000 (32-bit, non-prefetchable) [size=4K] > I/O ports at f080 [disabled] [size=32] > Capabilities: [c8] Power Management version 2 > Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Capabilities: [e0] PCI Advanced Features > Kernel driver in use: e1000e > Kernel modules: e1000e > > % dmesg -t | grep -i e1000 > efi: mem48: type=7, attr=0xf, range=[0x00000000becca000- > 0x00000000bece1000) (0MB) > efi: mem49: type=4, attr=0xf, range=[0x00000000bece1000- > 0x00000000bed17000) (0MB) > efi: mem73: type=4, attr=0xf, range=[0x00000000bf136000- > 0x00000000bf1e1000) (0MB) > efi: mem74: type=7, attr=0xf, range=[0x00000000bf1e1000- > 0x00000000bf203000) (0MB) > e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k > e1000e: Copyright(c) 1999 - 2013 Intel Corporation. > e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to > dynamic conservative mode e1000e 0000:00:19.0: irq 45 for MSI/MSI-X > e1000e 0000:00:19.0 eth0: registered PHC clock e1000e 0000:00:19.0 > eth0: (PCI Express:2.5GT/s:Width x1) ac:22:0b:4d:bf:a8 e1000e > 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection e1000e > 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF e1000e > 0000:00:19.0: irq 45 for MSI/MSI-X e1000e 0000:00:19.0: irq 45 for > MSI/MSI-X > e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx > > % dmesg -t | grep -i 'error\|warn' > ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND > (20131115/psargs-359) ACPI Error: Method parse/execution failed > [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880119db67a8), AE_NOT_FOUND > (20131115/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, > AE_NOT_FOUND (20131115/psargs-359) ACPI Error: Method parse/execution > failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880119db67a8), > AE_NOT_FOUND (20131115/psparse-536) ACPI Warning: 0x0000000000001828- > 0x000000000000182f SystemIO conflicts with Region \PMIO 1 > (20131115/utaddress-251) ACPI Warning: 0x0000000000001c30- > 0x0000000000001c3f SystemIO conflicts with Region \GPRL 1 > (20131115/utaddress-251) ACPI Warning: 0x0000000000001c30- > 0x0000000000001c3f SystemIO conflicts with Region \GPR_ 2 > (20131115/utaddress-251) ACPI Warning: 0x0000000000001c00- > 0x0000000000001c2f SystemIO conflicts with Region \GPRL 1 > (20131115/utaddress-251) ACPI Warning: 0x0000000000001c00- > 0x0000000000001c2f SystemIO conflicts with Region \GPR_ 2 > (20131115/utaddress-251) ACPI Warning: 0x000000000000f040- > 0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI > 1 (20131115/utaddress-251) ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ 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
