From owner-freebsd-current Fri Apr 10 14:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21154 for freebsd-current-outgoing; Fri, 10 Apr 1998 14:44:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21149 for ; Fri, 10 Apr 1998 14:44:36 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id OAA06116; Fri, 10 Apr 1998 14:43:57 -0700 (PDT) Date: Fri, 10 Apr 1998 14:43:57 -0700 (PDT) From: Jim Shankland Message-Id: <199804102143.OAA06116@biggusdiskus.flyingfox.com> To: lickyou@ein-hashofet.co.il, toasty@home.dragondata.com Subject: Re: ps segfaults since I overclocked. and worries. Cc: current@FreeBSD.ORG, jkh@time.cdrom.com, phk@critter.freebsd.dk, steve@visint.co.uk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, to the best of my knowledge, the p166 and p200 were almost > identical except the fact that intel test these prior to shipment, to > make sure what processor can achieve what clock speed without burning. > I think overclocking is a 99% fail-proof way to achieve better > performance from your CPU(To a limited extent, ofcourse) without > paying more money for something which is about the same. Let me make sure I got this right. 1. Intel makes chip. 2. Intel tests chip at 200 MHz; it fails. 3. Intel tests chip at 166 MHz; it works. 4. Intel sells chip as a P166. 5. Customer buys this P166. 6. Customer overclocks chip to 200 MHz. 7. Customer experiences failures. 8. Customer gripes to FreeBSD mailing lists about "inherent limits" in FreeBSD. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message