Date: Fri, 5 Dec 1997 13:59:39 -0500 From: "George M. Ellenburg" <gme@inspace.net> To: "'isp@freebsd.org'" <isp@freebsd.org>, "'hackers@freebsd.org'" <hackers@freebsd.org> Subject: FW: Touching Base Message-ID: <01BD0186.0B94F9C0.gme@inspace.net>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BD0186.0B94F9C0.gme>