From owner-freebsd-current  Tue Sep 17 20:54:33 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA22570
          for current-outgoing; Tue, 17 Sep 1996 20:54:33 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA22536
          for <current@FreeBSD.org>; Tue, 17 Sep 1996 20:54:27 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id UAA09793; Tue, 17 Sep 1996 20:54:16 -0700 (PDT)
Date: Tue, 17 Sep 1996 20:54:16 -0700 (PDT)
Message-Id: <199609180354.UAA09793@silvia.HIP.Berkeley.EDU>
To: rgrimes@GndRsh.aac.dev.com
CC: current@FreeBSD.org
In-reply-to: <199609180321.UAA01366@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com)
Subject: Re: RAM parity error
From: asami@FreeBSD.org (Satoshi Asami)
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

 * > Is there some other test I
 * > can run, other than stressing the SCSI system? 
 * 
 * Yes, ``make world''.

I've done this many times on this machine, both with and without ccd.
Also, it's been compiling most of packages-current recently, and it
can run like 4 simultaneous compilations without even flinching.

The crash so far has only happened during iozone.  It will crash with
100% probability if I run iozone on a ccd with a separate make
process.  It crashes less frequently if there is only one iozone on a
single ccd.  It did die with multiple iozone's on non-ccd disks too.

 * > (It doesn't crash when
 * > I run the "fast bcopy" benchmark, and I think that thing stresses the
 * > memory system a lot....)
 * 
 * That is only stressing the memory system from the ``host'' port, not
 * from the PCI bus master port.  Interactions between the two is what
 * really streeses the memory system to the limits.

I see.

Satoshi