From owner-freebsd-questions  Sat Aug 26 13:36:26 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id NAA29835
          for questions-outgoing; Sat, 26 Aug 1995 13:36:26 -0700
Received: from simon.chi.il.us (simon.chi.il.us [199.245.227.17])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id NAA29829
          for <questions@freebsd.org>; Sat, 26 Aug 1995 13:36:23 -0700
Received: by simon.chi.il.us (Smail3.1.29.1 #3)
	id m0smQqt-0006ILC; Sat, 26 Aug 95 14:25 CDT
Message-Id: <m0smQqt-0006ILC@simon.chi.il.us>
Date: Sat, 26 Aug 95 14:25 CDT
From: steve@simon.chi.il.us (Steven E. Piette)
To: BRUCE@AIIAD.COM, bugs@ns1.win.net
Subject: Re: ep0 status 2002
Cc: questions@freebsd.org
Sender: questions-owner@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