From owner-freebsd-current@FreeBSD.ORG Sun Dec 28 15:33:35 2003 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 B3D6016A4CE for ; Sun, 28 Dec 2003 15:33:35 -0800 (PST) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB79943D2D for ; Sun, 28 Dec 2003 15:33:32 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sun, 28 Dec 2003 15:33:30 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 1F3F05D04; Sun, 28 Dec 2003 15:33:31 -0800 (PST) To: Dejan Lesjak In-Reply-To: Message from Dejan Lesjak <200312280049.50629.dejan.lesjak@ijs.si> Date: Sun, 28 Dec 2003 15:33:31 -0800 From: "Kevin Oberman" Message-Id: <20031228233331.1F3F05D04@ptavv.es.net> cc: freebsd-current@freebsd.org Subject: Re: 5.2-RC oerrs and collisions on dc0 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: Sun, 28 Dec 2003 23:33:35 -0000 > From: Dejan Lesjak > Date: Sun, 28 Dec 2003 00:49:50 +0100 > Sender: owner-freebsd-current@freebsd.org > > > --Boundary-00=_eqh7/a7oNAgo+1o > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > Hello, > > I tried 5.2-RC2 on alpha and netstat -i keeps showing oerrs and collisions > on dc card (DEC DE500-BA): > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Coll > nge0* 1500 00:04:5a:71:d2:e0 0 0 0 0 > 0 > dc0 1500 00:00:f8:10:52:47 1478 0 737 335 > 5695 > dc0 1500 193.2.4 ewok 1103 - 733 - > - > lo0 16384 14 0 14 0 > 0 > lo0 16384 your-net localhost 0 - 0 - This looks very much like an auto-negotiation problem. Can you check ifconfig dc0? To have collisions, it must be running half-duplex. (By definition collision detection is disabled in FDX.) The additional errors further support this. The other question is what the other end of this link sees. Is it running full or half duplex? If full duplex, is it seeing input errors? If the far end is running FDX, can you set this end explicitly to FDX? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634