From owner-freebsd-hardware  Mon Aug 18 23:10:38 1997
Return-Path: <owner-freebsd-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA13812
          for hardware-outgoing; Mon, 18 Aug 1997 23:10:38 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (wck-ca8-25.ix.netcom.com [204.31.231.89])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA13772
          for <hardware@FreeBSD.ORG>; Mon, 18 Aug 1997 23:10:04 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id XAA22389; Mon, 18 Aug 1997 23:02:59 -0700 (PDT)
Date: Mon, 18 Aug 1997 23:02:59 -0700 (PDT)
Message-Id: <199708190602.XAA22389@silvia.HIP.Berkeley.EDU>
To: tom@sdf.com
CC: hardware@FreeBSD.ORG
In-reply-to: <Pine.BSF.3.95q.970818212602.1816A-100000@misery.sdf.com> (message from Tom Samplonius on Mon, 18 Aug 1997 21:27:22 -0700 (PDT))
Subject: Re: parity errors
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * > two lockups (no message on console).  I disabled parity check in the
 * > BIOS, and world aborted once with a sh seg-faulting and once with
 * > a syntax error from make.

 *   They are true parity simms right?  

I think so.  There are 36 identical-looking chips on each module.
I've never seen such big SIMMs before.

However, I brought the memory home and stuck it in my computer, and
make world's almost done.  Maybe it's the mothearboard that can't
handle the big modules, I have an Intel Venus at work and Asus P6NP5
at home.

Which brings up another question: does anyone have the Venus working
with 64MB memory modules?  Is the Venus one of those that can't work
with 24-chip or higher modules?

We had two computers at work (pretty much the same hardware as others)
with thise 64MB modules, running Windows NT for Adobe PhotoShop.  They
kept crashing with lots of different errors, so I swapped the memory
with my package-building machine and got errors.  If it's that one
module is bad, I would think at least one of the machines would run
ok.

Of course, after I swapped the memory, the machines kept crashing so
maybe some of that was just general Windows NT flakiness.

 * 					Do you have parity checking or
 * ECC turned on in the CMOS setup?

Sorry, by "BIOS" above I meant "CMOS".

Satoshi