public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ECC-ram, it is worth it.
Date: Wed, 30 Jul 2014 12:14:06 +0200	[thread overview]
Message-ID: <53D8C56E.4010305@googlemail.com> (raw)
In-Reply-To: <53D8B78C.2080208@openmailbox.org>

Am 30.07.2014 11:14, schrieb Edward M:
> On 07/29/14 11:18, Frank Steinmetzger wrote:
>> On Sat, Jul 26, 2014 at 11:00:26PM -0700, Edward MN wrote:
>>> On 07/26/14 15:55, walt wrote:
>>>> On 07/26/2014 10:39 AM, Volker Armin Hemmann wrote:
>>>>> [894019.770058] [Hardware Error]: MC4 Error (node 0): DRAM ECC error
>>>>> detected on the NB.
>>>>> […]
>>>>> and this, my children, is why I am using ECC ram.
>>>>> […]
>>>>> And this evening, with a thunderstorm outside I got that beauty
>>>>> above...
>>>>
>>>> Is ECC memory a drop-in replacement for ordinary RAM, or does it need
>>>> a special motherboard?
>>>>
>>>     yeah, requires a motherboard that supports ECC ram.
>>
>> Big was my surprise to learn that our old Pentium 3 PC from 1999 has ECC
>> support in its three RAM sockets. The problem today is the artificial
>> paritioning of the market.
>>
>> It seems nigh impossible (at least in the Intel world, please correct me
>> regarding AMD) to have ECC RAM in a normal Home PC these days,
>> especially in
>> an ITX form factor, as I am currently investigating. There are Xeons
>> for the
>> 1150 “consumer socket”, but ECC is only supported by server chipsets
>> such as
>> the C series. Those come either on ITX boards with abysmal I/O
>> capabilities
>> for home use or on high-power workstation ATX boards that cost a small
>> fortune. *sigh*
>>
>> I would have liked the aspect of a system that tells me when
>> something goes
>> wrong, but there seems no such thing for my requirements. So I must help
>> myself with file checksums when dealing with my archive disks.
>>
>
>
>   Unfortunately, I think it would be difficult finding a home-user board
>   with ECC support. since, nowadays appears ECC is mostly for systems
>   where data corruption is unacceptable, such a bank,etc
>

pretty easy actually. When I looked for ECC support, ALL Asus boards
supported it officially - and a whole bunch of Gigabyte boards according
to their forums.


  reply	other threads:[~2014-07-30 10:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26 17:39 [gentoo-user] ECC-ram, it is worth it Volker Armin Hemmann
2014-07-26 17:58 ` [gentoo-user] " Nikos Chantziaras
2014-07-26 18:23   ` Volker Armin Hemmann
2014-07-26 18:27     ` Mick
2014-07-26 19:07       ` J. Roeleveld
2014-07-27 10:49     ` Marc Stürmer
2014-07-27 11:05       ` Dale
2014-07-26 22:55 ` walt
2014-07-26 23:03   ` Volker Armin Hemmann
2014-07-26 23:07   ` Rich Freeman
2014-07-27  0:25     ` Volker Armin Hemmann
2014-07-27  6:00   ` Edward MN
2014-07-29 18:18     ` Frank Steinmetzger
2014-07-29 22:50       ` Volker Armin Hemmann
2014-07-31 10:37         ` Frank Steinmetzger
2014-07-31 16:40           ` Volker Armin Hemmann
2014-07-30  9:14       ` Edward M
2014-07-30 10:14         ` Volker Armin Hemmann [this message]
2014-07-30 11:25           ` Rich Freeman
2014-07-30 16:33             ` Volker Armin Hemmann
2014-07-30 10:16         ` Volker Armin Hemmann
2014-07-30 19:17           ` Edward M

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=53D8C56E.4010305@googlemail.com \
    --to=volkerarmin@googlemail.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