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!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!decvax!wanginst!ucadmus!harvard!seismo!brl-tgr!tgr!ucscc!haynes%ucsce.ucscc.UUCP@Berkeley
From: haynes%ucsce.ucscc.UUCP%Berkeley@ucscc.UUCP
Newsgroups: net.unix-wizards
Subject: Vax 750 correctable memory errors
Message-ID: <8042@brl-tgr.ARPA>
Date: Tue, 5-Feb-85 14:30:55 EST
Article-I.D.: brl-tgr.8042
Posted: Tue Feb  5 14:30:55 1985
Date-Received: Sat, 9-Feb-85 04:49:12 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 17


<>

Under 4.2BSD:  Sometimes we get a correctable memory error reported on
the console, and it seems to persist until the system is rebooted.  Presumably
it is in an area of memory that is only read, such as the kernel or locore.
This suggests that (1) The memory controller hardware/firmware doesn't
write the corrected word back into memory when it corrects an error, but
leaves the bad word in there. (2) An appropriate thing for the software to
do in case of a correctable memory error would be to read the contents of
the location and write it back, thus making the correction 'permanent'.

Can anybody confirm that (1) is true and that (2) is appropriate?  Has
anybody patched the kernel code to do this?  Is this problem peculiar
to 750s?

ucbvax!ucscc!haynes