From owner-freebsd-current  Sun Feb  9 17:35:35 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA26972
          for current-outgoing; Sun, 9 Feb 1997 17:35:35 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26943
          for <current@freebsd.org>; Sun, 9 Feb 1997 17:35:21 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id BAA19432; Mon, 10 Feb 1997 01:35:04 GMT
Date: Mon, 10 Feb 1997 10:35:03 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Andrew Herdman <andrew@why.whine.com>
cc: Poul-Henning Kamp <phk@critter.dk.tfs.com>, current@freebsd.org
Subject: Re: Make world of Current dies with weird errors. 
In-Reply-To: <Pine.BSF.3.95.970209191813.20055A-100000@why>
Message-ID: <Pine.SV4.3.95.970210103224.19032C-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Make world is well known to be a good stress tester.

BTW, in case you didn't this time, please report things like overclocking
the cpu initially.  It would really save some bandwidth on this mailing
list.

Mike Hancock

On Sun, 9 Feb 1997, Andrew Herdman wrote:

> I was able to actually make world today.  I had been overclocking my cpu
> at a 75mhz bus vs. a 66mhz bus.  Dropping it to 66, or disabling the
> level2 cache cause the problem to go away.  Question is... why is the only
> thing affected is make world?  It doesn't make sense.
> 
> Andrew