From owner-freebsd-current@FreeBSD.ORG  Wed May 31 22:01:24 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-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 F198116B211
	for <freebsd-current@freebsd.org>; Wed, 31 May 2006 22:01:24 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
	[66.23.211.162])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1479243D67
	for <freebsd-current@freebsd.org>; Wed, 31 May 2006 22:01:22 +0000 (GMT)
	(envelope-from jhb@freebsd.org)
Received: from [131.106.61.215] (72-255-64-171.client.stsn.net [72.255.64.171])
	(authenticated bits=0)
	by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k4VM1BQK072517;
	Wed, 31 May 2006 18:01:20 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org, thierry@herbelot.com
Date: Wed, 31 May 2006 17:53:23 -0400
User-Agent: KMail/1.9.1
References: <200605241556.44483.jhb@freebsd.org>
	<200605251023.34963.thierry@herbelot.com>
	<200605271830.50724.thierry@herbelot.com>
In-Reply-To: <200605271830.50724.thierry@herbelot.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200605311753.23976.jhb@freebsd.org>
X-Virus-Scanned: ClamAV 0.87.1/1504/Wed May 31 15:59:14 2006 on
	server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx
Cc: 
Subject: Re: [PATCH] if_dc cleanups..
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2006 22:01:29 -0000

On Saturday 27 May 2006 12:30, Thierry Herbelot wrote:
> Le Thursday 25 May 2006 10:23, Thierry Herbelot a =E9crit :
>=20
> > my dc is still probed and detected with your patch :
> > dc0: <82c169 PNIC 10/100BaseTX> port 0x9400-0x94ff mem
> > 0xd8000000-0xd80000ff irq 19 at device 9.0 on pci0
> > dc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x9400
> > miibus0: <MII bus> on dc0
> > bmtphy0: <BCM5201 10/100baseTX PHY> on miibus0
> > bmtphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > dc0: bpf attached
> > dc0: Ethernet address: 00:02:e3:08:63:af
> > dc0: [MPSAFE]
> >
> > the same dc is currently used to update the -current sources over NFS,
> > without any visible side effects.
>=20
> one side effect seems to be more watchdog timeouts :
>=20
> dc0: watchdog timeout
> dc0: failed to force tx and rx to idle state
>=20
> on a macroscopic level, the NIC is still usable (enough to get a cvs upda=
te=20
of=20
> the full world from an NFS repository).

It shouldn't have affect the operation of the device at all.  Do the probe=
=20
messages in dmesg match the dmesg lines w/o the patch exactly?  Do you have=
=20
before and after dmesg's that I can compare?

=2D-=20
John Baldwin