From: Marvin <marvin24@gmx.de>
To: Tim Small <tim@buttersideup.com>
Cc: bluesmoke-devel@lists.sourceforge.net
Subject: Re: ECC not detected
Date: Wed, 24 Feb 2010 12:51:05 +0100 [thread overview]
Message-ID: <201002241251.05318.marvin24@gmx.de> (raw)
In-Reply-To: <4B84E4E3.9050701@buttersideup.com>
> Marvin wrote:
> > I attached full dmesg, lspci and dmidecode (in case it helps) output. The
> > DRAM
>
> The output of "decode-dimms" is often also worth a look....
unfortunately, there is no module available to communicate with the eeprom.
In the mean time I found the reason for the error. The "real" CPU is a two core
Phenom (Phenom II X2 555 / BE 3.2 GHz). Two additional cores where enabled and
overclocked to 3.6 GHz in the BIOS setup (so BIOS reports X4 B55 / 3.6 GHz). While
this runs well under normal conditions (no crashes), other things seem to suffer -
like EDAC (also powernow-k8 has problems selecting the right clock frequency and
needs ignore_ppc option).
Sorry for the false report.
Marvin
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
next prev parent reply other threads:[~2010-02-24 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 20:35 ECC not detected Marvin
2010-02-24 8:35 ` Tim Small
2010-02-24 11:51 ` Marvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-23 19:08 Marvin
2010-02-23 19:23 ` Borislav Petkov
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=201002241251.05318.marvin24@gmx.de \
--to=marvin24@gmx.de \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=tim@buttersideup.com \
/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