From owner-freebsd-hardware  Mon Aug 18 21:29:21 1997
Return-Path: <owner-freebsd-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA08426
          for hardware-outgoing; Mon, 18 Aug 1997 21:29:21 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA08420
          for <hardware@freebsd.org>; Mon, 18 Aug 1997 21:29:17 -0700 (PDT)
Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1)
	id 0x0ft5-0000Wk-00; Mon, 18 Aug 1997 21:27:23 -0700
Date: Mon, 18 Aug 1997 21:27:22 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: Satoshi Asami <asami@cs.berkeley.edu>
cc: hardware@freebsd.org
Subject: Re: parity errors
In-Reply-To: <199708182317.QAA11642@vader.cs.berkeley.edu>
Message-ID: <Pine.BSF.3.95q.970818212602.1816A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Mon, 18 Aug 1997, Satoshi Asami wrote:

> What am I supposed to see when there is a parity error on the main
> memory?  I have a few memory modules I suspect to be bad, so I put
> them (256MB total) in our package building machine and tried a "make
> world", and got one "kernel page fault" (or something like that) and
> 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.
> 
> At this point, I think it is pretty clear that the memory's at fault,
> but shouldn't I see some "NMI" type messages?  (If I grepped
> correctly, it should be the "NMI indicates hardware failure" at line
> 265 in /sys/i386/i386/trap.c.)

  They are true parity simms right?  Do you have parity checking or
ECC turned on in the CMOS setup?

> This is with a P6-200 (not overclocked) on an Intel Venus motherboard.
> 
> Satoshi
> 
> 

Tom