Date: Thu, 8 Jan 2004 13:03:26 +0100 From: Philip Paeps <philip+freebsd@paeps.cx> To: current@FreeBSD.org Subject: Re: Call for testers - dc ethernet driver patch Message-ID: <20040108120326.GA22253@loge.nixsys.be> In-Reply-To: <200401071932.i07JWN7E017376@gw.catspoiler.org> References: <200401071932.i07JWN7E017376@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2004-01-07 11:32:23 (-0800), Don Lewis <truckman@FreeBSD.org> 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: <Intel 21143 10/100BaseTX> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040108120326.GA22253>