Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: mtap!meier@rutgers.edu (Christopher M. Meier)
Newsgroups: comp.sys.sun
Subject: Re: ie0: lost interrupt: resetting
Message-ID: <17217@srcsip.UUCP>
Date: 1 Mar 89 18:42:49 GMT
References: <8902080633.AA07926@oce.orst.edu>
Sender: usenet@rice.edu
Organization: Honeywell Systems & Research Center, Camden, MN
Lines: 18
Approved: Sun-Spots@rice.edu
Original-Date: 19 Feb 89 04:33:11 GMT
X-Sun-Spots-Digest: Volume 7, Issue 176, message 3 of 12
X-Issue-Reference: v7n157

rudolf@oce.orst.edu (Jim Rudolf) writes:
>...[getting "ie0: lost interrupt: resetting" messages]
>If this starts happening, we'll generally start getting a few of these too:
>	NFS getattr failed for server neptune: RPC: Timed out

Until I read this line, I thought this was written by someone here.
We have no 'neptune' 280.

We have seen this, but mostly at times when someone is adding/removing a
number of nodes from the ethernet.  This seems to cause lots of 'noise' on
the cable(s).  I can't qualify the 'noise', as I haven't had a sniffer to
use during one of those times.  It has also been seen when the network
traffic is heavy, but someone somewhere may have been fooling with the
cable.  We don't have a solution.

@ Christopher  M.  Meier   ms:  MN65-2300   Honeywell Systems & Research Center
@ Research Scientist/SIP   (612) 782-7191   3660 Technology Drive
@ meier@SRC.Honeywell.COM  !SRCSIP!meier    Mpls, MN  55418