From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 04:03:36 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 261D916A4CE for ; Thu, 8 Jan 2004 04:03:36 -0800 (PST) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35D5743D5A for ; Thu, 8 Jan 2004 04:03:33 -0800 (PST) (envelope-from philip@nixsys.be) Received: from loge.nixsys.be (loge.nixsys.be [195.144.77.45]) by gateway.nixsys.be (Postfix) with ESMTP id 8705047 for ; Thu, 8 Jan 2004 13:03:27 +0100 (CET) Received: by loge.nixsys.be (Postfix, from userid 1001) id DE8EA2F; Thu, 8 Jan 2004 13:03:26 +0100 (CET) Date: Thu, 8 Jan 2004 13:03:26 +0100 From: Philip Paeps To: current@FreeBSD.org Message-ID: <20040108120326.GA22253@loge.nixsys.be> Mail-Followup-To: current@FreeBSD.org 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> X-Date-in-Rome: ante diem VI Idius Ianuarias MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Mutt: User-Agent: Mutt/1.5.5.1i 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: Thu, 08 Jan 2004 12:03:36 -0000 On 2004-01-07 11:32:23 (-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. Seems to work pretty well on my Alpha (PWS500a) dc0: port 0x9100-0x917f mem 0x81192000-0x8119207f irq 0 at device 3.0 on pci0 Still some collisions reported, eight in about ten minutes, not full duplex though, so that might be okay, but a great improvement over the many thousands of collisions it used to report. Cheers, - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. BOFH Excuse #335: the AA battery in the wallclock sends magnetic interference