From owner-freebsd-hackers  Fri Jun 21 15:36:11 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA09185
          for hackers-outgoing; Fri, 21 Jun 1996 15:36:11 -0700 (PDT)
Received: from xenon.chromatic.com (xenon.chromatic.com [199.5.224.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA09180
          for <hackers@freebsd.org>; Fri, 21 Jun 1996 15:36:09 -0700 (PDT)
Received: from ohio.chromatic.com (ohio.chromatic.com [199.5.224.98]) by xenon.chromatic.com (8.7.5/8.7.3) with ESMTP id PAA09780; Fri, 21 Jun 1996 15:35:33 -0700 (PDT)
Received: (from hua@localhost) by ohio.chromatic.com (8.6.12/8.6.12) id PAA01459; Fri, 21 Jun 1996 15:35:32 -0700
Date: Fri, 21 Jun 1996 15:35:32 -0700
From: Ernest Hua <hua@XENON.chromatic.com>
Message-Id: <199606212235.PAA01459@ohio.chromatic.com>
To: hackers@freebsd.org
Subject: Memory tests ...
Cc: hua@XENON.chromatic.com
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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