From owner-freebsd-current@FreeBSD.ORG Sat Jan 3 20:14:56 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 6A50716A4CE for ; Sat, 3 Jan 2004 20:14:56 -0800 (PST) Received: from niobe.ijs.si (mail.ijs.si [193.2.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A366D43D6B for ; Sat, 3 Jan 2004 20:14:34 -0800 (PST) (envelope-from dejan.lesjak@ijs.si) Received: from localhost (localhost.ijs.si [127.0.0.1]) by niobe.ijs.si (Postfix) with ESMTP id 4B2421DDC0E; Sun, 4 Jan 2004 05:14:33 +0100 (CET) Received: from niobe.ijs.si ([193.2.4.66]) by localhost (niobe.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 84156-02; Sun, 4 Jan 2004 05:14:31 +0100 (CET) Received: from rincewind.ijs.si (rincewind.ijs.si [193.2.4.137]) by niobe.ijs.si (Postfix) with ESMTP id DEB801DDA1F; Sun, 4 Jan 2004 05:14:30 +0100 (CET) From: Dejan Lesjak To: Mike Silbersack Date: Sun, 4 Jan 2004 05:14:30 +0100 User-Agent: KMail/1.5.94 References: <20031228233331.1F3F05D04@ptavv.es.net> <200312302250.03256.dejan.lesjak@ijs.si> <20040103201927.G5165@odysseus.silby.com> In-Reply-To: <20040103201927.G5165@odysseus.silby.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200401040514.30273.dejan.lesjak@ijs.si> X-Virus-Scanned: by amavisd-new / Sophos+Sophie at ijs.si 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:14:56 -0000 On Sunday 04 of January 2004 03:23, Mike Silbersack wrote: > On Tue, 30 Dec 2003, Dejan Lesjak wrote: > > I'm glad to hear that reporting of errors might be false. So I setup some > > monitoring of ports on both ends of cable, put apache on server with dc > > card and made a cron job on another machine (on same switch) to fetch a > > file of around 100MB every 5 minutes from server. > > So things go thusly - on server side there is constant flow of output > > errors and collisions with a peak at reboot. Collisions amount about 10% > > of output errors, which about 0.1% of output traffic. On switch side > > there is only a peak of input errors at server reboot, then there are no > > more errors. I'm not entirely sure if I can make conclusions based on > > this, but this can probably be false alarm then. Tell me if there is > > something more that I can do to confirm that these are in fact false > > collisions and errors. Also if seing graphs would help, they are on > > http://niobe.ijs.si/ewok/ > > > > Thanks everybody for help, > > Dejan > > Hm, you may have a real problem. I see 0 output errors here, although my > collision count is constantly increasing. > > If you'd like to "fix" the false collisions, find the following line in > if_dc.c, and remove it: > > ifp->if_collisions += (txstat & DC_TXSTAT_COLLCNT) >> 3; > > I say "fix" because that count used to be accurate, we apparently broke > something somewhere else in the driver which is causing the false > collision reports. Of course, whatever is causing the false collisions > may be causing false errors on your card, so it's hard to tell. :) > > Good luck, > > Mike "Silby" Silbersack 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