From owner-freebsd-current@FreeBSD.ORG  Mon Sep  1 15:16:59 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 EDC8A16A4BF
	for <freebsd-current@freebsd.org>;
	Mon,  1 Sep 2003 15:16:59 -0700 (PDT)
Received: from mps4.plala.or.jp (c147060.vh.plala.or.jp [210.150.147.60])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 86C4043FDF
	for <freebsd-current@freebsd.org>;
	Mon,  1 Sep 2003 15:16:58 -0700 (PDT)
	(envelope-from s-hrgsh@lapis.plala.or.jp)
Received: from hrgsh.homeip.net ([219.164.118.76]) by mps4.plala.or.jp
          with SMTP
          id <20030901221657.XIXU5316.mps4.plala.or.jp@hrgsh.homeip.net>
          for <freebsd-current@freebsd.org>; Tue, 2 Sep 2003 07:16:57 +0900
Date: Tue, 2 Sep 2003 07:16:57 +0900
From: Seishi Hiragushi <s-hrgsh@lapis.plala.or.jp>
To: freebsd-current@freebsd.org
Message-Id: <20030902071657.1e94e2b4.s-hrgsh@lapis.plala.or.jp>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386-portbld-freebsd5.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: current: network collition increase
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, 01 Sep 2003 22:17:00 -0000

Hi.

I noticed that network collition increase, in log of 7/26.
Such still a state continues.
What became like this owing to?

5.1-CURRENT-20030720 (daily run 7/26):
Network interface status:
Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
dc0    1500 <Link#1>      00:90:cc:a2:59:56   383420    27   441061     0 260568
dc0    1500 192.168.200   *****************   374698     -   431325     -     -
dc1    1500 <Link#2>      00:c0:ca:10:91:89   190866     0   136617  4124 70128

5.1-CURRENT-20030713 (daily run 7/17):
Network interface status:
Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
dc0    1500 <Link#1>      00:90:cc:a2:59:56    56144     3    64299     0     0
dc0    1500 192.168.200   *****************    27732     -    23965     -     -
dc1    1500 <Link#2>      00:c0:ca:10:91:89    63447     0    46153     0    54

dc0: <Intel 21143 10/100BaseTX> port 0xa000-0xa07f mem 0xe5800000-0xe580007f irq 4 at device 10.0 on pci0
dc0: Ethernet address: 00:c0:ca:10:91:8c
miibus0: <MII bus> on dc0
dcphy0: <Intel 21143 NWAY media interface> on miibus0
dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc1: <Intel 21143 10/100BaseTX> port 0x9400-0x947f mem 0xe4000000-0xe400007f irq 3 at device 13.0 on pci0
dc1: Ethernet address: 00:c0:ca:10:91:89
miibus1: <MII bus> on dc1
dcphy1: <Intel 21143 NWAY media interface> on miibus1
dcphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.200.1 netmask 0xffffff00 broadcast 192.168.200.255
        inet6 fe80::2c0:caff:fe10:918c%dc0 prefixlen 64 scopeid 0x1
        ether 00:c0:ca:10:91:8c
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::2c0:caff:fe10:9189%dc1 prefixlen 64 scopeid 0x2
        ether 00:c0:ca:10:91:89
        media: Ethernet autoselect (10baseT/UTP)
        status: active