Bug#556365: Please enable CONFIG_MEMTEST
As a matter of fact MEMTEST is a quite useful feature.
We ask to enable it not for what it cannot do, but for what it can.
For example ECC in hardware is not useless even though it doesn't
catch all possible errors.
As I demonstrate in
MEMTEST successfully detects and isolate problems.
It write 17 patterns, not one.
Bootable memtest86+ utility cannot be a substitute for in-kernel
feature in production/mission critical systems which cannot be stopped
to perform memory test.
Memory modules broke unexpectedly.
When it happen, there is a time when data corruption occur before
MEMTEST can proactively and automatically isolate such problem and
therefore protect from silent data corruption.
Real MEMTEST's value in preventing or minimizing damage from
undetected memory failure which [typically] lead to silent data
Particularly storage systems will benefit from it, because MEMTEST
MEMTEST is a powerful feature despite its limitations.
Data integrity matters - MEMTEST is much better than nothing.
Enabling It cost almost nothing - it will be very handy to have it
Enabling MEMTEST is safe because It should be activated with boot-time
P.S. I've seen cases when memory corruption was discovered months
later. Obviously it is very hard to say when it happened and therefore
evaluate how much damage is done.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com
Archive: AANLkTi=3Xsvukdu_B+n7THK7UgGnS2n+Y+kK7cMR9f=7@mail .gmail.com">http://lists.debian.org/AANLkTi=3Xsvukdu_B+n7THK7UgGnS2n+Y+kK7cMR9f=7@mail .gmail.com