From owner-freebsd-commit  Sun Sep 17 11:10:52 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id LAA21684
          for freebsd-commit-outgoing; Sun, 17 Sep 1995 11:10:52 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id LAA21671
          for cvs-all-outgoing; Sun, 17 Sep 1995 11:10:47 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id LAA21657
          for cvs-user-outgoing; Sun, 17 Sep 1995 11:10:45 -0700
Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA21641
          ; Sun, 17 Sep 1995 11:10:06 -0700
Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id SAA03823; Sun, 17 Sep 1995 18:42:27 +0200
Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id SAA02314; Sun, 17 Sep 1995 18:42:26 +0200
Message-Id: <199509171642.SAA02314@grumble.grondar.za>
X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol
To: Bill Paul <wpaul@freefall.freebsd.org>
cc: mark@grondar.za (Mark Murray), CVS-commiters@freefall.freebsd.org,
        cvs-user@freefall.freebsd.org
Subject: Re: cvs commit: src/eBones/usr.sbin/kerberos kerberos.c 
Date: Sun, 17 Sep 1995 18:42:25 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-commit@FreeBSD.org
Precedence: bulk

I've got two systems, one an early-model pentium, the other a Cx486DLC both
experiencing the occasional odd failure when running under FreeBSD and I want
to double-check the hardware on these machines.

(Yes, I know about the cache weirdness on the 486DLC, I've even disabled the
 internal cache completely as part of my testing).

I think the Pentium either has a bad CPU (likely) or a bad cache chip (unlikely)
and the DLC either has a bad cache chip (likely) or bad dram (unlikely).

Does anyone have ANY pointers whatsoever to a really really really good and
thorough set of diagnostics that could be used to check for hardware faults?

Specificly, anything that can be used to diagnose external caches, memory,
(and in the case of the pentium, perform cpu diagnostics) would be cool.

Paul