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 1955413860D for ; Wed, 23 Jan 2013 01:55:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D5A1421C040; Wed, 23 Jan 2013 01:55:24 +0000 (UTC) Received: from mail-yh0-f41.google.com (mail-yh0-f41.google.com [209.85.213.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4EED721C025 for ; Wed, 23 Jan 2013 01:55:23 +0000 (UTC) Received: by mail-yh0-f41.google.com with SMTP id 47so604258yhr.14 for ; Tue, 22 Jan 2013 17:55:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=umVSLBB4WDJdlYN2f8DHocxspMcycknXJ7dcd32JO5c=; b=zeD4qvaU+VsQq1fVe2d5vOtbG+qPpum9Vsn98muVZ1k1AKi3/2cLpBmCKqOVn7STP9 2ihWROrQapvoXPRZhom+mJKi9g9AZ/B/3jaaMNaGwwFFj5qZdL2oiwV/hJCnnBaNgQEw xtCeKs1TFsdqRS63vzEesN7CSk3W/bJdTtdHTV5+af9G8FDQ9PaFW79AdvkYpAwg2hc0 YOxjNvpEBWlZnW2qiEZM/nt0CnTSEIWo4wcgsShzDT93y52TUAZIShmotmH4MqyOn7q6 o9H+Rx9W2yehGswyniyknWr5z545QiLGcmCWd0sonGV5nHg/YOjsoT8sdKYibqkMzuE7 48Vw== X-Received: by 10.236.91.201 with SMTP id h49mr83123yhf.99.1358906122370; Tue, 22 Jan 2013 17:55:22 -0800 (PST) Received: from [192.168.2.5] (adsl-74-240-57-140.jan.bellsouth.net. [74.240.57.140]) by mx.google.com with ESMTPS id j13sm6394466ani.19.2013.01.22.17.55.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 17:55:21 -0800 (PST) Message-ID: <50FF4307.1010609@gmail.com> Date: Tue, 22 Jan 2013 19:55:19 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Overclocking CPU causes segmentation fault References: <50FE429A.8060708@nileshgr.com> <50FEDC01.9080306@googlemail.com> <50FEDE38.2010100@nileshgr.com> In-Reply-To: <50FEDE38.2010100@nileshgr.com> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 1253bf25-2bce-4e61-8221-f8c9b8ae0802 X-Archives-Hash: 7bf6c14b7f00c65875528cc7ae0a2b94 Nilesh Govindrajan wrote: > On Wednesday 23 January 2013 12:05:45 AM IST, Volker Armin Hemmann > wrote: >> Am 22.01.2013 08:41, schrieb Nilesh Govindrajan: >>> 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. >>> >>> >> and now you know why overclocking is stupid. (disabling mce is stupid >> too btw). >> >> Before there are segfaults there are silent data corruption errors. The >> file you downloaded and saved to the disk? Damaged - and you won't >> know... or you will, when those errors add up, turning precious data >> into binary garbage. >> >> Only overclock if there is nothing of worth on your computer - and >> nothing of worth done with it. But in that case - why use it in the >> first place? >> >> Don't be stupid. Don't overvlock. >> > Enabled MCE back after realising it's RAM issue. Anyway, it's too much > work running torture tests. Back to safe levels. > > -- > Nilesh Govindarajan > http://nileshgr.com > > I tired overclocking once a good while back. It just wasn't worth it. By the time you fix everything that gets broke, it just isn't worth that extra single digit percentage point of gain. You run the risk of having memory issues which can lead to bad data on the hard drive. Then that leads to more issues and this just keeps going in circles. At some point, it is going to fail and you could loose data that you don't really want to loose. There is also the heat issue as well. Also, I used to run foldingathome. It does not do well with overclocking. It will error out pretty quick. I tried this on a Abit NF7 v2 mobo. At that time, they were pretty much the king of overclocking. I bought everything intending to overclock but it wasn't worth it. I had a HUGE copper heat sink on that CPU. I wonder what the scrap value of that thing is? lol Save up, buy a faster CPU or just do a upgrade. Make a router out of the older box, if it doesn't pull to much power. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!