Date: Mon, 4 Feb 2008 20:56:54 +0100 From: Stefan Ehmann <shoesoft@gmx.net> To: freebsd-current@freebsd.org Cc: Marcin Wisnicki <mwisnicki+freebsd@gmail.com> Subject: Re: CFT: vr(4) Message-ID: <200802042056.54799.shoesoft@gmx.net> In-Reply-To: <fo7j40$6cb$1@ger.gmane.org> References: <20080204022334.GC27999@cdnetworks.co.kr> <200802041545.m14FjpVn014969@lava.sentex.ca> <fo7j40$6cb$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 04 February 2008 18:47:44 Marcin Wisnicki wrote: > On Mon, 04 Feb 2008 10:48:02 -0500, Mike Tancsa wrote: > > At 09:23 PM 2/3/2008, Pyun YongHyeon wrote: > >>Dear all, > >> > >>Here is overhauled vr(4) that shall address all known issues. PR > >>database showed vr(4) is not stable enough under high load and > > > > Hi, > > Is there a RELENG_7 or 6 version of the driver to test ? > > Using RELENG_7 from this morning, I get > > Try this: > http://wisnia21.freeshell.org/f/freebsd/if_vr-pyunyh-to-releng6.diff > > On RELENG7 there could be a conflict in second change that should be > safe to ignore. Using it with the second chunk ignored. > I'm not 100% sure if this is all that is required for RELENG6, but it > works wonderfully so far. > > Even fixed Rx errors I was seeing for some time and didn't have the time > to investigate whether they were caused by some recent commit to releng6 > (like the last mfc) or simply a hardware failure. The current vr driver works fine for me but the interface is only slightly loaded. It got stuck very rarely. Since I can't reproduce this, I don't know whether it's fixed. vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xa000-0xa0ff mem 0xf0000000-0xf00000ff at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x74 miibus0: <MII bus> on vr0 vr0: Ethernet address: 00:0e:a6:40:3f:d0 vr0: [ITHREAD] Works fine so far. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802042056.54799.shoesoft>