From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 00:59:39 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 1737316A4CE for ; Sun, 4 Jan 2004 00:59:39 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52C9B43D46 for ; Sun, 4 Jan 2004 00:59:37 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i048xR7E008500; Sun, 4 Jan 2004 00:59:32 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401040859.i048xR7E008500@gw.catspoiler.org> Date: Sun, 4 Jan 2004 00:59:27 -0800 (PST) From: Don Lewis To: dejan.lesjak@ijs.si In-Reply-To: <200401040717.42334.dejan.lesjak@ijs.si> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: ryans@gamersimpact.com cc: silby@silby.com 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 08:59:39 -0000 On 4 Jan, Dejan Lesjak wrote: > On Sunday 04 of January 2004 06:33, Don Lewis wrote: >> On 4 Jan, 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. >> >> The driver might be less verbose if you added some braces here. > > Hm.. Yes I did that, however I was writing mail relying on memory which seems > to have failed me. When errors occur in full duplex mode, you might want to print the value of CSR_READ_4(sc, DC_NETCFG) to verify that the full duplex bit is actually set.