Xref: utzoo comp.dcom.lans:7572 alt.sys.sun:3248 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!uw-beaver!mit-eddie!rutgers!usc!elroy.jpl.nasa.gov!lll-winken!xanth!xanth.cs.odu.edu!jason From: jason@cs.odu.edu (Jason "dedos" Austin) Newsgroups: comp.dcom.lans,alt.sys.sun Subject: Re: Booting a SPARCstation SLC Message-ID: Date: 24 Mar 91 05:10:38 GMT References: <1991Mar23.020515.22554@ccs.carleton.ca> Sender: usenet@cs.odu.edu (Usenet News Poster) Distribution: comp Organization: Old Dominion University, Norfolk, VA Lines: 20 In-Reply-To: mikey@ccs.carleton.ca's message of 23 Mar 91 02:05:15 GMT Nntp-Posting-Host: lancelot.cs.odu.edu In article <1991Mar23.020515.22554@ccs.carleton.ca> mikey@ccs.carleton.ca (Mike McFaul) writes: -> In article otto@tukki.jyu.fi (Otto J. Makela) writes: -> >We just got a SPARCstation SLC, which works fine except that during tftp -> >bootup, we get these messages splattered all over the screen: -> > CRC Error -> > Silo exceeded -> >Now, these would seem to be Ethernet traffic statuses. Is our network -> >getting congested, or is the boot server (a 4/260) somehow misconfigured ? -> >Or are these messages normal ? -> -> I believe these are indications of garbage on your network. We have an SLC -> and a Sparc station 1+ (diskless) and we've seen similar stuff when our -> network had bad packets on it. We installed a bridge between the offending -> equipment and our network and the errors went away. If it's only this one machine that's giving you trouble, try swapping transceivers and see if the problem follows. -- Jason C. Austin jason@cs.odu.edu