From owner-freebsd-hackers  Fri Sep 20 08:18:34 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA20642
          for hackers-outgoing; Fri, 20 Sep 1996 08:18:34 -0700 (PDT)
Received: from relay.philips.nl (ns.philips.nl [130.144.65.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA20605
          for <freebsd-hackers@FreeBSD.org>; Fri, 20 Sep 1996 08:18:23 -0700 (PDT)
Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id RAA29046; Fri, 20 Sep 1996 17:16:35 +0200
Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP
	id sma027123; Fri Sep 20 17:04:00 1996
Received: from spooky.lss.cp.philips.com (spooky.lss.cp.philips.com [130.144.199.105]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id RAA00835; Fri, 20 Sep 1996 17:06:52 +0200
Received: (from guido@localhost) 
	by spooky.lss.cp.philips.com (8.6.10/8.6.10-0.991c-08Nov95) id RAA25073; Fri, 20 Sep 1996 17:03:52 +0200
From: Guido van Rooij <Guido.vanRooij@nl.cis.philips.com>
Message-Id: <199609201503.RAA25073@spooky.lss.cp.philips.com>
Subject: Re: new if_vx driver on freefall
To: nao@sbl.cl.nec.co.jp (Naoki Hamada)
Date: Fri, 20 Sep 1996 17:03:51 +0200 (MET DST)
Cc: guido@gvr.win.tue.nl, dfr@render.com, Guido.vanRooij@nl.cis.philips.com,
        freebsd-hackers@FreeBSD.org
Reply-To: Guido.vanRooij@nl.cis.philips.com
In-Reply-To: <199609200757.QAA20436@sirius.sbl.cl.nec.co.jp> from Naoki Hamada at "Sep 20, 96 04:57:33 pm"
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

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