From owner-freebsd-current  Tue Sep 17 20:17:02 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA07487
          for current-outgoing; Tue, 17 Sep 1996 20:17:02 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA07460;
          Tue, 17 Sep 1996 20:16:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id UAA11098; Tue, 17 Sep 1996 20:17:39 -0700 (PDT)
Message-Id: <199609180317.UAA11098@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: asami@freebsd.org (Satoshi Asami)
cc: rgrimes@gndrsh.aac.dev.com, current@freebsd.org
Subject: Re: RAM parity error 
In-reply-to: Your message of "Tue, 17 Sep 1996 19:22:06 PDT."
             <199609180222.TAA09684@silvia.HIP.Berkeley.EDU> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 17 Sep 1996 20:17:39 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> * 							 I would highly
> * encorage you to try a swapout with some ``real parity'' memory and
> * more than likely watch your problem go away...
>
>I'd never buy a "logic parity" board myself, but unfortunately, these
>machines are donated to our project (they aren't even supposed to be
>running FreeBSD!) so I can't change anything in them. :(
>
>So, do you think this is a memory problem?  Is there some other test I
>can run, other than stressing the SCSI system?  (It doesn't crash when
>I run the "fast bcopy" benchmark, and I think that thing stresses the
>memory system a lot....)

   Not likely. All of the memory in wcarchive is "true" parity. The parity
errors always occur during the *same* instruction.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project