Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!sri-spam!nike!oliveb!tolerant!mordor!jdb
From: jdb@mordor.ARPA (John Bruner)
Newsgroups: net.unix-wizards
Subject: Re: SUN-3 messages - ie0: no carrier
Message-ID: <11959@mordor.ARPA>
Date: Thu, 17-Jul-86 18:30:57 EDT
Article-I.D.: mordor.11959
Posted: Thu Jul 17 18:30:57 1986
Date-Received: Sat, 19-Jul-86 01:11:31 EDT
References: <15@unc.unc.UUCP> <2393@phri.UUCP>
Reply-To: jdb@mordor.UUCP (John Bruner)
Distribution: net
Organization: S-1 Project, LLNL
Lines: 17

We see a lot of "ie0: no carrier" messages here, too.  They occur on
multiple machines (perhaps all of our Sun 3's) at once.  Our Sun 2's,
VAXes, Integrated Solutions, VALIDs, LSI-11's, and miscellaneous
other machines NEVER experience trouble with the Ethernet.

For a while I suspected that the "no carrier" messages were
correlated with "panic: ifree: freeing free inode" crashes that
we experience on our Sun 3's (only) with annoying frequency.  These
crashes usually leave behind an inode with a too-small link count
(the actual number of links is greater than the link count) and
must be recovered manually.  I'm no longer as suspicious of the
role of the "no carrier" errors in these crashes, but I haven't
ruled it out yet.
-- 
  John Bruner (S-1 Project, Lawrence Livermore National Laboratory)
  MILNET: jdb@mordor [jdb@s1-c.ARPA]	(415) 422-0758
  UUCP: ...!ucbvax!decwrl!mordor!jdb 	...!seismo!mordor!jdb