Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site bradley.UUCP Path: utzoo!linus!decvax!decwrl!amd!dual!zehntel!ihnp4!inuxc!pur-ee!uiucdcs!bradley!brad From: brad@bradley.UUCP Newsgroups: net.bugs.2bsd Subject: Re: Re: 73 system problem? Message-ID: <1900003@bradley.UUCP> Date: Tue, 16-Oct-84 09:31:00 EDT Article-I.D.: bradley.1900003 Posted: Tue Oct 16 09:31:00 1984 Date-Received: Fri, 19-Oct-84 05:45:46 EDT References: <81@lasspvax.UUCP> Lines: 24 Nf-ID: #R:lasspvax:-8100:bradley:1900003:000:1264 Nf-From: bradley!brad Oct 16 08:31:00 1984 Here is a message that I recieved on that very same subject. The exchange program through DEC is going on until Dec, or so I understand. You really have to get your DEC salesman to dig to help you, most don't know or even heard about it, according to DEC the letters went out in July, so if you haven't heard better given them a call. Brad Smith Text Processing/Bradley Unversity -forward message- There is a bug in some (9%) early J-11 chips, check the date code on your CPU chip if your chip as made before May 1 1984, you may have the problem. The date code is on the CPU end of the J-11 chip and is of the form YYWW where YY is the year of Mfgr. and WW is the week, codes earlier than 8419 may have the fault. The problem is very hard to reproduce as it involves integer add/sub with certain values while a Cache miss or DMA Xfer is in progress. If your CPU fits the date code, get in touch with DEC. I'm in the process of getting a copy of the actual letter posted to a 11/73 owning friend of mine, I hope to get it on monday. Whenever I get it, I'll post a copy to the net as a whole. Keep in touch with me on this as there are at least 3 11/73s on the net now, you 2 and cepu!ucla-an (just getting going with 2.9, and a whole bunch of diskdrives).