From owner-freebsd-stable@FreeBSD.ORG Mon Aug 4 10:23:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1293B106566B for ; Mon, 4 Aug 2008 10:23:08 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id F10C28FC0A for ; Mon, 4 Aug 2008 10:23:07 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id B5BB81CC0B0; Mon, 4 Aug 2008 03:23:07 -0700 (PDT) Date: Mon, 4 Aug 2008 03:23:07 -0700 From: Jeremy Chadwick To: Martin Message-ID: <20080804102307.GA28928@eos.sc1.parodius.com> References: <20080801142005.473c17ca@zelda.local> <20080801154208.W6085@fledge.watson.org> <2a41acea0808010924u22603c61p10e47237fad5b6fb@mail.gmail.com> <20080802064727.042d5e3d@web.de> <2a41acea0808021034g588fdc77w50797f473e8809b0@mail.gmail.com> <20080804113448.0a4b3991@zelda.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080804113448.0a4b3991@zelda.local> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: jfv@freebsd.org, Robert Watson , freebsd-stable@freebsd.org, Jack Vogel Subject: Re: em(4) on FreeBSD is sometimes annoying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2008 10:23:08 -0000 On Mon, Aug 04, 2008 at 11:34:48AM +0200, Martin wrote: > On Sat, 2 Aug 2008 10:34:47 -0700 > "Jack Vogel" wrote: > > > Telling me what kind of NIC it is isn't going to help, 82573's are > > working the world over :) What exactly is your laptop, what model, > > is the NIC a LOM (on the motherboard) or some addin. > > Hi Jack, > > this is a Lenovo Thinkpad T60p model 2007-93G. It's the standard > built-in NIC by Lenovo on the mainboard. I also have a T60p (though a different model/type number). Note that the BIOSes for the T60p have historically documented numerous changes to how the NIC is initialised and "fiddled with", **especially** if PXE booting is enabled (regardless if a PXE boot itself is performed or not). My employer sent a company-wide message to all owners of the T60p asking that they upgrade their BIOS solely to address link negotiation failures occasionally seen when PXE booting. Meaning: I would not be surprised if this issue proved to be something specific to Lenovo laptops, possibly this model. When I return to work on Wednesday night, I'll try to reproduce what you see (we have Juniper, Cisco, Extreme, and Netgear switches there), then bring the laptop home and test against a D-Link switch, as well as my ProCurve. I can tell you that I have absolutely no problems under Windows Vista when pulling the CAT5 cable out and reinserting it; and yes, DHCP is used. (I do this literally on a nightly basis, which is how/why I'm so sure.) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |