Home Forum Software discussion ECC RAM

Tagged: 

This topic contains 1 reply, has 2 voices, and was last updated by  nanasi 2 months, 1 week ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #7369

    skodde
    Participant

    Does anyone use an ECC RAM module and they actually see it active as such on Linux (i.e. via dmesg, edac-util, dmidecode, etc.)?

    I just installed a CT16G4WFD8266 module and it’s not recognized as ECC (dmidecode shows 64 bits of total width instead of the expected 72). Also, no EDAC memory controller is found on the system.

    Kernel version is 4.20.12 with the following options enabled:

    CONFIG_EDAC_SUPPORT=y
    CONFIG_EDAC=y
    CONFIG_EDAC_LEGACY_SYSFS=y
    CONFIG_EDAC_DEBUG=y
    CONFIG_EDAC_GHES=y
    CONFIG_EDAC_THUNDERX=y
    CONFIG_EDAC_XGENE=y

    Firmware is EDK II compiled using:

    atf-v1.5-armada-18.09
    binaries-marvell-armada-18.06
    uefi-2.7-armada-18.09
    mv_ddr-armada-18.12

    Is this expected or ECC RAM is indeed not (yet?) supported?

    #7373

    nanasi
    Participant

    Hi.
    If ECC is initialized correctly, the next message will appear.

    mv_ddr: scrubbing memory...
    mv_ddr: completed successfully

    There is no easy way to check whether ECC is working.
    Since there is no open source memory controller driver for A8k/A7k.(AFAIK)

    In addition, the memory width is hardcoded into UEFI source.
    From dmidecode manpage:

    BUGS
           More often than not, information contained in the DMI tables is inaccurate, incomplete or simply wrong.
Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Technical specification tables can not be displayed on mobile. Please view on desktop