From owner-freebsd-questions  Mon Sep 25 09:20:52 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id JAA15723
          for questions-outgoing; Mon, 25 Sep 1995 09:20:52 -0700
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA15718
          for <questions@freebsd.org>; Mon, 25 Sep 1995 09:20:46 -0700
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA28362; Mon, 25 Sep 1995 12:20:08 -0400
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 25 Sep 1995 12:20 EDT
Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.11/8.6.5) with ESMTP id KAA03965; Mon, 25 Sep 1995 10:02:44 -0400
Received: (from rivers@localhost) by lakes (8.6.11/8.6.9) id KAA00531; Mon, 25 Sep 1995 10:10:02 -0400
Date: Mon, 25 Sep 1995 10:10:02 -0400
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199509251410.KAA00531@lakes>
To: BRUCE@AIIAD.COM, bugs@ns1.win.net, simon.chi.il.us!steve@dg-rtp.dg.com
Subject: Re: ep0 status 2002
Cc: questions@freebsd.org
Content-Type: text
Content-Length: 1840
Sender: owner-questions@freebsd.org
Precedence: bulk

> 
> > From freefall.FreeBSD.org!owner-freebsd-questions Thu Aug 24 15:06:30 1995
> > Sender: freefall.FreeBSD.org!owner-freebsd-questions
> > From: Mark Hittinger <bugs@ns1.win.net>
> > Subject: ep0 status 2002
> > To: questions@freebsd.org
> > Date: Thu, 24 Aug 1995 12:36:33 -0400 (EDT)
> > X-Mailer: ELM [version 2.4 PL23]
> > Content-Type> : > text> 
> > Content-Length: 439
> > Sender: questions-owner@freebsd.org
> > 
> > > From: BRUCE@AIIAD.COM
> > > got ep0 status 2002.  I'm using 3com etherlink III. 
> > >  everything seems to be working fine.
> > 
> > same here :-)  We see this about 4 times a day on our servers.  We see it
> > on the EISA 3c5x9 running -current and on boxes running -stable with the
> > ISA version.
> > 
> > > can you tell me what this is or where I can look it 
> > > up?
> > 
> > I'm curious too.  The sources don't indicate what it is.
> > 
> > Regards,
> > 
> > Mark Hittinger
> > bugs@win.net
> > 
> 
> These status errors are generated when the card indicates an adaptor failure.
> 
> ie: if (status & S_CARD_FAILURE) printf("ep%d: Status: %x\n", unit, status);
> 
> That's where the 0x0002 part of the status comes from. The 0x2000 means
> window 1 is the active window at the time of the failure, which is normal.
> 
> 3Com describes three type of errors that can cause an adaptor failure.
> 
> Transmit overrun (host writes more that there is room for in TX buffer)
> 
> Receive underrun (host reads data that is not yet available or past the
> pad bytes in RX FIFO)
> 
> Internal hardware errors as yet undefined.
> 
> If you compile the ep driver with EP_LOCAL_STATS defined it will print
> more information and we can figure out which error it is.
> 
> Steve
> 
> 
> 

 Just to chime in here - I also see this problem on a DELL P-90 with
a 3c509 - about once every other day...

	- Dave R. -