Message from syslogd@server at Sep 14 11:35:59 ...
kernel:[Hardware Error]: MC4 Error (node 1): DRAM ECC error detected on the NB.
Message from syslogd@server at Sep 14 11:35:59 ...
kernel:[Hardware Error]: Error Status: Corrected error, no action required.
Message from syslogd@server at Sep 14 11:35:59 ...
kernel:[Hardware Error]: CPU:6 (10:8:0) MC4_STATUS[Over|CE|MiscV|-|AddrV|CECC]: 0xdc00400021080813
Message from syslogd@server at Sep 14 11:35:59 ...
kernel:[Hardware Error]: MC4_ADDR: 0x000000082b185760
Message from syslogd@server at Sep 14 11:35:59 ...
kernel:[Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: SRC (no timeout)
We just wish we could know what module caused it. This may not even be an issue as sometimes incorrect timings are what cause issues like this.
ecc, errors, actionmessage, syslogd, server, sep, kernel, hardware, mc, node, dram, detected, nb, corrected, cpu, _status, ce, miscv, addrv, cecc, xdc, _addr, cache, gen, mem, io, tx, rd, proc, src, timeout, module, incorrect, timings,