From owner-freebsd-hardware Mon Aug 18 16:18:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24439 for hardware-outgoing; Mon, 18 Aug 1997 16:18:02 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24429 for ; Mon, 18 Aug 1997 16:17:56 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.6/8.7.3) id QAA11642; Mon, 18 Aug 1997 16:17:53 -0700 (PDT) Date: Mon, 18 Aug 1997 16:17:53 -0700 (PDT) Message-Id: <199708182317.QAA11642@vader.cs.berkeley.edu> To: hardware@freebsd.org Subject: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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.) This is with a P6-200 (not overclocked) on an Intel Venus motherboard. Satoshi