From owner-freebsd-current@FreeBSD.ORG Sat Jan 3 20:32:18 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 C661016A4CE for ; Sat, 3 Jan 2004 20:32:18 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A432443D66 for ; Sat, 3 Jan 2004 20:32:16 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 55487 invoked from network); 4 Jan 2004 04:32:15 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 4 Jan 2004 04:32:15 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sat, 3 Jan 2004 22:32:13 -0600 (CST) From: Mike Silbersack To: Dejan Lesjak In-Reply-To: <200401040514.30273.dejan.lesjak@ijs.si> Message-ID: <20040103222844.H561@odysseus.silby.com> References: <20031228233331.1F3F05D04@ptavv.es.net> <200312302250.03256.dejan.lesjak@ijs.si> <200401040514.30273.dejan.lesjak@ijs.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sat, 03 Jan 2004 21:35:51 -0800 cc: Ryan Sommers 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, 04 Jan 2004 04:32:18 -0000 On Sun, 4 Jan 2004, Dejan Lesjak wrote: > Hello again, > With this line commented out, I still get both errors and collisions, twice as > much collisions as errors. On another occasion, I also added two printf lines > in here: > if (txstat & DC_TXSTAT_EXCESSCOLL) > ifp->if_collisions++; > printf("EXCESSCOLL\n"); > if (txstat & DC_TXSTAT_LATECOLL) > ifp->if_collisions++; > printf("LATECOLL\n"); > and I constantly get both of those, so this would be where counters go up if > this helps in any way. > > Dejan It certainly looks like you're experiencing a real problem then. If fiddling with the duplex settings hasn't fixed it and you've replaced the cable, then I would guess that we may have a driver problem. You may wish to try one of the following: 1) Replace the card with a different dc-supported card and see if the problem resolves itself. 2) Stick one of those cheap 5-port switches between the card and the switch you're currently attaching to. I'm going to be out of town for the next few days, so I'll be unable to help you debug further. If you can try those two tests and find out the results, perhaps someone else can help you poke at the MII driver and see if something is broken for your specific card. Mike "Silby" Silbersack