From owner-freebsd-stable Sun Aug 15 1:43:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alice.gba.oz.au (gba-254.tmx.com.au [203.9.155.254]) by hub.freebsd.org (Postfix) with SMTP id D041314CF0 for ; Sun, 15 Aug 1999 01:43:06 -0700 (PDT) (envelope-from gjb-freebsd@gba.oz.au) Received: (qmail 24845 invoked by uid 1001); 15 Aug 1999 18:14:34 +1000 Message-ID: <19990815081434.24844.qmail@alice.gba.oz.au> X-Posted-By: GBA-Post 1.03 20-Sep-1998 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Date: Sun, 15 Aug 1999 18:14:33 +1000 From: Greg Black To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Random disk read problems References: In-reply-to: of Sat, 14 Aug 1999 23:32:01 MST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer writes: > Bad memory seems like the best bet. The BIOS on the motherboard (a > SuperMicro S2DGU) has settings for memory checking that are disabled > (it came from the vendor that way, with FreeBSD 2.2.8 installed). Is > there any point in turning this on? Anything I can do besides buying > another DIMM to plug in to test it? It's certainly worth turning on the memory checking. If it fails, then you can be certain the memory is no good. And if it passes, you can't trust the result :-) I built a new box out of bits last week and got all sorts of random failures, with various programs crashing in odd ways. In each case, md5 checksums of the faulty program and the original on the CD differed. I bet on bad memory, turned on the memory checks and fortunately it failed, so my vendor agreed to swap the memory, although when he saw FreeBSD starting up after he swapped the chip he wanted to blame the OS for the problem :-( -- Greg Black -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message