From owner-freebsd-current@FreeBSD.ORG Fri Jun 9 00:31:16 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 5AA4F16A418 for ; Fri, 9 Jun 2006 00:31:16 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.67.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED26343D45 for ; Fri, 9 Jun 2006 00:31:15 +0000 (GMT) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 1D89233C03; Fri, 9 Jun 2006 02:31:14 +0200 (CEST) Date: Fri, 9 Jun 2006 02:31:14 +0200 From: Lars Engels To: current@freebsd.org Message-ID: <20060609003113.GD61348@e.0x20.net> References: <20060607195303.GA3225@roadrunner.q.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K/NRh952CO+2tg14" Content-Disposition: inline In-Reply-To: <20060607195303.GA3225@roadrunner.q.local> X-Editor: VIM - Vi IMproved 6.4 User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Fri, 09 Jun 2006 00:57:38 +0000 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: Fri, 09 Jun 2006 00:31:16 -0000 --K/NRh952CO+2tg14 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Ulrich, On Wed, Jun 07, 2006 at 09:53:03PM +0200, Ulrich Spoerlein wrote: > Hi, >=20 > 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. I do not have this problem with my bfe NIC and it always worked here. > If you are running bfe hardware, *please* test the following (NO > PATCHING OR REBOOTING REQUIRED) >=20 > 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'? Jun 9 01:49:11 bart kernel: bfe0: link state changed to DOWN Jun 9 01:49:14 bart kernel: bfe0: link state changed to UP > 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=3D0x81271028 chip=3D0x440114e4 rev=3D0x01. bfe0@pci2:5:0: class=3D0x020000 card=3D0x108217c0 chip=3D0x440114e4 rev=3D= 0x01 hdr=3D0x00 vendor =3D 'Broadcom Corporation' device =3D 'BCM4401 10/100 Integrated Ethernet Controller' So it is a different card but the same chip and revision. The system is a FreeBSD 7.0-CURRENT with sources from last weekend. I just applied your patch and it does still work for me, so if the patch wo= rks=20 for you, we can both be happy :) Lars --K/NRh952CO+2tg14 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEiMFRKc512sD3afgRAvphAJ0XyMBvjCTI/vP2ehlP/4JLSKEC8gCeJkTO GRWPjMS/7NZIvLTMQZQ/MNM= =zpH1 -----END PGP SIGNATURE----- --K/NRh952CO+2tg14--