From owner-freebsd-stable  Fri Sep 26 09:16:34 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA13452
          for stable-outgoing; Fri, 26 Sep 1997 09:16:34 -0700 (PDT)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA13447;
          Fri, 26 Sep 1997 09:16:29 -0700 (PDT)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA02310;
	Fri, 26 Sep 1997 09:17:32 -0700 (PDT)
Date: Fri, 26 Sep 1997 09:17:32 -0700 (PDT)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199709261617.JAA02310@biggusdiskus.flyingfox.com>
To: dg@root.com
Subject: Re: fxp driver/chip problems
Cc: hackers@freebsd.org, stable@freebsd.org
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Thanks for the information, David.  OK, I won't go off hunting for
a bug in the fxp driver :-).  As another data point, in my case, it's
the rev 1 card, and it's in 10 Mb mode.  Unfortunately, I have no
control over the hub being used, so I'll need to either upgrade to a
rev 2 card, and hope that "Intel (rev 2) inside" fixes it, or (sigh)
write a little "ping daemon" that resets the interface after several
lost ping packets to the gateway on the wire.  The things I stoop to :-)!

Jim Shankland
Flying Fox Computer Systems, Inc.