From owner-freebsd-stable Sat Jan 8 22:10:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id E9AE414BDA for ; Sat, 8 Jan 2000 22:10:32 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id WAA71435 for ; Sat, 8 Jan 2000 22:10:33 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: Subject: RE: load spike strangeness Date: Sat, 8 Jan 2000 22:10:34 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200001090555.GAA88547@dorifer.heim3.tu-clausthal.de> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Of course, overclocking is not recommended. There is (and was) > no doubt about that. But it certainly does not cause the kind > of problems which this thread is about, originally. > > Regards > Oliver > Thank GOD we're getting back to the issue at hand. I don't know that to be necessarily true but I'm no guru. Overclocking can cause "random strangeness" in any OS which, again IMHO, includes load spikes. I'm not saying that's definitely it, in fact, I think Mr. Bushong stated, later, that it was doing so even before he started overclocking. So I doubt, now, that was it but when I originally replied it was merely a possibility. *shrug* To quote Forrest Gump: "And that's all I have to say about that." FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message