From owner-freebsd-stable@FreeBSD.ORG Wed Aug 13 19:10:39 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 42404106567D for ; Wed, 13 Aug 2008 19:10:39 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.231]) by mx1.freebsd.org (Postfix) with ESMTP id 002428FC13 for ; Wed, 13 Aug 2008 19:10:38 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so59466wra.27 for ; Wed, 13 Aug 2008 12:10:38 -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=fQ2Ne4q7e/GDdRjDRhXR0qa2horG4LJW21XrEJCx6QQ=; b=hNwu5c6bdMyCxeEgvdONeacmxL462h3H7DJz62W58N1auGjjlm1an0cv43+zw3TKl7 bQCm62iHIooZibRpAj4Lt8rZu6hWmS3x+8rx4AMB0JAnYUXAzJPDpbTk62lvoNkvRw25 tYgipTie6T9RHzun9lxCiAxFp+/zwqy31eDww= 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=FDZGPRBCIgB7+yDCUE3aU5K2bDvYA5y1BBkV3/Sh2sGcWD6xUc3TDF7NKfG/PjohTL zCw6u5/gb0Tz7F8JCEfCYfXwNxDL9j0p5uE7dCGKW1xwpJu6LT/JTKzGb57/s8WmdfP0 90qFvsDPJob4MQaSQQJpFbud8p65p1r1PgqwU= Received: by 10.90.31.8 with SMTP id e8mr267307age.1.1218654638068; Wed, 13 Aug 2008 12:10:38 -0700 (PDT) Received: by 10.100.43.1 with HTTP; Wed, 13 Aug 2008 12:10:37 -0700 (PDT) Message-ID: <2a41acea0808131210r6371b532i93f1ae6963d1f1b9@mail.gmail.com> Date: Wed, 13 Aug 2008 12:10:37 -0700 From: "Jack Vogel" To: "Markus Vervier" In-Reply-To: <2a41acea0808130822i5f336b1ci15099f27a3a7c13d@mail.gmail.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> <2a41acea0808110928h10d54441o7d49b11a60406934@mail.gmail.com> <48A0A1D9.8030601@vervier.info> <2a41acea0808111340o7b506804u9e4c95f1af22b95c@mail.gmail.com> <48A2B1CB.7060303@vervier.info> <2a41acea0808130822i5f336b1ci15099f27a3a7c13d@mail.gmail.com> Cc: 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: Wed, 13 Aug 2008 19:10:39 -0000 On Wed, Aug 13, 2008 at 8:22 AM, Jack Vogel wrote: > On Wed, Aug 13, 2008 at 3:04 AM, Markus Vervier wrote: >> Jack Vogel wrote: >>> >>> I didn't mean the NIC EEPROM, but the system BIOS, make sure you are >>> running the version that Jeremy said he was, if that matches you might go >>> look at settings in the BIOS that are about management. >>> >> I'm now running the latest BIOS for my X60 version 2.22 with the same >> results. Jeremy runs version 1.15 but on a T60. >>> >>> I thought you told us that when you had a back to back connection that it >>> worked, no?? >> >> Sorry, it does not work when having a b2b connection, never said that. But I >> noticed another thing: >> >> It is important that the device was up without a cable connected: >> >> 1. power off completely >> 2. boot freebsd without a cable connected >> 3. in a rootshell do ifconfig em0 up >> 4. connect the cable >> 5. no link > > Hmmm, well let me see if I can get ahold of an X60. > > Jack > Markus, I have reproduced the problem, you are correct. Thank you for persisting thru my doubts :) There is a flip side to the problem, once the interface is up and active, if you remove the cable it never shows inactive :( It must be some interrupt handling/media status issue, I'll be looking into a fix this afternoon. OH, I should note that as long as you put in a cable before you ifconfig up its fine so its not that hard to work around the issue. Stay tuned.... Jack