From owner-freebsd-stable Sat Jul 22 15:19:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id D605E37B506 for ; Sat, 22 Jul 2000 15:19:17 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA01836; Sat, 22 Jul 2000 17:19:06 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-103.max1.wa.cyberlynk.net(207.227.118.103) by peak.mountin.net via smap (V1.3) id sma001834; Sat Jul 22 17:18:58 2000 Message-Id: <4.3.2.20000722162331.00d5ec70@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Sat, 22 Jul 2000 17:18:03 -0500 To: "Rodney W. Grimes" From: "Jeffrey J. Mountin" Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Cc: lioux@uol.com.br (Mario Sergio Fujikawa Ferreira), freebsd-stable@FreeBSD.ORG In-Reply-To: <200007211953.MAA39777@gndrsh.dnsmgr.net> References: <4.3.2.20000721132938.00b49400@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:53 PM 7/21/00 -0700, Rodney W. Grimes wrote: >Note also that OC'ing can cause _permanent_ damage to semiconductors, >and that clocking down to spec may still leave you with hardware that >does not function correctly. The predominant failure mode is caused >by something called electromigration that has to do with metal migrating >into the semiconductor due to operating at excessive temperature. Certainly, but excellent cooling is a must when OC'ing, even if one is just doing a quick test to see if the CPU can be OC'ed. Electromigration can happen when running a CPU within specs, except for sufficient cooling. >Electromigration is a non reversable process, and it only takes a few >microseconds to occur should the temperature at a metal/silicon interface >rise above a certain threshold, this spot heating occurs on the microscopic >level and external temperature monitoring has very little, if any, >visibility into it. This problem becomes more and more critical as >geometries shrink. A design flaw can also attribute. My C instructor ran into to this years back with an Alpha when using 2 registers in a tight loop. The layout had them adjacent on the chip, resulting in excessive heat explaining the odd failures. Didn't care to add more to OC'ing, but what the hey. Just run for cover afterwards. ;) OC'ing non-Intel processors has shown the smallest gain. As mentioned on the list they already run hot. Trying to squeeze more out is asking for trouble. A good OC'ing text *should* mention this. While I no longer have any OC'ed servers, I do make sure to have better processor cooling and prefer 2 fans per CPU. Should one fail, the cooling is sufficient, since most are designed for OC'ing. http://www.computernerd.com/ I've used products from the first for some time now. The FC-PGA pages are buried at: http://www.computernerd.com/futu33.html Those that like to OC may wish to check out: http://www.computernerd.com/futu36-1.html For links to various cooling suppliers check out: http://www.heatsink-guide.com/ Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message