From: John Gilmore <gnu@toad.com>
To: Chris Torek <torek@torek.net>, gnu@toad.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] ECC memory
Date: Mon, 06 Jul 2020 16:23:37 -0700 [thread overview]
Message-ID: <23548.1594077817@hop.toad.com> (raw)
In-Reply-To: <202007061651.066GpW9s048139@elf.torek.net>
Chris Torek <torek@torek.net> wrote:
> I keep thinking I'll replace it with a new box that does have ECC,
> but haven't gotten around to it yet. I see some consumer-priced
> AMD CPUs have at least theoretical ECC support but I haven't found
> anything that says the ECC actually works, and have seen a few
> articles that hint that it doesn't.
All the AMD Ryzen CPUs and chipsets have built-in ECC. It's easy since
the CPU pins talk directly to main memory. This is one among thousands
of reasons to avoid buying Intel CPUs.
The machine I'm typing on has ECC memory, and I bought it in 2019. You
have to pick a motherboard that wasn't designed by dolts. (I got the
Gigabyte Aorus "AX-370-GAMING5", which of course is no longer
manufactured.) And you have to spend an extra $5 or $10 on your DIMMs.
Get the motherboard maker's "Qualified Vendor List", e.g.:
http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-gaming5_pinnacle_v4.pdf
Be sure there *are* some approved ECC dimms on the list. Buy those.
You may or may not have to fiddle something in the BIOS settings.
Check dmesg when you first boot the machine (booting the installer is
fine). Make sure the Linux kernel sees the DIMMS, isn't subverted by
the BIOS, and understands the CPU/memory control registers. When it
works, you'll see something like:
[ 0.180161] EDAC MC: Ver: 3.0.0
[ 9.389338] EDAC amd64: Node 0: DRAM ECC enabled.
[ 9.389339] EDAC amd64: F17h detected (node 0).
[ 9.389375] EDAC MC: UMC0 chip selects:
[ 9.389376] EDAC amd64: MC: 0: 0MB 1: 0MB
[ 9.389376] EDAC amd64: MC: 2: 4096MB 3: 4096MB
[ 9.389378] EDAC MC: UMC1 chip selects:
[ 9.389379] EDAC amd64: MC: 0: 0MB 1: 0MB
[ 9.389379] EDAC amd64: MC: 2: 4096MB 3: 4096MB
[ 9.389380] EDAC amd64: using x8 syndromes.
[ 9.389380] EDAC amd64: MCT channel count: 2
[ 9.389422] EDAC MC0: Giving out device to module amd64_edac controller F17h: DEV 0000:00:18.3 (INTERRUPT)
[ 9.389428] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV 0000:00:18.0 (POLLED)
[ 9.389429] AMD64 EDAC driver v3.5.0
Success! Non-flaky main memory in a PC clone! Cost: about $50 plus
paying attention.
John
next prev parent reply other threads:[~2020-07-06 23:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 9:09 [TUHS] VFS prior to 1984 Paul Ruizendaal
2020-06-23 14:01 ` Larry McVoy
2020-06-23 15:12 ` Clem Cole
2020-06-23 15:55 ` Rich Morin
2020-06-23 20:38 ` Rob Pike
2020-06-23 20:57 ` Larry McVoy
2020-06-24 5:14 ` arnold
2020-06-24 21:08 ` Dave Horsfall
2020-06-24 19:30 ` Clem Cole
2020-06-24 19:36 ` Larry McVoy
2020-06-25 6:52 ` Rob Gingell
2020-07-05 0:05 ` Dave Horsfall
2020-07-05 0:16 ` Larry McVoy
2020-07-06 4:42 ` Dave Horsfall
2020-07-06 16:51 ` Chris Torek
2020-07-06 23:23 ` John Gilmore [this message]
2020-07-07 1:07 ` Bakul Shah
2020-07-05 1:43 ` Clem Cole
2020-07-05 14:43 ` Larry McVoy
2020-07-05 18:40 ` Arthur Krewat
2020-07-05 20:08 ` Clem Cole
2020-07-05 20:42 ` John Cowan
2020-07-05 21:04 ` Clem Cole
2020-07-05 21:14 ` Dan Cross
2020-06-24 16:51 ` Anthony Martin
2020-06-24 17:31 ` Anthony Martin
2020-06-24 18:31 ` Paul Ruizendaal
2020-06-25 0:56 ` Rob Gingell via TUHS
2020-06-25 4:15 ` [TUHS] Oh, things were very different Rich Morin
2020-06-25 15:45 ` Lawrence Stewart
2020-06-25 16:24 ` Warner Losh
2020-06-25 17:57 ` Arthur Krewat
2020-06-25 20:22 ` Dave Horsfall
2020-06-25 20:42 ` Michael Kjörling
2020-06-25 20:49 ` Clem Cole
2020-06-26 0:48 ` Dave Horsfall
2020-06-24 19:05 ` [TUHS] VFS prior to 1984 Paul Ruizendaal
2020-06-24 20:27 ` Derek Fawcus
2020-06-24 21:33 ` Greg A. Woods
2020-06-25 0:45 ` Adam Thornton
2020-06-25 19:40 ` Greg A. Woods
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=23548.1594077817@hop.toad.com \
--to=gnu@toad.com \
--cc=torek@torek.net \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).