- 08 Aug, 2014 1 commit
-
-
Xian Li authored
Closes #1614
-
- 21 Jan, 2013 1 commit
-
-
antirez authored
This closes issue #859, thanks to @erbenmo.
-
- 29 Nov, 2012 1 commit
-
-
antirez authored
1) We no longer test location by location, otherwise the CPU write cache completely makes our business useless. 2) We still need a memory test that operates in steps from the first to the last location in order to never hit the cache, but that is still able to retain the memory content. This was tested using a Linux box containing a bad memory module with a zingle bit error (always zero). So the final solution does has an error propagation step that is: 1) Invert bits at every location. 2) Swap adiacent locations. 3) Swap adiacent locations again. 4) Invert bits at every location. 5) Swap adiacent locations. 6) Swap adiacent locations again. Before and after these steps, and after step 4, a CRC64 checksum is computed. If the three CRC64 checksums don't match, a memory error was detected.
-
- 21 Nov, 2012 1 commit
-
-
antirez authored
-
- 08 Nov, 2012 1 commit
-
-
antirez authored
-
- 27 Apr, 2012 1 commit
-
-
antirez authored
-
- 12 Apr, 2012 1 commit
-
-
antirez authored
-
- 11 Apr, 2012 1 commit
-
-
antirez authored
-
- 19 Mar, 2012 1 commit
-
-
antirez authored
-
- 18 Mar, 2012 3 commits
-
-
antirez authored
More memory tests implemented. Default number of iterations lowered to a more acceptable value of 50.
-
antirez authored
-
antirez authored
Number of iteration of --test-memory is now 300 (several minutes per gigabyte). Memtest86 and Memtester links are also displayed while running the test.
-
- 16 Mar, 2012 2 commits