From owner-freebsd-hackers Mon Jun 24 05:17:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13775 for hackers-outgoing; Mon, 24 Jun 1996 05:17:19 -0700 (PDT) Received: from www.hsc.wvu.edu (www.hsc.wvu.edu [157.182.98.68]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA13756 for ; Mon, 24 Jun 1996 05:17:16 -0700 (PDT) Received: (from jsigmon@localhost) by www.hsc.wvu.edu (8.6.12/8.6.12) id IAA11352; Mon, 24 Jun 1996 08:17:53 -0400 Date: Mon, 24 Jun 1996 08:17:53 -0400 (EDT) From: Jeremy Sigmon To: Ernest Hua cc: hackers@freebsd.org, hua@XENON.chromatic.com Subject: Re: Memory tests ... In-Reply-To: <199606212235.PAA01459@ohio.chromatic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to the systems people around here, the best way to test memory is to put it into a Novell server. If the memory is flakey it will let you know fast. (ABEND???) I thinks someone around here has a 4.1 2 user box setup just for that purpose. On Fri, 21 Jun 1996, Ernest Hua wrote: > Anyone know of any memory testing utilities for FreeBSD? > > I've just spent countless days with yet another set of > questionable SIMMs, and I just can't wait for the real > hardware SIMM tester. In the mean time, I really want to > run some memory tests to check for the basic problems. > > If none exists, how does one demand physical access to > memory? Does mmap() have that ability? How do I prevent > the kernel from waking up during a critical region of the > test. > > Ern >