From owner-freebsd-questions Thu Oct 4 20:35:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from lists.blarg.net (lists.blarg.net [206.124.128.17]) by hub.freebsd.org (Postfix) with ESMTP id C920D37B403 for ; Thu, 4 Oct 2001 20:35:44 -0700 (PDT) Received: from thig.blarg.net (thig.blarg.net [206.124.128.18]) by lists.blarg.net (Postfix) with ESMTP id BB63EBCFB; Thu, 4 Oct 2001 20:35:43 -0700 (PDT) Received: from localhost.localdomain ([206.124.139.115]) by thig.blarg.net (8.9.3/8.9.3) with ESMTP id UAA28740; Thu, 4 Oct 2001 20:35:43 -0700 Received: (from jojo@localhost) by localhost.localdomain (8.11.6/8.11.3) id f953d9B89985; Thu, 4 Oct 2001 20:39:10 -0700 (PDT) (envelope-from swear@blarg.net) To: "Kory Hamzeh" Cc: "Jonathan Blanton" , Subject: Re: Random crashes References: <000801c14d27$73f9d260$14ce21c7@avatar.com> From: swear@blarg.net (Gary W. Swearingen) Date: 04 Oct 2001 20:39:08 -0700 In-Reply-To: <000801c14d27$73f9d260$14ce21c7@avatar.com> Message-ID: <76zo76kb6r.o76@localhost.localdomain> Lines: 24 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Kory Hamzeh" writes: > There are some memory test utilities in the /usr/ports/sysutils directory, > but they can only test portions on the main memory. That may be correct, but there's a version of /usr/ports/sysutils/memtest which tests all of memory after booting from a floopy that it has you make during "install". You might have to get via freshmeat.net or somewhere. I've used memtest v.2.7 and it comes with a version that runs from the command line (which I suppose is what was ported) and the floppy thing. It had a minor bug when run on an old 486 (reporting a bad cell repeatedly, but by dinking with the part of memory you ask it to test, I could get the bad address to change, so it looks like a bug, not bad memor). It has quite a few tests, some of which take hours to run, but which it claims does an extremely good job of testing. I suspect that is only theoretically so, and that one could get a few memory-type (maybe memory I/O?, maybe timing) errors to occur by heavy use of the CPU and I/O subsystems at the same time as memory testing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message