From owner-freebsd-questions  Tue Oct  8 11:16:56 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA12454
          for questions-outgoing; Tue, 8 Oct 1996 11:16:56 -0700 (PDT)
Received: from spoon.beta.com (root@[199.165.180.33])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA12445
          for <questions@freebsd.org>; Tue, 8 Oct 1996 11:16:52 -0700 (PDT)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.7.5/8.6.9) with ESMTP id OAA03574; Tue, 8 Oct 1996 14:16:36 -0400 (EDT)
Message-Id: <199610081816.OAA03574@spoon.beta.com>
To: questions@freebsd.org
cc: fgray@rice.edu
Subject: vx driver...
Date: Tue, 08 Oct 1996 14:16:35 -0400
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I was reading the man page on the vx driver, and noted that 3Com is aware
that these "early rev" cards were known to drop a large number of
packets. I've been seeing additional problems while running under DOS
with my 3C590 card - for instance, my X windows emulator will tell the server
that the client connection has been accepted, and then never open the
window on the screen. Under Unix (FreeBSD), it dies after a handful of
packets, and 50% of the time, requires a reboot to get the card back
to a level of sanity.

Does anyone know if 3Com will readily admit to these problems, and if they
have any plan for replacing the so-called "defective" cards? I'm curious,
as I'm about to go head to head with their tech support, and want all the
ammunition I could have.
	-Brian