From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 43AFD138628 for ; Wed, 23 Jan 2013 15:36:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2FABB21C0D3; Wed, 23 Jan 2013 15:35:57 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7F87E21C0CA for ; Wed, 23 Jan 2013 15:35:55 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id AC24833DA7B for ; Wed, 23 Jan 2013 15:35:54 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: 0.291 X-Spam-Level: X-Spam-Status: No, score=0.291 tagged_above=-999 required=5.5 tests=[AWL=-0.908, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=1.2, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FEuJeaow3OOi for ; Wed, 23 Jan 2013 15:35:49 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 163B933DA79 for ; Wed, 23 Jan 2013 15:35:48 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ty2Mq-0003Wa-By for gentoo-user@gentoo.org; Wed, 23 Jan 2013 16:36:00 +0100 Received: from athedsl-358384.home.otenet.gr ([85.72.255.142]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2013 16:36:00 +0100 Received: from realnc by athedsl-358384.home.otenet.gr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2013 16:36:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nikos Chantziaras Subject: [gentoo-user] Re: Overclocking CPU causes segmentation fault Date: Wed, 23 Jan 2013 17:35:09 +0200 Organization: Lucas Barks Message-ID: References: <50FE429A.8060708@nileshgr.com> <50FEDC01.9080306@googlemail.com> <50FEDE38.2010100@nileshgr.com> <50FF4307.1010609@gmail.com> <50FFD2EB.9030402@gmail.com> <50FFFD1E.3020701@nileshgr.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: athedsl-358384.home.otenet.gr User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 In-Reply-To: <50FFFD1E.3020701@nileshgr.com> X-Archives-Salt: adac77f6-a0a8-4961-a152-aa9777614375 X-Archives-Hash: f41d2c43722d05d0c87df90216401e71 On 23/01/13 17:09, Nilesh Govindrajan wrote: > On Wednesday 23 January 2013 07:52:03 PM IST, Nikos Chantziaras wrote: >> [...] >> In my experience, most of the time you can overclock. The issue is >> with the user not knowing exactly how to do it. You need to >> understand a few things and how they affect each other. It's not just >> a knob you can turn. > > That pretty much applies to me. I don't know much about hardware stuff. > Regarding your 1 Ghz overclock, you probably have good components in > terms of RAM & SMPS. > When I bought this rig in 2008, I knew nothing about good components, > blindly trusted local vendor... also internet shopping wasn't advanced > here. > So pretty much substandard components. The part that's really important is the mainboard. RAM doesn't matter. In my case, I had pretty basic 800MHz DDR2 RAM. Raising the FSB would bring it above that, so I changed the DRAM ratio to 1:1, and the RAM then ran at only 600Mhz. That was the starting point to rule out RAM problems. After that, I raised FSB but kept the VCore constant until I hit the first instabilities. When that happened, I raised VCore a bit. Rinse and repeat, until the VCore was still below the maximum recommendation by Intel. That happened at 3.4GHz (378MHz FSB * 9 CPU multiplier = 3402MHz CPU clock.) The E6600 CPU I got was an average sample. Others were running it at 3.6GHz (or even higher with water cooling.) This was a process that took about 3 days to complete (needs a lot of stability testing.) The good thing about those older CPUs was that the performance boost I got by OCing wasn't just scaling linearly with the CPU frequency. It was scaling *better* than that, because raising the FSB also made the mainboard itself perform better and with lower latencies. > Now that I know stuff, I'm thinking of assembling my own AMD FX8350 rig > soon by buying components from the web. > So, let's close this topic :-) As I said above, the mainboard is really the only important factor.