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 8E4C91385F2 for ; Tue, 22 Jan 2013 11:44:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A39FC21C062; Tue, 22 Jan 2013 11:44:11 +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 EB3FA21C003 for ; Tue, 22 Jan 2013 11:44:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 2F73B33DA3E for ; Tue, 22 Jan 2013 11:44:09 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: 0.277 X-Spam-Level: X-Spam-Status: No, score=0.277 tagged_above=-999 required=5.5 tests=[AWL=-0.922, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, 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 LoJzj-cs7qbv for ; Tue, 22 Jan 2013 11:44:03 +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 2FB4933DB52 for ; Tue, 22 Jan 2013 11:44:02 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TxcH2-0008T1-1v for gentoo-user@gentoo.org; Tue, 22 Jan 2013 12:44:16 +0100 Received: from athedsl-345361.home.otenet.gr ([85.72.204.175]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Jan 2013 12:44:16 +0100 Received: from realnc by athedsl-345361.home.otenet.gr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Jan 2013 12:44:16 +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: Tue, 22 Jan 2013 13:43:21 +0200 Organization: Lucas Barks Message-ID: References: <50FE429A.8060708@nileshgr.com> <50FE747D.5080408@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-345361.home.otenet.gr User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 In-Reply-To: <50FE747D.5080408@nileshgr.com> X-Archives-Salt: 63af4dc6-402f-435f-b6e2-26dab2b9bae0 X-Archives-Hash: 72d6d85020dc436461ccb6746b9a79f8 On 22/01/13 13:14, Nilesh Govindrajan wrote: > On Tuesday 22 January 2013 03:13:01 PM IST, Nikos Chantziaras wrote: >> On 22/01/13 09:41, Nilesh Govindrajan wrote: >>> So I have this old E2180 processor and no money as of now to buy a new >>> rig :P >>> I'm trying to overclock my CPU using BIOS host clock control and >>> everything is fine at 2.6 Ghz up to bootloader. >>> >>> Kernel segfaults. Any idea why? I'm running pf-kernel 3.7.2 and it >>> doesn't work with vanilla kernel either. >>> >>> Intel MCE is disabled in kernel configuration. >> >> When you raise the "host clock", which is the FSB, you are also >> raising the frequency of your RAM. So make sure you select a lower >> FSB:DRAM ratio in your BIOS. To begin with, set it to 1:1. >> >> Also, if you only have the stock CPU cooler that came with it, you >> won't be able to actually get a stable overclock. Your CPU's stock >> frequency is 2GHz. Without a better cooler, you might get it to 2.2 >> or 2.3 maybe. But 2.6? That's pretty optimistic. I don't think >> it'll work in the long run, unless you happen to have picked a good >> chip that can be overclocked without raising the VCore. >> >> But first, solve the RAM problem by lowering the FSB:DRAM ratio. >> >> > > I don't get even 2.1 with the stock cooler. Temperature easily goes > above 75-80 (spec say high temp is 86) on the prime95 test. Quite easy > to cook it considering that I'm a Gentoo user :D > Not really worth that. Thanks for replies. It really worth trying *lowering* VCore instead of raising it. If your chip happens to be very good and deal with this without causing instabilities, this will result in a big drop of temperatures. I did this on a C2D CPU in the past. I lowered VCore and raised FSB. I ended up with a good performance boost *and* lower temperatures. Unfortunately, not all chips behave the same. It's hit and miss.