Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: rudolf@oce.orst.edu (Jim Rudolf)
Newsgroups: comp.sys.sun
Subject: ie0: lost interrupt: resetting
Message-ID: <8902080633.AA07926@oce.orst.edu>
Date: 15 Feb 89 21:02:12 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 33
Approved: Sun-Spots@rice.edu
Original-Date: Tue, 7 Feb 89 22:33:12 PST
X-Sun-Spots-Digest: Volume 7, Issue 157, message 4 of 21

I vaguely remember seeing this discussion somewhere before.  My apologies
if it has already been run into the ground.

We have two 3/280 servers running SunOS 3.5.  Almost on a weekly basis,
usually during a period of moderate net activity, one of the servers will
start spewing forth with:

	ie0: lost interrupt: resetting

If this starts happening, we'll generally start getting a few of these too:

	NFS getattr failed for server neptune: RPC: Timed out

Quoting from the man page:
     ie%d: lost interrupt: resetting
          The driver and 82586  chip  have  lost  synchronization
          with  each  other.   The  driver  recovers by resetting
          itself and the chip.

Our ethernet boards must not have read the man pages, because the affected
board does not recover by itself.  When this happens, the server is pretty
much hung up, and the only effective solution we've come up with is the
dreaded L1-A.  Who else has experienced this?  What did you do to stop it?

Thanks for your help,

Jim Rudolf
rudolf@oce.orst.edu
College of Oceanography
Oregon State University

[[ I can find no evidence of a previous discussion about this in either
volume 6 or 7. --wnl ]]