From owner-freebsd-questions Tue Mar 28 03:31:15 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA08806 for questions-outgoing; Tue, 28 Mar 1995 03:31:15 -0800 Received: from dtr.com (dtr.rain.com [204.119.8.19]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA08789 for ; Tue, 28 Mar 1995 03:31:12 -0800 From: bmk@dtr.com Received: (from bmk@localhost) by dtr.com (8.6.11/8.6.9) id DAA00743; Tue, 28 Mar 1995 03:25:15 -0800 Message-Id: <199503281125.DAA00743@dtr.com> Subject: Re: RAM parity error?? To: krebs@faps.uni-erlangen.de (Thomas Krebs) Date: Tue, 28 Mar 1995 03:25:14 -0800 (PST) Cc: questions@FreeBSD.org In-Reply-To: <9503280822.AA07344@behaim.faps.uni-erlangen.de> from "Thomas Krebs" at Mar 28, 95 10:21:18 am Reply-To: bmk@dtr.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 978 Sender: questions-owner@FreeBSD.org Precedence: bulk > Hi, > since FreeBSD 2.0 my machine often crashes with "RAM parity error..." > In 1.1.5.1 I never had this problem, nor do I have it with dos. > I tried lots of hardware testing utilities (under dos) but none of them > could reliable report problems. Doesn't suprise me. Generally speaking, software based diagnostics for DOS suck. > My questions: > Is the "RAM parity error" in FreeBSD 2.0 (2.0-950322-SNAP) reliable? I would guess that message comes from your BIOS, and not from FreeBSD - but I could be mistaken. I would think that if FreeBSD detected an error of this sort, it'd force a panic. > Do you know of a real(!) good hardware (memory) testing utility, maybe under > dos? The only decent memory testers I've seen are dedicated SIMM testers - they are not cheap, and even so they don't detect all problems. Check your "CMOS setup" against the manufacturer's recommended settings. You might also try swapping out some of RAM to try and isolate the problem.