From owner-freebsd-current@FreeBSD.ORG  Mon Dec 29 12:23:55 2003
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 2BB2C16A4CE
	for <freebsd-current@freebsd.org>;
	Mon, 29 Dec 2003 12:23:55 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id D2B7343D39
	for <freebsd-current@freebsd.org>;
	Mon, 29 Dec 2003 12:23:53 -0800 (PST)	(envelope-from silby@silby.com)
Received: (qmail 97684 invoked from network); 29 Dec 2003 20:23:53 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 29 Dec 2003 20:23:53 -0000
X-pair-Authenticated: 209.68.2.70
Date: Mon, 29 Dec 2003 14:23:51 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Ryan Sommers <ryans@gamersimpact.com>
Message-ID: <20031229140852.J62022@odysseus.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Mon, 29 Dec 2003 12:44:02 -0800
cc: Dejan Lesjak <dejan.lesjak@ijs.si>
cc: freebsd-current@freebsd.org
Subject: dc0 collisions in -current
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: Mon, 29 Dec 2003 20:23:55 -0000


I haven't read the thread in question through completely, but I just want
to make you guys aware that -current's if_dc has a bug where it will
report _false_ collisions on many network cards.

Example from one of my systems:

dc0    1500 <Link#2>      00:20:78:0f:a0:a6 10307782     0 15428017     0 827213
dc0    1500 10.1.1/24     10.1.1.6          10304908     - 15428012     -     -

However, I am not aware of it producing any output error messages, so that
may be a real problem.

Also, "dc0: TX underrun -- increasing TX threshold" is normal, you will
see that message a few times once you start putting the system under
network load until it finds a good TX threshold.  Nothing to worry about
there.

So, as I said, I did not read the entire thread, so I'm not sure if a real
problem is occuring for you guys or not; just make sure that you aren't
chasing a ghost.

Mike "Silby" Silbersack