Linus Torvalds Calls Out Intel for ECC Memory Market Stagnation

[L'Eliminateur]

Wait. What? Are each of those table entries an indication where data was corrupted? Holy crap!

What is your data server doing that it is encountering that many memory errors?

The server does not really need to be doing "anything" for memory errors to pop, it could be a single write/read to an address that's bad and it will trigger the ECC.
You could be "idling" in desktop and the errors will trigger all the same, it all depends on what address is being used(maybe it's at the beginning of the array, maybe it's at the end and you don't "see" it until the ram gets full)
those table entries are indeed data corruption events SOLVED by the ECC(so they're transparent to the OS)

 

[trparky]

If one of my systems were experiencing those kinds of memory errors (I don't run ECC memory) the odds of it affecting something important, like I don't know... the kernel, gets higher. If I was in a casino, I'd bet on it.

I'd say time to replace that RAM.

 

[cst1992]

Wouldn't mandating ECC drive the price of modules way up?

 

[Kapone33]

Hi,
Yeah 3200c22 or even c16 is no prize, oc ability is not good.
AMD is getting better with memory oc but still same old story only using 2 sticks and 4 sticks still way more handicapped than Intel systems are.

Well I have 4 sticks on my X570 running at 3600 MHZ. Instead of handicapped you should say more responsive.

 

[L'Eliminateur]

If one of my systems were experiencing those kinds of memory errors (I don't run ECC memory) the odds of it affecting something important, like I don't know... the kernel, gets higher. If I was in a casino, I'd bet on it.

I'd say time to replace that RAM.

Well.. yes, that's what you do, you buy/warranty the replacement and change it as soon as convenient, but meanwhile the errors will continue that's why you see soo many errors in the log.
I've had a customer that had a RAM error but was much more intermittent (probably a high address) and he ran like that for months