From owner-freebsd-hackers  Fri Sep 26 08:55:39 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA12186
          for hackers-outgoing; Fri, 26 Sep 1997 08:55:39 -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 IAA12165;
          Fri, 26 Sep 1997 08:55:34 -0700 (PDT)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id IAA02046;
	Fri, 26 Sep 1997 08:56:42 -0700 (PDT)
Date: Fri, 26 Sep 1997 08:56:42 -0700 (PDT)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199709261556.IAA02046@biggusdiskus.flyingfox.com>
To: tarkhil@mgt.msk.ru
Subject: fxp driver problem?
Cc: hackers@freebsd.org, stable@freebsd.org
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Re Alex Povolotsky's problem (fxp driver becomes unresponsive, putting it
into promiscuous mode briefly makes it work again):  I am getting
sporadic reports of a similar (or the same) problem with the fxp driver
running on a hacked-up (by me) version of the 2.2.2-RELEASE kernel.
In our case, the fxp driver becomes unresponsive, bringing the interface
down and back up again with ifconfig brings it back to life.

I will likely be putting some effort into tracking this one down.  This is
complicated by the fact that the failure happens only on a heavily used
interface on a production system, and happens maybe once a month at most.
If anyone (dg?) has ideas on what to instrument to figure out what's
going on, I'm all ears :-).

Jim Shankland
Flying Fox Computer Systems, Inc.