3 ms·
I agree with the "if a machine passes a memtest scrub for 24+ hours then it's probably fine" in theory. Sadly in practice I regularly find dimms that generate
by sliken 4y ago
I agree with the "if a machine passes a memtest scrub for 24+ hours then it's probably fine" in theory. Sadly in practice I regularly find dimms that generate errors plenty of errors, and test find with memtest.
Not sure why, maybe it's the different memory access patterns, maybe bad dimms are more sensitive to repeated accesses below the rowhammer level, that healthy dimms have no problems with.
I find things like make -j for large builds MUCH better at finding memory errors than memtest.
- paulmd 4y agoyep also true. maybe you could build some kind of tooling around this, if builds are deterministic (or you do something like pgbench with a deterministic workload/script) then there's no reason you can't check the output in addition to very obvious segfault failures.
- sliken 4y agoYears ago the GCC FAQ had an entry for a strange compiler error, that pretty much was only triggered by overclocking or memory errors. I just looked and couldn't find it.