From owner-freebsd-current@FreeBSD.ORG  Thu Aug 19 14:42:40 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 7603316A4CE
	for <freebsd-current@freebsd.org>;
	Thu, 19 Aug 2004 14:42:40 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 234F543D1F
	for <freebsd-current@freebsd.org>;
	Thu, 19 Aug 2004 14:42:40 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.11/8.12.11) id i7JEgYRX092681;
	Thu, 19 Aug 2004 09:42:34 -0500 (CDT)
	(envelope-from dan)
Date: Thu, 19 Aug 2004 09:42:33 -0500
From: Dan Nelson <dnelson@allantgroup.com>
To: Jeffrey Katcher <jmkatcher@yahoo.com>
Message-ID: <20040819144233.GA74594@dan.emsphone.com>
References: <20040818162215.30029.qmail@web41105.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040818162215.30029.qmail@web41105.mail.yahoo.com>
X-OS: FreeBSD 5.2-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
cc: freebsd-current@freebsd.org
Subject: Re: Lots of collisions on em0
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: Thu, 19 Aug 2004 14:42:40 -0000

In the last episode (Aug 18), Jeffrey Katcher said:
> My network performance is a little spotty under -current lately so I
> looked at netstat -i:
> 
> netstat -i
> Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
> em0       0 <Link#1>      00:0d:60:2d:b0:c2        0  5722        0     0 5803493
> em0       0 192.168.168   clio                  6445     -     5680     -     -
> lo0*      0 <Link#2>                               0     0        0     0     0
> lo0*      0 your-net      localhost                0     -        0     -     -
> 
> With only a short uptime, I'm seeing insane numbers of collisions on
> em0, which is connected via a known-good cable to a known-good switch
> which shows no collisions on any of its ports.  Is there something
> going on with the em driver?

Sounds like your netstat binary is out of sync with your kernel.  Ipkts
and Opkts for your two em0 lines should be almost the same, and you
can't have collisions with no Opkts.

-- 
	Dan Nelson
	dnelson@allantgroup.com