From: Nilesh Govindrajan <me@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Overclocking CPU causes segmentation fault
Date: Wed, 23 Jan 2013 00:15:12 +0530 [thread overview]
Message-ID: <50FEDE38.2010100@nileshgr.com> (raw)
In-Reply-To: <50FEDC01.9080306@googlemail.com>
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
next prev parent reply other threads:[~2013-01-22 18:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:41 [gentoo-user] Overclocking CPU causes segmentation fault Nilesh Govindrajan
2013-01-22 9:16 ` Helmut Jarausch
2013-01-22 9:43 ` [gentoo-user] " Nikos Chantziaras
2013-01-22 11:14 ` Nilesh Govindrajan
2013-01-22 11:43 ` Nikos Chantziaras
2013-01-22 11:46 ` Nilesh Govindrajan
2013-01-22 13:49 ` Nilesh Govindrajan
2013-01-22 18:35 ` [gentoo-user] " Volker Armin Hemmann
2013-01-22 18:45 ` Nilesh Govindrajan [this message]
2013-01-23 1:55 ` Dale
2013-01-23 8:21 ` [gentoo-user] " Nikos Chantziaras
2013-01-23 12:09 ` Dale
2013-01-23 14:22 ` Nikos Chantziaras
2013-01-23 15:09 ` Nilesh Govindrajan
2013-01-23 15:35 ` Nikos Chantziaras
2013-01-23 16:22 ` Bruce Hill
2013-01-23 16:32 ` Nikos Chantziaras
2013-01-23 17:16 ` Volker Armin Hemmann
2013-01-23 17:21 ` Michael Mol
2013-01-23 18:46 ` Nikos Chantziaras
2013-01-23 17:13 ` Volker Armin Hemmann
2013-01-23 18:52 ` Nikos Chantziaras
2013-01-24 2:23 ` [gentoo-user] " Peter Humphrey
2013-01-24 4:08 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FEDE38.2010100@nileshgr.com \
--to=me@nileshgr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox