From owner-freebsd-current@FreeBSD.ORG Wed Jan 7 13:36:51 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 E91B016A4CE; Wed, 7 Jan 2004 13:36:51 -0800 (PST) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97DD543D45; Wed, 7 Jan 2004 13:36:45 -0800 (PST) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1AeLM4-0009oA-65; Wed, 07 Jan 2004 22:36:44 +0100 Received: from w by mail.evip.pl with local (Exim 4.22) id 1AeLM4-0009o4-39; Wed, 07 Jan 2004 22:36:44 +0100 Date: Wed, 7 Jan 2004 22:36:44 +0100 From: Wiktor Niesiobedzki To: Don Lewis Message-ID: <20040107213644.GD6151@mail.evip.pl> References: <200401071932.i07JWN7E017376@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401071932.i07JWN7E017376@gw.catspoiler.org> User-Agent: Mutt/1.4i Sender: Wiktor Niesiobedzki X-Mailman-Approved-At: Wed, 07 Jan 2004 21:02:54 -0800 cc: current@FreeBSD.org Subject: Re: Call for testers - dc ethernet driver patch 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: Wed, 07 Jan 2004 21:36:52 -0000 On Wed, Jan 07, 2004 at 11:32:23AM -0800, Don Lewis wrote: > The dc driver has been broken ever since it was converted to use busdma. > The symptoms are that it reports spurious output errors and collisions, > even when running in full-duplex mode. I believe the patch below fixes > the problem, but I do not have the appropriate hardware to test it. I > have had one gotten one report so far from someone who claims this patch > fixed the problems he was seeing. I'd appreciate further testing of > this patch, especially with as many of the chipsets supported by the > driver as possible so that I can commit this patch. Please mention the > type of hardware you are using (machine architecture and card probe > message) in your reports. This is somewhat time critical because I've > had users express interest in getting this into 5.2. I may confirm: i386 - dc0: <3Com OfficeConnect 10/100B> port 0xd400-0xd4ff mem 0xdffff800-0xdffffbff irq 5 at device 13.0 on pci0 Before - Coll=90%*Opkts Now - Coll=0 and Opkts=51426 Cheers and thanks, Wiktor Niesiobedzki