From owner-freebsd-questions  Wed Oct  6  0:52: 2 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id D6A9414D3A
	for <freebsd-questions@FreeBSD.ORG>; Wed,  6 Oct 1999 00:51:59 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Received: from localhost (bright@localhost)
	by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id BAA08652;
	Wed, 6 Oct 1999 01:10:49 -0700 (PDT)
Date: Wed, 6 Oct 1999 01:10:48 -0700 (PDT)
From: Alfred Perlstein <bright@wintelcom.net>
To: Jamie Norwood <mistwolf@mushhaven.net>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Tracking down causes of crashes
In-Reply-To: <19991005141614.A92820@mushhaven.net>
Message-ID: <Pine.BSF.4.05.9910060110300.8080-100000@fw.wintelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Tue, 5 Oct 1999, Jamie Norwood wrote:

> 
> All,
> 
> I am running (From uname -a):
> 
> FreeBSD diarmadhi.mushhaven.net 3.2-STABLE FreeBSD 3.2-STABLE #2: Sun Aug
> 8 12:09:11 GMT 1999     root@:/usr/src/sys/compile/DIARMADHI  i386       
> 
> Now, I am running an Abit dual socket 370 mainboard with 2 Celeron 500
> CPU's. All work fine under low load, but should I raise the load (Say 
> by running Seti@Home, within 2 hours it just freezes up.              

Are you over clocking these celerons?

-Alfred



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message