From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 1 17:08:17 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C7B61065678 for ; Tue, 1 Jun 2010 17:08:17 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) by mx1.freebsd.org (Postfix) with ESMTP id 1062C8FC0C for ; Tue, 1 Jun 2010 17:08:16 +0000 (UTC) Received: from [192.168.2.161] (soundwave.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.161]) by relay.admin.pitbpa0.priv.collaborativefusion.com with esmtp; Tue, 01 Jun 2010 12:58:13 -0400 id 00017018.000000004C053C25.00008761 From: "Brian A. Seklecki" To: freebsd-hardware Organization: Collaborative Fusion, Inc. Date: Tue, 01 Jun 2010 12:58:13 -0400 Message-ID: <1275411493.30057.42.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=_blackout-34657-1275411493-0001-2" X-Mailer: Evolution 2.30.1.2 (2.30.1.2-6.fc13) Subject: em(4) duplex problems with 82541EI on RELENG_8, -CURRENT on PowerEdge 1850 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2010 17:08:17 -0000 This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_blackout-34657-1275411493-0001-2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable All: Has anyone upgraded their PowerEdge 1850s to 8.0-PL or=20 RELENG_8 -stable? We're seeing problems where 7.2-PL and 6.3-PL were not affected on the same hardware. The problem is that forcing the duplex 100/full on both=20 sides no longer functions. Configuration: =20 - A variety of Cisco L2/L3 switches over the last decade: -- 2848G-L3 -- 2950 -- 2960s -- 3550-12Ts -- 3550XLs -- Duplex forced 100/full on Cisco side - FreeBSD/amd64 RELENG_8 or 9-CURRENT with duplex forced '100baseTX mediaopt full-duplex', - This configuration has worked since FreeBSD 5.4 =20 When connected to PowerEdge 1850r1/r2, with the onboard Intel=20 82541EI, the parenthesis show an actual media speed/duplex of: media: Ethernet 100baseTX (100baseTX ) The same configuration using a Dell-sold Intel dual port 82546EB, in the same system, on the same switch, works fine. ----------------- ifconfig(8): ----------------- em3: flags=3D8843 metric 0 mtu 1500 options=3D9b ether 00:13:72:4f:70:81 inet 192.168.97.20 netmask 0xffffff80 broadcast 192.168.97.127 media: Ethernet 100baseTX (100baseTX ) status: active ----------------- em0: flags=3D8843 metric 0 mtu 1500> options=3D9b ether 00:04:23:c8:fe:ac media: Ethernet 100baseTX status: active ----------------- ----------------- pciconf(8): ----------------- em3@pci0:7:8:0: class=3D0x020000 card=3D0x016d1028 chip=3D0x10768086=20 rev=3D0x05 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Gigabit Ethernet Controller (82541EI)' class =3D network subclass =3D ethernet em0@pci0:3:11:0: class=3D0x020000 card=3D0x10128086 chip=3D0x10108086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' class =3D network subclass =3D ethernet ----------------- rc.conf(5) for shits & giggles: ifconfig_em0=3D"inet X netmask Y media 100baseTX mediaopt full-duplex" ifconfig_em3=3D"inet Z netmask F media 100baseTX mediaopt full-duplex" -------- Example IOS switch config: interface FastEthernet0/39 description I hate Dell switchport access vlan 100 switchport mode access speed 100 duplex full spanning-tree portfast end -------- I've been clearing interface counters on the switch side, but I'll send 'netstat -i', 'show interface counters', and 'sudo sysctl -w dev.em.3.stats=3D1' ASAP to illustrate connectivity errors soon. Are we being punished for patronizing Dell? Is it possible that ifconfig(8) output has simply changed? Are the values in the parenthesis on the right the Ethernet auto-sense desired values where as outside the parenthesis the current active values? In 6.3/7.2, once you forced a speed/duplex, the values in parenthesis went away entirely.=20 The only way I've been able to make that happen is to #define in src/sys/dev/e1000/if_em.h: #define DO_AUTO_NEG 0 /* * This parameter control whether or not the driver will wait for * autonegotiation to complete. * 1 - Wait for autonegotiation to complete * 0 - Don't wait for autonegotiation to complete */ Also seems odd that some ICs are affected but not others. Its also possible that my problems are pf(4) + setfib(8) related and I that this is a separate issue. --=20 Brian A. Seklecki Collaborative Fusion, Inc. --=_blackout-34657-1275411493-0001-2 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: 7bit Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEABECAAYFAkwFPCUACgkQCne6BNDQ+R/zRgCfWyRF/pQztfPwyZvyNgwjxgLG ATQAn3Mr+4RLf5MH5jom83SqBggkOjHO =FlA/ -----END PGP SIGNATURE----- --=_blackout-34657-1275411493-0001-2--