Date: Wed, 05 May 2010 23:19:25 +0200 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: em WOL_MCAST repowers machine after poweroff [Was: Re: em JumboFrame improovement and PCIe addon-card regression] Message-ID: <4BE1E0DD.6070107@omnilan.de> In-Reply-To: <m2u2a41acea1004271458k7a43aa6bo858f229158ef3b7c@mail.gmail.com> References: <4BC82B80.3070108@omnilan.de> <20100416092803.GA17526@icarus.home.lan> <4BC82FF7.1030700@omnilan.de> <201004160822.09359.jhb@freebsd.org> <p2i2a41acea1004160829i53efa312k3ebec61cc2d9d251@mail.gmail.com> <u2s179b97fb1004160832u69175c8bi1c5a069cf872ef5b@mail.gmail.com> <4BC8A76A.6000107@omnilan.de> <s2q2a41acea1004161302k9e1261adx45efb4c9b0eebabd@mail.gmail.com> <4BC8CB9E.8060802@omnilan.de> <4BD75D2E.50302@omnilan.de> <m2u2a41acea1004271458k7a43aa6bo858f229158ef3b7c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9CBEA88FF2495A0EE6372B5E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Jack Vogel schrieb am 27.04.2010 23:58 (localtime): > Thanks Harald, >=20 > Have already been made aware of this, its due to the broadcast WOL bein= g=20 > enabled, I will be > fixing the problem shortly. Sorry for the inconvenience. Hello Jack, I saw your RELENG_8 change and recompiled one kernel today. It seems=20 that you only disabled WOL_*CAST for 7.0.5 adapters. Here's one=20 S3200SHLX board, which has two onboard nics (em0 with WOL_*CAST disabled = and em1 with WOL_* enabled): em0: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x30e0-0x30ff mem = 0xe1b00000-0xe1b1ffff,0xe1b20000-0xe1b20fff irq 20 at device 25.0 on pci0= em0: Using MSI interrupt em0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 15= 00 options=3D219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL= _MAGIC> em1: <Intel(R) PRO/1000 Legacy Network Connection 1.0.1> port=20 0x1000-0x103f mem 0xe1920000-0xe193ffff,0xe1900000-0xe191ffff irq 18 at=20 device 2.0 on pci4 em1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu=20 1500=20 options=3D389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAS= T,WOL_MCAST,WOL_MAGIC> I set this options manually on another box and with these em1 settings=20 the machine powers up immediately. But I have a much more severe problem: I disabled WOL_MCAST with ifconfig for one of my cold-standby machines.=20 But the machine doesn't wake up any more, even if I can see the WOL=20 packets arriving at the NIC (LED blinks). Since the machine also doesn't power up on WOL when shutted down via=20 ESXi I thought that was an issue with BIOS49, which I recently upgraded=20 to. I filed an intel reseller case -> status still in progress. Is it possible that the new code also broke intentionally WOL events? Thanks, -Harry --------------enig9CBEA88FF2495A0EE6372B5E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkvh4O8ACgkQLDqVQ9VXb8jkogCghNOs2zmxTpGcpjEKgYz0RHYR ffoAoJVSAQDhBLHUqZeK9bnTfTty/2gc =xj7c -----END PGP SIGNATURE----- --------------enig9CBEA88FF2495A0EE6372B5E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BE1E0DD.6070107>