Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!zehntel!dual!amdcad!decwrl!decvax!genrad!wjh12!talcott!harvard!seismo!brl-tgr!tgr!rbbb@RICE.ARPA From: rbbb@RICE.ARPA Newsgroups: net.unix-wizards Subject: tbuf errors Message-ID: <6592@brl-tgr.ARPA> Date: Sat, 15-Dec-84 22:42:53 EST Article-I.D.: brl-tgr.6592 Posted: Sat Dec 15 22:42:53 1984 Date-Received: Wed, 19-Dec-84 00:24:28 EST Sender: news@brl-tgr.ARPA Organization: Ballistic Research Lab Lines: 15 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, please let me know, because this all happened a looong time ago (but we still don't have the PCS, and we still run rev 7 hardware, and we don't get tbuf errors, and we swapped a pile of boards; I just can't remember exactly which one). And it is also true that Unix seems to get more of these than VMS (including the user-mode machine checks). Weird as shit. drc