From owner-freebsd-current Mon Nov 23 18:42:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22210 for freebsd-current-outgoing; Mon, 23 Nov 1998 18:42:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22168 for ; Mon, 23 Nov 1998 18:41:58 -0800 (PST) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id SAA12771; Mon, 23 Nov 1998 18:37:15 -0800 (PST) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199811240237.SAA12771@GndRsh.aac.dev.com> Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <5830.911860593@critter.freebsd.dk> from Poul-Henning Kamp at "Nov 23, 98 11:36:33 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 24 Nov 1998 02:37:15 +0000 (GMT) Cc: jdp@polstra.com, rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199811232228.OAA00715@vashon.polstra.com>, John Polstra writes: > > >> Well, I would, but I have been running this box > >> overclocked for more than 6 months now, never had > >> a glitch. Reboots only started back when other > >> people reported such behaviour on the list as well. > >> Im going to get a spare box and make a serial console > >> off of it, see if I can get the panic message. > > > >It doesn't make any difference how long your box has appeared to work. > >If you're overclocking it at all, we don't want to see your panic > >messages. They are too likely to mislead. It's just that simple. > > I would actually argue that the longer the box has been overclocked > the warmer the cpu runs. > > Think "dusty fans" to follow the drift. And in reality electromigration is something that takes some amount of time to occur. The additional heat created by overclocking the chip doesn't just cause problems instantly, it takes quite some time for the process to occur. It may run fine for a day, a week, a month, or even a year before enough damage occurs to cause a failure mode. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message