From owner-freebsd-current@FreeBSD.ORG  Sun Jan  4 12:41:25 2004
Return-Path: <owner-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 BF22D16A4CE
	for <freebsd-current@FreeBSD.org>;
	Sun,  4 Jan 2004 12:41:25 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C394F43D1D
	for <freebsd-current@FreeBSD.org>;
	Sun,  4 Jan 2004 12:41:24 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i04KfE7E009622;
	Sun, 4 Jan 2004 12:41:19 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200401042041.i04KfE7E009622@gw.catspoiler.org>
Date: Sun, 4 Jan 2004 12:41:14 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: dejan.lesjak@ijs.si
In-Reply-To: <200401041115.29188.dejan.lesjak@ijs.si>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: ryans@gamersimpact.com
cc: silby@silby.com
cc: freebsd-current@FreeBSD.org
Subject: Re: 5.2-RC oerrs and collisions on dc0
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Sun, 04 Jan 2004 20:41:25 -0000

On  4 Jan, Dejan Lesjak wrote:
> On Sunday 04 of January 2004 09:59, Don Lewis wrote:
>> When errors occur in full duplex mode, you might want to print the value
>> of
>> 	CSR_READ_4(sc, DC_NETCFG)
>> to verify that the full duplex bit is actually set.
> 
> I put this right after
>                 if (txstat & DC_TXSTAT_ERRSUM) {
>                         ifp->if_oerrors++;
> 
> it gives me 0x338c2203 and DC_NETCFG_FULLDUPLEX is 0x00000200, so as I 
> understand full-duplex is set. Also none of previous two suggestions made 
> difference. I also found this documentation:
> ftp://download.intel.com/design/network/manuals/27807401.pdf
> if it helps.

Interesting, this card appears to use the PCS interface instead of MII
(bit 23 is set).  Also bit 28 is set.  The 21143 documentation says this
is unused, but my copy of the 21140A documentation says this bit must be
zero.