From owner-freebsd-hackers  Fri Dec  5 11:01:27 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA25426
          for hackers-outgoing; Fri, 5 Dec 1997 11:01:27 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from inspace.net (nova.ispace.com [207.204.40.7])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25419;
          Fri, 5 Dec 1997 11:01:22 -0800 (PST)
          (envelope-from gme@inspace.net)
Received: from caffeine (caffeine.inspace.net [207.204.40.248])
	by inspace.net (8.8.6) (8.8.6) (SPAM Stopper: 3.0b2) with SMTP id OAA06211;
	Fri, 5 Dec 1997 14:01:10 -0500 (EST)
Received: by localhost with Microsoft MAPI; Fri, 5 Dec 1997 13:59:46 -0500
Message-ID: <01BD0186.0B94F9C0.gme@inspace.net>
From: "George M. Ellenburg" <gme@inspace.net>
To: "'isp@freebsd.org'" <isp@freebsd.org>,
        "'hackers@freebsd.org'"
	 <hackers@freebsd.org>
Subject: FW: Touching Base
Date: Fri, 5 Dec 1997 13:59:39 -0500
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Greetings, Gentlemen.

An associate of mine is experiencing a rather unique problem with his 
FreeBSD box (P233, 64Mb Ram, 2 Maxtor 3.0gb IDE Hard Drives) ... I'm 
enclosing an excerpt from our message.  Perhaps you may have some clues 
as I'm stumped.

Regards,

George Ellenburg


-----Original Message-----
From:	Tom Holderby
Sent:	Friday, December 05, 1997 11:57 AM
To:	George M. Ellenburg
Subject:	Re: Touching Base

George,

[My Comments:]  [...Non Relevant Material Cut...]

Let me also give you a quick update on the FreeBSD situation.  When I 
run
that "tar x" while sitting at the console I see "Memory Parity Error". 
 But
I ran several iterations of the CheckIt memory diagnostic with its most
advanced testing options and it's not turning up any errors, so I tend 
to
believe it's a software problem.  I have definitely seen software bugs
cause memory parity halts, but that was mostly back in the days of
assembler code under DOS when you tried to access a non existant add  
ress.
I've never seen it under Unix before.  Any ideas?

Tom