Date: Fri, 20 Sep 1996 17:03:51 +0200 (MET DST) From: Guido van Rooij <Guido.vanRooij@nl.cis.philips.com> To: nao@sbl.cl.nec.co.jp (Naoki Hamada) Cc: guido@gvr.win.tue.nl, dfr@render.com, Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@FreeBSD.org Subject: Re: new if_vx driver on freefall Message-ID: <199609201503.RAA25073@spooky.lss.cp.philips.com> In-Reply-To: <199609200757.QAA20436@sirius.sbl.cl.nec.co.jp> from Naoki Hamada at "Sep 20, 96 04:57:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Naoki Hamada wrote: > Hi. > > A few of my friends tested the new vx driver. The result is mostly > positive with/without BROKEN_AVAIL after a ping -f -s 1000. But one of > them reported that his system works with the new vx driver (with > BROKEN_AVAIL) almost well, but the network stops sometimes, then he > had to re-ifconfig the board. I ordered the specs from 3com and I'm waiting for them. Basically,if your board runs fine without BROKEN_AVAIL, do *not* define it. If it stops for your firends, could you verfiy with ifconfig vx0 that the state is OACTIVE? -Guido
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609201503.RAA25073>