netdev - Re: bnx2 driver can't enable/disable wake-on-lan on HP DL585 G2 onboard NICs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 6 Oct 2008 21:36:54 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"'Tim Mann'" <mann@...are.com>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: bnx2 driver can't enable/disable wake-on-lan on HP DL585 G2
 onboard NICs


Tim Mann wrote:

>
> Here's the deal.  The HP DL585 G2 has an onboard dual-port
> NIC based on
> the bcm5706.  Both ports support wake-on-lan, but WOL works
> if and only
> if you enable it using an option in the HP BIOS setup screens.  If you
> disable it from there, ethtool still thinks WOL is supported and that
> it's enabled by default, but the machine won't wake.  Conversely (and
> this part surprises me more), if you enable WOL from the BIOS setup
> screen, the machine always wakes on a WOL magic packet *even* if you
> try to disable WOL using ethtool.  Again ethtool thinks that WOL is
> supported and that it's enabled by default, and it thinks that it can
> disable WOL, but disabling it through ethtool has no effect -- the
> machine wakes anyway.

It sounds like an extra reset to the NIC is happening on this machine
during shutdown or suspend.  When that happens, it would wipe out the
WoL setting done by the driver.  I'll see if we have this DL585 to
try it out here.

>
> I don't have this problem with other NICs that use the bnx2
> driver.  In
> particular, I just retested one that I have in a box in my office, and
> the bnx2 driver can both enable and disable WOL on that NIC fine.
>
> So far I've tried this only with a bnx2 driver that advertises itself
> as 1.6.9 with release date December 8, 2007.  I could try with a newer
> one, but I looked at the diffs between 1.6.9 and 1.8.0 and I
> didn't see
> anything that looks like it should affect this.  Let me know if I
> should try it anyway, though.
>
> In case it helps, here's lspci output from the HP box with
> the misbehaving NIC:
>
> [root@...121 ~]# lspci -s 41:01.0 -v
> 41:01.0 Ethernet controller: Broadcom Corporation NetXtreme
> II 5706 Gigabit Ethernet (rev 02)
>         Subsystem: Hewlett-Packard Company Unknown device 1709
>         Flags: bus master, 66MHz, medium devsel, latency 120, IRQ 23
>         Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
>         [virtual] Expansion ROM at 88200000 [disabled] [size=2K]
>         Capabilities: [40] PCI-X non-bridge device
>         Capabilities: [48] Power Management version 2
>         Capabilities: [50] Vital Product Data
> [root@...121 ~]# lspci -s 41:01.0 -v -n
> 41:01.0 0200: 14e4:164a (rev 02)
>         Subsystem: 103c:1709
>         Flags: bus master, 66MHz, medium devsel, latency 120, IRQ 23
>         Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
>         [virtual] Expansion ROM at 88200000 [disabled] [size=2K]
>         Capabilities: [40] PCI-X non-bridge device
>         Capabilities: [48] Power Management version 2
>         Capabilities: [50] Vital Product Data

This is unrelated to WoL, but why is MSI capability missing on the
HP machine?

>
> Here's output from my test machine:
>
> [root@...pet ~]# lspci -s 41:04.0 -v
> 41:04.0 Ethernet controller: Broadcom Corporation NetXtreme
> II 5706 Gigabit Ethernet (rev 02)
>         Subsystem: Hewlett-Packard Company Unknown device 3101
>         Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
>         Memory at f0000000 (64-bit, non-prefetchable) [size=32M]
>         [virtual] Expansion ROM at 88000000 [disabled] [size=64K]
>         Capabilities: [40] PCI-X non-bridge device
>         Capabilities: [48] Power Management version 2
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts:
> 64bit+ Queue=0/0 Enable-
>
> [root@...pet ~]# lspci -s 41:04.0 -v -n
> 41:04.0 0200: 14e4:164a (rev 02)
>         Subsystem: 103c:3101
>         Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
>         Memory at f0000000 (64-bit, non-prefetchable) [size=32M]
>         [virtual] Expansion ROM at 88000000 [disabled] [size=64K]
>         Capabilities: [40] PCI-X non-bridge device
>         Capabilities: [48] Power Management version 2
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts:
> 64bit+ Queue=0/0 Enable
>
>
> --
> Tim Mann  work: mann@...are.com  home: tim@...-mann.org
>           http://www.vmware.com  http://tim-mann.org
>
>

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html