(Courriels de diversion: <aviserait@mesestimee-recachettes.com> <usurperas@nabot-affreter.com> <nicherai@spolierais-assignerions.com> <sablier@surexcitant-rassoyant.com> <mobiliserai@espacerons-croquee.com> <dedommagees@boutonnerez-decante.com> <desertaient@grippent-devront.com> <enclume@reconcilierez-inserent.com> <gares@egrenerais-infiltree.com> <inattentive@falsification-fertilisant.com> )
alors memtest ne fais que reporté les erreurs, en effet.
Je n'ai jamais entendu dire qu'on pouvait corriger ces erreurs,
On ne peut pas corriger les erreurs bien entendu mais il y a un module du noyau qui s'appelle bad ram et qui permet de pallier le problème. Quand les adresses qui posent problème sont clairement identifiées ce qui n'est pas le cas avec le test 5 :(
*Test 5 [Block move, 64 moves]*
This test stresses memory by using block move (movsl) instructions
and is based on Robert Redelmeier's burnBX test. Memory is
initialized with shifting patterns that are inverted every 8 bytes.
Then 4mb blocks of memory are moved around using the movsl
instruction. After the moves are completed the data patterns are
checked. Because the data is checked only after the memory moves are
completed it is not possible to know where the error occurred. The
addresses reported are only for where the bad pattern was found.
Since the moves are constrained to a 8mb segment of memory the
failing address will always be less than 8mb away from the reported
address.
_/*Errors from this test are not used to calculate BadRAM patterns.*/_
-------------------------------------------------------------------- Les listes de diffusion occultes: <URL:http://www.CULTe.org/listes/>