Project

General

Profile

Bug #25034

Fix Intel i350 WOL bug

Added by Andrew McCann over 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Alexander Motin
Category:
OS
Target version:
Seen in:
Sprint:
Severity:
New
Backlog Priority:
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Network i350 Controller (2 ports) running LCAP
Supermicro X10SRi-F with Intel E5-2603v3
64GB (4*16GB) Samsung ECC DDR4 2400MHz
LSI SAS 9201-16i
7/2 * RAIDZ3 - Hitachi/Toshiba 3TB
2*140GB HP SAS Drives (Boot)
Norco 4224 Case (120mm fans)

ChangeLog Required:
No

Description

Hi, been trying to work out my WOL issues, and think i found the related BSD fixes. Could be completely wrong, but thought i would raise it anyway :) Possibly related to ticket Bug #24465

Basically, if i shutdown via GUI, WOL does not work. If i shutdown via ipmi (forced) or power off device normally using GUI, then switch server power off till link lights drop and power up again, WOL works!

WOL EM
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208343

WOL IGB
https://svnweb.freebsd.org/base?view=revision&revision=312641

Thanks

Associated revisions

Revision 116d6e97 (diff)
Added by Dru Lavigne 11 months ago

Mention improvements to em(4).
Ticket: #25034

History

#1 Updated by Andrew McCann over 1 year ago

Sorry, this is the correct link revision for EM
https://svnweb.freebsd.org/base?view=revision&revision=311982

#2 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to Alexander Motin

#3 Updated by Alexander Motin over 1 year ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Nice to have

#4 Updated by Alexander Motin over 1 year ago

Have you tried it on the same configuration but without LACP?

#5 Updated by Andrew McCann over 1 year ago

Disabled lagg completly and still the same problem, it interesting I cant see WOL on the available options, that why i suspected a driver issue.

[root@freenas ~]# ifconfig
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether xx:xx:xx:xx:xx:xx
inet 192.168.1.218 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether xx:xx:xx:xx:xx:xx
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
[root@freenas ~]#

gb0: flags=8943&lt;UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500                                                  
options=2400b9&lt;RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6&gt;
ether xx:xx:xx:xx:xx:xx
nd6 options=9&lt;PERFORMNUD,IFDISABLED&gt;
media: Ethernet autoselect (1000baseT &lt;full-duplex&gt;)
status: active
igb1: flags=8943&lt;UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
options=2400b9&lt;RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6&gt;
ether xx:xx:xx:xx:xx:xx
nd6 options=9&lt;PERFORMNUD,IFDISABLED&gt;
media: Ethernet autoselect (1000baseT &lt;full-duplex&gt;)
status: active
lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; metric 0 mtu 16384
options=600003&lt;RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6&gt;
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21&lt;PERFORMNUD,AUTO_LINKLOCAL&gt;
groups: lo
lagg0: flags=8943&lt;UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
options=2400b9&lt;RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6&gt;
ether xx:xx:xx:xx:xx:xx
inet 192.168.1.218 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9&lt;PERFORMNUD,IFDISABLED&gt;
media: Ethernet autoselect
status: active
groups: lagg
laggproto lacp lagghash l2,l3,l4
laggport: igb0 flags=1c&lt;ACTIVE,COLLECTING,DISTRIBUTING&gt;
laggport: igb1 flags=1c&lt;ACTIVE,COLLECTING,DISTRIBUTING&gt;

#6 Updated by Andrew McCann about 1 year ago

Seems there are now commits to Freebsd 11 Stable, for the fixes, both for the igb(4) and em(4) drivers.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208343

#7 Updated by Dru Lavigne 11 months ago

  • Status changed from Screened to 46

Sasha: can you double-check to see if these need to be merged into 11.1 or if they are already in there?

#8 Updated by Alexander Motin 11 months ago

  • Status changed from 46 to 15

The patch from mention FreeBSD ticket is already in 11.1. Andrew, could you test it 11.1-RC1 or 11-nightly?

#9 Updated by Andrew McCann 11 months ago

Hi Alex

Tested on the nightly (FreeNAS-11-MASTER-201711140419) and can confirm WOL is now working correctly.

Thanks
Andrew

#10 Updated by Alexander Motin 11 months ago

  • Status changed from 15 to Ready For Release
  • Target version set to 11.1

#11 Updated by Dru Lavigne 11 months ago

  • Subject changed from Intel i350 WOL issues to Fix Intel i350 WOL bug

#12 Updated by Dru Lavigne 11 months ago

  • Target version changed from 11.1 to 11.1-RC2

#13 Updated by Nick Wolff 11 months ago

  • Needs QA changed from Yes to No

Removing needs QA as has been verified as pulled in from upstream and by creator of ticket as functional

#14 Updated by Dru Lavigne 11 months ago

  • Target version changed from 11.1-RC2 to 11.1-RC3

#15 Updated by Dru Lavigne 11 months ago

  • Status changed from Ready For Release to Resolved

Also available in: Atom PDF