From owner-freebsd-stable Fri May 19 18: 7: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by hub.freebsd.org (Postfix) with ESMTP id C912637B68F for ; Fri, 19 May 2000 18:07:00 -0700 (PDT) (envelope-from manek@ecst.csuchico.edu) Received: from after (shiva-user30.corp.home.net [24.0.8.160]) by zipcode.corp.home.net (8.9.3/8.9.3) with SMTP id SAA26751; Fri, 19 May 2000 18:05:24 -0700 (PDT) From: "Sameer R. Manek" To: "Mike C. Muir" , "Sebastien ROCHE" Cc: Subject: RE: occasional reboots Date: Fri, 19 May 2000 18:04:44 -0700 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mike C. Muir > Sebastien ROCHE wrote: > > > > I had this kind of problem. > > The solution was to increase the CAS latency from 2 to 3, and to go back > > to a not-overclocked cpu. > > Strangely, I find FreeBSD to be the most welcoming OS to overclocked > cpu's.. > My old celeron 300a which would only go so far as 464mhz in Win NT or 98, > under FreeBSD 3.2-S, was rock solid at 504mhz. > Right now i have two ppga 366's at 550, under freebsd they are stable at > any speed between 550 and 600 (havnt tried any higher) yet Win2k/98 only > seem to accept 550 without occasional freezes (albiet after a long time) Overclocking is entirely a crap shot. You are pushing a system to above what the vendor rated it for. Maybe it will work, as for you it did. Or maybe you'll end up with a pile of molten transistors. It's not a good way to measure os stability, it is expected that the os will barf on hardware errors. The question you should be asking is what errors is win 2k/nt/98 failing on, that fbsd is apparently not noticing, or handling differently. RAM errors? bus errors? cache errors? video card errors? Sameer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message