From owner-freebsd-current  Mon Sep 23 08:12:09 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA02358
          for current-outgoing; Mon, 23 Sep 1996 08:12:09 -0700 (PDT)
Received: from walkabout.asstdc.com.au (walkabout.asstdc.com.au [202.12.127.73])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02257
          for <current@freebsd.org>; Mon, 23 Sep 1996 08:11:56 -0700 (PDT)
Received: (from imb@localhost)
          by walkabout.asstdc.com.au (8.7.6/BSD4.4) id BAA00512
          for current@freebsd.org; Tue, 24 Sep 1996 01:11:42 +1000 (EST)
From: michael butler <imb@asstdc.com.au>
Message-Id: <199609231511.BAA00512@walkabout.asstdc.com.au>
Subject: 3C589b + ep driver
To: current@freebsd.org
Date: Tue, 24 Sep 1996 01:11:42 +1000 (EST)
X-Comment: Phone 0419-240-180, International +61-419-240-180
X-Comment: finger imb@asstdc.com.au for PGP public key
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm still fighting with my laptop (100MHz TP560) and the ep driver.
Intermittently, the "link OK" light on my hub goes out and ifconfig reports
the driver hung in the OACTIVE state.

I've tried several things .. reinstating the dynamic TX_START_THRESH stuff
and reordering the ep_intr function. Since ep_intr is executed under
splbio(), I found that these hangs were much less frequent when I removed
the disabling of interrupts (with SET_INTR_MASK) but still there :-( The
threshold stuff appears to have little or no bearing on the problem.

At first, I though that the practice of re-reading status information (see
the "continue" on RX_COMPLETE or RX_EARLY) was the problem but coding around
this (reading only once per interrupt and moving the TX_STATUS stuff onto a
separate variable) didn't help either.

I can easily provoke a hung condition by ftp-ing (inbound) a sizable file
(e.g. a tarred and gzipped source tree) to my laptop. I cannot reliably
generate it with outbound traffic.

Since it seems that others are now having similar experiences with similarly
structured drivers (e.g. if_vx), I wonder if someone could shed some light
on what is going on (and how to fix it :-)) ?

My D-Link just causes a panic in the ed driver so this is the nearest I have
to "working" ..

	michael