Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: dvandeer@oracle.com (Danny Vanderryn)
Newsgroups: comp.sys.sun
Subject: Re: Ethernet panic/reboot !!
Keywords: Networks
Message-ID: <1341@brchh104.bnr.ca>
Date: 19 Jan 91 00:39:42 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 15
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v10n11, Replies: v10n15
X-Sun-Spots-Digest: Volume 10, Issue 18, message 9
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

In article <1202@brchh104.bnr.ca> dupuy@cs.columbia.edu writes:
>
>There's a patch for the "RINT with buffer owned by chip", which you can
>get via anonymous ftp from princeton.edu, in
>~ftp/pub/sun-fixes/if_le.patch.shar.

Does this solve spurious "le0: No carrier - transceiver cable problem?"
messages as well?  Our network people have been reinstalling ethernet
boards left and right, etc., but I keep thinking maybe it's a software
prob.

[[Ed's Note: These messages (No carrier) were discussed in some detail a
while back (v8n80 v8n88 v8n98 v8n121 among others), and then general
consensus seemed to be that this was usually a hardware problem with loose
connections being the #1 cited cause. -bdg]]