From owner-freebsd-current@FreeBSD.ORG  Fri Nov 14 23:14:40 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 0AE8816A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 14 Nov 2003 23:14:40 -0800 (PST)
Received: from mail3.dslextreme.com (mail3.dslextreme.com [66.51.199.73])
	by mx1.FreeBSD.org (Postfix) with SMTP id 46A6B43F3F
	for <freebsd-current@freebsd.org>;
	Fri, 14 Nov 2003 23:14:39 -0800 (PST)	(envelope-from jos@catnook.com)
Received: (qmail 17752 invoked from network); 15 Nov 2003 07:14:38 -0000
Received: from unknown (HELO w250.z064001178.sjc-ca.dsl.cnc.net)
	(66.218.45.239)
	by 192.168.8.73 with SMTP; Sat, 15 Nov 2003 07:14:38 +0000
Received: (qmail 46088 invoked by uid 1000); 15 Nov 2003 07:14:58 -0000
Date: Fri, 14 Nov 2003 23:14:36 -0800
From: Jos Backus <jos@catnook.com>
To: freebsd-current@freebsd.org
Message-ID: <20031115071458.GA29973@lizzy.catnook.com>
Mail-Followup-To: freebsd-current@freebsd.org
References: <20031115164720.I13393@hewey.af.speednet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031115164720.I13393@hewey.af.speednet.com.au>
User-Agent: Mutt/1.5.5.1i
Subject: Re: dc still reporting collisions
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: jos@catnook.com
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: Sat, 15 Nov 2003 07:14:40 -0000

On Sat, Nov 15, 2003 at 04:52:14PM +1000, Andy Farkas wrote:
> The dc(4) driver is still reporting collisions on 100 Mbit full-duplex
> links:
[snip]
> > netstat -i
> Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
> dc0    1500 <Link#1>      00:00:e8:89:b9:66    26463     0    26737 13253 225301

Fwiw, I'm seeing the same with tx(4):

lizzy:~% ifconfig tx0
tx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255
        inet 10.0.0.10 netmask 0xffffffff broadcast 10.0.0.10
        ether 00:e0:29:09:e4:1a
        media: Ethernet autoselect (10baseT/UTP)
        status: active
lizzy:~% netstat -i
Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
tx0    1500 <Link#1>      00:e0:29:09:e4:1a   154423     1   118093     0   253
tx0    1500 10/24         lizzy               159162     -   122841     -     -
tx0    1500 10.0.0.10/32  lizzy-proxy             28     -       28     -     -
lo0   16384 <Link#2>                            5347     0     5347     0     0
lo0   16384 your-net      localhost              442     -      442     -     -
lizzy:~% 

It's gotten so bad that I can no longer transfer files from a Windows system
to this FreeBSD system (both are on the same 10BaseT hub). I only rarely used
to see collisions before, and filetransfers have always worked just fine. Last
time I know for sure this worked was October 17th.

-- 
Jos Backus                       _/  _/_/_/      Sunnyvale, CA
                                _/  _/   _/
                               _/  _/_/_/
                          _/  _/  _/    _/
jos at catnook.com        _/_/   _/_/_/          require 'std/disclaimer'