4 ms·
If you're on Linux, dmesg containing EDAC MC0: Giving out device to module amd64_edac is a pretty reliable indication that ECC is working. See my blog post
by sunshowers 1y ago
If you're on Linux, dmesg containing
EDAC MC0: Giving out device to module amd64_edac
is a pretty reliable indication that ECC is working.
See my blog post about it (it was top of HN): https://sunshowers.io/posts/am5-ryzen-7000-ecc-ram/ https://sunshowers.io/posts/am5-ryzen-7000-ecc-ram/
- oneshtein 1y agoMy `dmesg` tells: EDAC MC0: Giving out device to module igen6_edac controller Intel_client_SoC MC#0: DEV 0000:00:00.0 (INTERRUPT) EDAC MC1: Giving out device to module igen6_edac controller Intel_client_SoC MC#1: DEV 0000:00:00.0 (INTERRUPT) but `dmidecode --type 16` says: Error Correction Type: None Error Information Handle: Not Provided
- sunshowers 1y agoTo be honest I don't know how Intel works, my post is limited to AMD.
- c0l0 1y agoAre you sure you have ECC-capable DIMM installed? What does find /sys/devices/system/edac/mc/mc0/csrow* -maxdepth 1 -type f -exec grep --color . {} + report?
- oneshtein 1y agoAFAIK, I have 2x DDR5 non-ECC memory (`dmidecode --type 17` says Samsung M425R1GB4BB0-CQKOL). Your command tells about SECDEC (single bit error correction, double bit error detection). /sys/devices/system/edac/mc/mc0/csrow0/ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ch0_dimm_label:MC#0_Chan#0_DIMM#0 /sys/devices/system/edac/mc/mc0/csrow0/size_mb:8192 /sys/devices/system/edac/mc/mc0/csrow0/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ue_count:0 /sys/devices/system/edac/mc/mc0/csrow0/mem_type:Unbuffered-DDR3 /sys/devices/system/edac/mc/mc0/csrow0/edac_mode:SECDED /sys/devices/system/edac/mc/mc0/csrow0/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ch1_dimm_label:MC#0_Chan#1_DIMM#0 /sys/devices/system/edac/mc/mc0/csrow0/dev_type:x16 > find /sys/devices/system/edac/mc/mc0/csrow* -maxdepth 1 -type f -exec grep --color . {} + It looks like DDR5 supports SECDEC by default. :-/