From owner-freebsd-current@FreeBSD.ORG Thu Jun 8 21:31:09 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D865316ABAC for ; Thu, 8 Jun 2006 17:11:04 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAB6043D7B for ; Thu, 8 Jun 2006 17:11:03 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so371302wxd for ; Thu, 08 Jun 2006 10:11:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=S7lH1ETFoU6raN6aDQY2kBo7XZBFA8toxFO1R/JacGJFpDi2GUpRklJPDDE0c92NHPE7kgiMoVSyWDUYua1FOxnTKiIVYR1jgHebpr82qIBr8QXU1RsKhFAbATkpJGlQlLdpcpkVQrBIdbJVWPloDi6hFFQrvCmQsWzo4GwWxRs= Received: by 10.70.109.5 with SMTP id h5mr2288324wxc; Thu, 08 Jun 2006 10:11:02 -0700 (PDT) Received: by 10.70.36.8 with HTTP; Thu, 8 Jun 2006 10:11:02 -0700 (PDT) Message-ID: <47d0403c0606081011y5f610eb3h8eb8ac32f1a6bee0@mail.gmail.com> Date: Thu, 8 Jun 2006 17:11:02 +0000 From: "Ben Kaduk" To: current@freebsd.org In-Reply-To: <20060607195303.GA3225@roadrunner.q.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060607195303.GA3225@roadrunner.q.local> Cc: Subject: Re: [PATCH] Call for bfe(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2006 21:31:09 -0000 On 6/7/06, Ulrich Spoerlein wrote: > Hi, > > I investigated a bug/missing feature in the bfe(4) driver, which makes > it not see any LINK DOWN events unless you happen to invoke ifconfig. > > If you are running bfe hardware, *please* test the following (NO > PATCHING OR REBOOTING REQUIRED) > > 1. Plug in ethernet cable > 2. Watch dmesg/syslogd for the LINK UP message > 3. Remove the cable > 4. Do you see a LINK DOWN message? Does it appear after you issue > 'ifconfig'? > > Please run these simple steps and report back to me, if you get the LINK > DOWN message or not and which hardware you are running. For reference, > mine is a BCM4401, card=0x81271028 chip=0x440114e4 rev=0x01. > > If you want to give the patch a try, you are of course encouraged to do > so. > > Ulrich Spoerlein > -- > PGP Key ID: 20FEE9DD Encrypted mail welcome! > Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD > Which is worse: ignorance or apathy? > Don't know. Don't care. > > > Hi Ulrich, It appears that I have the same card as you, but I performed the simple test anyways (kernel recompile will have to wait until my ~5 hour computation finishes). The link up message appears automatically, but the link down message does not appear until I issue an ``ifconfig" command. pciconf -lv: bfe0@pci2:0:0: class=0x020000 card=0x81271028 chip=0x440114e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4401 10/100 Integrated Ethernet Controller' class = network subclass = ethernet I will hopefully give the patch a try in the next couple of days. -Ben Kaduk