From owner-freebsd-current Mon Nov 23 17:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15149 for freebsd-current-outgoing; Mon, 23 Nov 1998 17:20:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15144 for ; Mon, 23 Nov 1998 17:20:18 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA44812; Mon, 23 Nov 1998 17:17:10 -0800 (PST) To: Poul-Henning Kamp cc: John Polstra , rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Mon, 23 Nov 1998 23:36:33 +0100." <5830.911860593@critter.freebsd.dk> Date: Mon, 23 Nov 1998 17:17:09 -0800 Message-ID: <44808.911870229@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would actually argue that the longer the box has been overclocked > the warmer the cpu runs. I've also had OC'd boxes start failing. A trusty PPro 233 of mine ran OC'd for almost 2 years before finally starting to exhibit occasional flakiness. I now run it at 200 and it's happy again. Next to it sits another PPro which has run at 233 all its life without any problems *except* during the summer months, at which point things start doing the sig-11 dance. I keep it around deliberately in that configuration to show people who claim that OC'ing is entirely safe and a boolean go/no-go decision at worst. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message