From owner-freebsd-stable@FreeBSD.ORG Mon Aug 11 16:28:02 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 5EEA81065675 for ; Mon, 11 Aug 2008 16:28:02 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.238]) by mx1.freebsd.org (Postfix) with ESMTP id 133EA8FC12 for ; Mon, 11 Aug 2008 16:28:01 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so792790wra.27 for ; Mon, 11 Aug 2008 09:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=oqBFVm89W9mkSiMXpDAvbTAol1XI0pQYwavTYfeXLZw=; b=jEXrbr/XXaJnMV5rSTqpFcQ+FL7QiPdVM6+u2C0IhlrRLrs4CYT8IbBGxF/v9BjwwK 2PQYAIdwyvSk1DyGf8+eYnaZPs9VvLjQiq9gsdcFjt2I/wbtoDM4++qWKEgQAa2Uoeib 0snniB25y6uQbwXm+Op0Cd/G4Evhb5LRtVuGo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=vy93AVxx7Fus2K7+s9Rc0dXkNkb/bTzFO0mveRqBdnxAxAHAMK6Q4pVDADRGWqLuH8 ggLkDS1T9nApq4fzbV/jKfpadEzYF2aylDqr7NoaS5cbctz3Q2r1c2foF4H7Nty3ti10 QHJ2EWG+FdRP6z9qD1IYOvTebNJBlCmlQ2UJQ= Received: by 10.90.91.2 with SMTP id o2mr10799778agb.111.1218472081379; Mon, 11 Aug 2008 09:28:01 -0700 (PDT) Received: by 10.100.43.1 with HTTP; Mon, 11 Aug 2008 09:28:01 -0700 (PDT) Message-ID: <2a41acea0808110928h10d54441o7d49b11a60406934@mail.gmail.com> Date: Mon, 11 Aug 2008 09:28:01 -0700 From: "Jack Vogel" To: "Jeremy Chadwick" In-Reply-To: <20080811140249.GA27379@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <489C4129.4090303@vervier.info> <489C88DB.6030000@vervier.info> <2a41acea0808081131m1eddc4caib0963c8a5443afd2@mail.gmail.com> <200808110819.53914.josh@tcbug.org> <20080811140249.GA27379@eos.sc1.parodius.com> Cc: Josh Paetzel , Markus Vervier , freebsd-stable@freebsd.org 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, 11 Aug 2008 16:28:02 -0000 On Mon, Aug 11, 2008 at 7:02 AM, Jeremy Chadwick wrote: > On Mon, Aug 11, 2008 at 08:19:46AM +0000, Josh Paetzel wrote: >> On Friday 08 August 2008 06:31:24 pm Jack Vogel wrote: >> > OK, I just got access to a machine, am going to install and see if I >> > can repro this >> > this afternoon. >> > >> > Jack >> >> For what it's worth, I have a T60 that dual boots 6.3-R/amd64 and 7.0-R/i386 >> and neither install has this problem. I can cold boot it with the NIC >> unplugged, plug in a cable, I get a link light and ifconfig em0 goes to >> active, dhclient em0 gets an IP successfully. > > As promised, I tested said issue out on my T60p (widescreen) tonight, > using both FreeBSD 7.0-STABLE and 7.0-RELEASE. > > I wasn't able to reproduce the issue; so my experience was the same as > Josh. I can also boot it with the CAT5 inserted, dhclient fetch an IP, > no LED oddities -- then yank the cable (LED and link light go off), > re-insert the cable, and within a moment or so dhclient again gets an > IP. > > I'm left wondering if maybe there's an EEPROM setting that's doing this > (purely speculative on my part), or possibly some odd BIOS quirk. My > T60p (widescreen) is running BIOS 1.14. It's worth noting that the > non-widescreen T60p uses a different BIOS. Cool, it turned out that the laptop I was told I could use was an X61 and it had an ICH8 NIC rather than 82573 anyway, they were supposed to get me one today but given the two of you have already gone thru this verification I see little point in doing the same. Seems possibly a BIOS thing, if not that bad cable, bad link partner maybe?? Jack