From owner-freebsd-hackers Fri Dec 5 12:00:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01491 for hackers-outgoing; Fri, 5 Dec 1997 12:00:56 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01486 for ; Fri, 5 Dec 1997 12:00:54 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id PAA17468; Fri, 5 Dec 1997 15:00:44 -0500 (EST) Date: Fri, 5 Dec 1997 15:00:42 -0500 (EST) From: Snob Art Genre To: "George M. Ellenburg" cc: "'hackers@freebsd.org'" Subject: Re: FW: Touching Base In-Reply-To: <01BD0186.0B94F9C0.gme@inspace.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Everything I've heard supports the thesis that memory-checking software is useless. The best way to test memory, IMO, is to put it in a machine and then run some big compiles, tar/gzips, that sort of thing. On Fri, 5 Dec 1997, George M. Ellenburg wrote: > 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 > > Ben "You have your mind on computers, it seems."