From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Overclocking CPU causes segmentation fault
Date: Wed, 23 Jan 2013 20:52:53 +0200 [thread overview]
Message-ID: <kdpbiq$cqv$1@ger.gmane.org> (raw)
In-Reply-To: <51001A29.6040006@googlemail.com>
On 23/01/13 19:13, Volker Armin Hemmann wrote:
> Am 23.01.2013 09:21, schrieb Nikos Chantziaras:
>> On 23/01/13 03:55, Dale wrote:
>>> [...]
>>> I tired overclocking once a good while back. It just wasn't worth it.
>>
>> I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three
>> years. Instead of a new CPU, I only bought a €30 cooler.
>>
>> Oh, it *was* totally worth it. Mainly for games, where the
>> performance difference was really dramatic.
>
> yeah and all those files with bit flips (not a problem with films or
> pics or mp3s....) you don't know about were totally worth it...
Stability testing is important. If no bit gets flipped after 5 hours of
Prime95, one can be confident that the chip can take it. But I never
noticed anything. At least git would have picked this up (I'm working
on a project with 330k lines of code; a change gets picked up as a
difference.)
But I agree; if I had any hugely important data on my system, I would
not have OCed it. I do not consider game saves, email and porn as
hugely important :-P The source code *is* important, but I said, it's
on a git server and therefore guarded against corruption.
next prev parent reply other threads:[~2013-01-23 18:53 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
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 [this message]
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='kdpbiq$cqv$1@ger.gmane.org' \
--to=realnc@gmail.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