Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site unc.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!mcnc!unc!sherouse From: sherouse@unc.UUCP Newsgroups: net.unix-wizards Subject: Re: tbuf errors Message-ID: <221@unc.UUCP> Date: Mon, 17-Dec-84 17:11:50 EST Article-I.D.: unc.221 Posted: Mon Dec 17 17:11:50 1984 Date-Received: Thu, 20-Dec-84 03:30:26 EST References:Reply-To: sherouse@unc.UUCP (George W. Sherouse) Organization: CS Dept., U. of N. Carolina at Chapel Hill Lines: 26 In article rbbb@RICE.ARPA writes: >It is still possible to get the tbuf errors with rev 7 hardware. We have >always had rev 7 hardware, and we have never had the writeable control >store. We once had lots of errors, and now we do not. How did we fix >this, back in the days before microcode updates? I believe that we >replaced the L0001 module with one that used a different brand of chips. >This fix was discovered through a great deal of board-swapping; if anyone >has a similar story... Similar is not the word. We had exactly the same experience. The original L0001 was *so* bad we couldn't keep the machine up long enough to read the distribution tape! We are now crashing about once every two weeks with a light load. Is it true that there is a *tested* and available version of the micropatch loader for 4.2bsd? And does it really help? George W. Sherouse Associate Physicist Division of Radiation Therapy North Carolina Memorial Hospital Chapel Hill, NC 27514 (919) 966-1101