Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucsd!ucsdhub!esosun!seismo!sundc!potomac!jtn
From: jtn@potomac.ads.com (John T. Nelson)
Newsgroups: comp.sys.next
Subject: Re: NeXT Memory - No Error Checking or Parity !
Summary: parity errors
Keywords: Memory,errors,parity
Message-ID: <7078@potomac.ads.com>
Date: 28 Oct 88 03:26:59 GMT
References: <549@gt-eedsp.UUCP> <3569@phri.UUCP>
Organization: Advanced Decision Systems, Arlington VA
Lines: 25

> In article <3569@phri.UUCP>, roy@phri.UUCP (Roy Smith) writes:

> 	I'm hardly an expert on ram, but here goes anyway.  We've got 19
> Sun-3's of various flavors around here with a total of 84 Mbytes of ram.
> We get a parity error panic on one machine or another a couple of times a
> year.  Make that, oh maybe, 1 error per 400 Mbyte-months.  In perhaps 2000
> Mbyte-months of operation, we've had one hard memory error.


It only takes once to crash a machine... and it will probably occur at
the least convenient time.  This might not sound so bad in a
University environment, but it could be disastorous elsewhere.  NeXT
really should have provided the extra bit pepr byte of parity
checking (and they probably will once we've all bought these initial
machine grumble).



-- 

John T. Nelson			UUCP: sun!sundc!potomac!jtn
Advanced Decision Systems	Internet:  jtn@potomac.ads.com
1500 Wilson Blvd #512; Arlington, VA 22209-2401		(703) 243-1611

Shar and Enjoy!