On 11/28/2012 09:24 AM, Gary Dale wrote:
I'm afraid I can't really answer that. All I can do is repeat that
when MemTest86+ reports an error, it is a good indication that you
have a problem. I've seen this on systems where MemTest86+ reported
only a few problems but the computer locked up intermittently in use.
Replacing the memory with ones that MemTest86+ passed cured the lockups.
I also have a motherboard that was running reliably for 2 years then
started locking up. MemTest86+ reported that the memory was OK but
Klaus Knopper's suggestion that it was a chipset problem seemed
reasonable since the problem occurred during operations where both
memory and disk access were high. The manufacturer meanwhile replaced
the board three times with repaired boards all of which displayed the
same problem. Their repair testing tests components in isolation,
which usually is OK but in this case failed to trigger the real problem.
The problem seems to be more common on modern hardware than on older
systems. I hadn't seen it before but now have seen it on a couple
different motherboards. Slowing down the memory access cures it.
Well, it's not just Memtest86+ that is reporting errors. I decided to
get a second opinion, as it were, and installed memtester from the
Debian repository. I let it run through 5 cycles of its tests. I have
included the results of the first loop below. The other loops were
similar. None of the five loops found any errors in the first 9 tests.
The 'Checkerboard' test found errors in 2 of the 5 tests and only the
first test found errors in the 'Waking zeros' test. As you can see, I
was testing 7GB on an 8GB system. This was running from inside an xterm
while I was cruising the web. As you can see from the results of
running 'free' while the test was going, I had under 80GB (less than 1%
of my total memory) free, so the full memory was getting a workout. I
am just having difficulty with the idea that there are this may memory
errors throughout the range of the RAM and I keep right on working with
no apparent difficulties? Others that I have talked to, who have
actually had memory go bad on them (I never have, before) say that it is
extremely obvious and normal operations are not possible. I believe the
term he used was that "the OS completely wigged out!"
Do I really have bad memory? Or is this some other kind of aberration.
Sunday is the end of my in-store return period. After that I have to
ship things back to manufacturers which is a problem if I don't really
know were the trouble lies.
free
total used free shared buffers cached
Mem: 8179084 8099244 79840 0 22292 199752
-/+ buffers/cache: 7877200 301884
Swap: 8388600 256 8388344
sudo memtester 7G 2>&1 | tee memtester.txt
memtester version 4.1.3 (64-bit)
Copyright (C) 2010 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).
pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 7168MB (7516192768 bytes)
got 7168MB (7516192768 bytes), trying mlock ...locked.
Loop 1:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : testing 1FAILURE: 0xffffffffffffffff !=
0xffffffffffffff at offset 0x04373faf.
FAILURE: 0x00000000 != 0xff00000000000000 at offset 0x04373fb0.
FAILURE: 0xffffffffffffffff != 0xffffffffffffff at offset 0x04373fb1.
FAILURE: 0x00000000 != 0xff00000000000000 at offset 0x04373fb2.
FAILURE: 0xffffffffffffffff != 0xffffffffffffff at offset 0x04373fb3.
FAILURE: 0x00000000 != 0xff00000000000000 at offset 0x04373fb4.
FAILURE: 0xffffffffffffffff != 0xffffffffffffff at offset 0x04373fb5.
FAILURE: 0x00000000 != 0xff00000000000000 at offset 0x04373fb6.
Block Sequential : testing 109FAILURE: 0x6d6d6d6d6d6d6d6d !=
0x6c6d6d6d6d6d6d6d at offset 0x001e71bf.
FAILURE: 0x6d6d6d6d6d6d6d6d != 0x6c6d6d6d6d6d6d6d at offset 0x001e71c0.
FAILURE: 0x6d6d6d6d6d6d6d6d != 0x6c6d6d6d6d6d6d6d at offset 0x001e71c1.
FAILURE: 0x6d6d6d6d6d6d6d6d != 0x6c6d6d6d6d6d6d6d at offset 0x001e71c2.
FAILURE: 0x6d6d6d6d6d6d6d6d != 0x6c6d6d6d6d6d6d6d at offset 0x001e71c3.
FAILURE: 0x6d6d6d6d6d6d6d6d != 0x6c6d6d6d6d6d6d6d at offset 0x001e71c4.
FAILURE: 0x6d6d6d6d6d6d6d6d != 0x6c6d6d6d6d6d6d6d at offset 0x001e71c5.
FAILURE: 0x6d6d6d6d6d6d6d6d != 0x6c6d6d6d6d6d6d6d at offset 0x001e71c6.
Checkerboard : testing 63FAILURE: 0x5555555555555555 !=
0xaa55555555555555 at offset 0x00740b07.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b08.
FAILURE: 0x5555555555555555 != 0xaa55555555555555 at offset 0x00740b09.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b0a.
FAILURE: 0x5555555555555555 != 0xaa55555555555555 at offset 0x00740b0b.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b0c.
FAILURE: 0x5555555555555555 != 0xaa55555555555555 at offset 0x00740b0d.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b0e.
FAILURE: 0x5555555555555555 != 0xaa55555555555555 at offset 0x00740b0f.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b10.
FAILURE: 0x5555555555555555 != 0xaa55555555555555 at offset 0x00740b11.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b12.
FAILURE: 0x5555555555555555 != 0xaa55555555555555 at offset 0x00740b13.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b14.
FAILURE: 0x5555555555555555 != 0xaa55555555555555 at offset 0x00740b15.
FAILURE: 0xaaaaaaaaaaaaaaaa != 0x55aaaaaaaaaaaaaa at offset 0x00740b16.
Bit Spread : testing 57FAILURE: 0x500000000000000 !=
0xa00000000000000 at offset 0x083c0420.
FAILURE: 0xfaffffffffffffff != 0xf5ffffffffffffff at offset 0x083c0421.
FAILURE: 0x500000000000000 != 0xa00000000000000 at offset 0x083c0422.
FAILURE: 0xfaffffffffffffff != 0xf5ffffffffffffff at offset 0x083c0423.
FAILURE: 0x500000000000000 != 0xa00000000000000 at offset 0x083c0424.
FAILURE: 0xfaffffffffffffff != 0xf5ffffffffffffff at offset 0x083c0425.
FAILURE: 0x500000000000000 != 0xa00000000000000 at offset 0x083c0426.
FAILURE: 0xfaffffffffffffff != 0xf5ffffffffffffff at offset 0x083c0427.
Bit Flip : testing 14FAILURE: 0x00000002 !=
0xff00000000000002 at offset 0x09cf90bf.
FAILURE: 0xfffffffffffffffd != 0xfffffffffffffd at offset 0x09cf90c0.
FAILURE: 0x00000002 != 0xff00000000000002 at offset 0x09cf90c1.
FAILURE: 0xfffffffffffffffd != 0xfffffffffffffd at offset 0x09cf90c2.
FAILURE: 0x00000002 != 0xff00000000000002 at offset 0x09cf90c3.
FAILURE: 0xfffffffffffffffd != 0xfffffffffffffd at offset 0x09cf90c4.
FAILURE: 0x00000002 != 0xff00000000000002 at offset 0x09cf90c5.
FAILURE: 0xfffffffffffffffd != 0xfffffffffffffd at offset 0x09cf90c6.
FAILURE: 0xfffffffffffffd != 0xfffffffffffffffd at offset 0x09d210c8.
FAILURE: 0xff00000000000002 != 0x00000002 at offset 0x09d210c9.
FAILURE: 0xfffffffffffffd != 0xfffffffffffffffd at offset 0x09d210ca.
FAILURE: 0xff00000000000002 != 0x00000002 at offset 0x09d210cb.
FAILURE: 0xfffffffffffffd != 0xfffffffffffffffd at offset 0x09d210cc.
FAILURE: 0xff00000000000002 != 0x00000002 at offset 0x09d210cd.
FAILURE: 0xfffffffffffffd != 0xfffffffffffffffd at offset 0x09d210ce.
FAILURE: 0xff00000000000002 != 0x00000002 at offset 0x09d210cf.
Walking Ones : ok
Walking Zeroes : testing 61FAILURE: 0x2000000000000000 !=
0x1000000000000000 at offset 0x083e810f.
FAILURE: 0x2000000000000000 != 0x1000000000000000 at offset 0x083e8110.
FAILURE: 0x2000000000000000 != 0x1000000000000000 at offset 0x083e8111.
FAILURE: 0x2000000000000000 != 0x1000000000000000 at offset 0x083e8112.
FAILURE: 0x2000000000000000 != 0x1000000000000000 at offset 0x083e8113.
FAILURE: 0x2000000000000000 != 0x1000000000000000 at offset 0x083e8114.
FAILURE: 0x2000000000000000 != 0x1000000000000000 at offset 0x083e8115.
FAILURE: 0x2000000000000000 != 0x1000000000000000 at offset 0x083e8116.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50b710ed.3080...@gmail.com
