From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 13:11:06 2004 Return-Path: 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 43D8D16A4CE for ; Thu, 19 Aug 2004 13:11:06 +0000 (GMT) Received: from smtp02.net-yan.com (smtp02.hgcbroadband.com [210.0.255.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3E8743D4C for ; Thu, 19 Aug 2004 13:11:04 +0000 (GMT) (envelope-from sam.wun@tech-21.com.hk) Received: (qmail 45340 invoked from network); 19 Aug 2004 13:11:02 -0000 Received: from unknown (HELO [192.168.4.129]) (samwun@hgcbroadband.com@[221.127.107.239]) (envelope-sender ) by localhost (qmail-ldap-1.03) with SMTP for ; 19 Aug 2004 13:11:02 -0000 Message-ID: <4124A5E0.4030103@tech-21.com.hk> Date: Thu, 19 Aug 2004 21:06:40 +0800 From: sam User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeffrey Katcher References: <20040818162215.30029.qmail@web41105.mail.yahoo.com> In-Reply-To: <20040818162215.30029.qmail@web41105.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Aug 2004 13:11:06 -0000 Jeffrey Katcher wrote: >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 00:0d:60:2d:b0:c2 0 5722 0 0 >5803493 >em0 0 192.168.168 clio 6445 - 5680 - - >lo0* 0 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? > >Thanks, > > > The vr0 driver is not working again. The system can detect the link to vr0 is on and off, but failed pinging. It has a error message saying Watchdog on vr0 timeout. sam