Segmentation Faults - Memtest

Hast Du Probleme mit Hardware, die durch die anderen Foren nicht abgedeckt werden? Schau auch in den "Tipps und Tricks"-Bereich.
Antworten
Benutzeravatar
tani
Beiträge: 28
Registriert: 19.08.2003 18:58:50

Segmentation Faults - Memtest

Beitrag von tani » 07.09.2003 23:20:09

Hi,

ich habe ein Problem mit meinem Server. Und zwar bringt er mir seit heute ab und an Segmentation Faults, zum Beispiel bei "apt-get install ..."
Aus diesem Grund habe ich mal memtest laufen lassen und folgendes Ergebnis erhalten:

Code: Alles auswählen

root@server:~# memtest mem all
.
. (Ausgabe gekürzt)
.
Unable to malloc 3044016128 bytes.
Unable to malloc 3039821824 bytes.
Unable to malloc 3035627520 bytes.
Unable to malloc 3031433216 bytes.
Unable to malloc 3027238912 bytes.
Unable to malloc 3023044608 bytes.
Unable to malloc 3018850304 bytes.
Unable to malloc 3014656000 bytes.
Unable to malloc 3010461696 bytes.
Unable to malloc 3006267392 bytes.
Unable to malloc 3002073088 bytes.
Unable to malloc 2997878784 bytes.
.
.
.
Allocated 358010880 bytes...trying mlock...failed:  insufficient resources.
Allocated 356958208 bytes...trying mlock...failed:  insufficient resources.
Allocated 355905536 bytes...trying mlock...failed:  insufficient resources.
Allocated 354852864 bytes...trying mlock...failed:  insufficient resources.
Allocated 353800192 bytes...trying mlock...failed:  insufficient resources.
Allocated 352747520 bytes...trying mlock...failed:  insufficient resources.
Allocated 351694848 bytes...trying mlock...failed:  insufficient resources.
Allocated 350642176 bytes...trying mlock...failed:  insufficient resources.
Allocated 349589504 bytes...trying mlock...failed:  insufficient resources.
Allocated 348536832 bytes...trying mlock...failed:  insufficient resources.
Allocated 347484160 bytes...trying mlock...failed:  insufficient resources.
Allocated 346431488 bytes...trying mlock...failed:  insufficient resources.
Allocated 345378816 bytes...trying mlock...failed:  insufficient resources.
Allocated 344326144 bytes...trying mlock...failed:  insufficient resources.
Allocated 343273472 bytes...trying mlock...failed:  insufficient resources.
Allocated 342220800 bytes...trying mlock...failed:  insufficient resources.
Allocated 341168128 bytes...trying mlock...failed:  insufficient resources.
Allocated 340115456 bytes...trying mlock...failed:  insufficient resources.
Allocated 339062784 bytes...trying mlock...failed:  insufficient resources.
Allocated 338010112 bytes...trying mlock...failed:  insufficient resources.
Allocated 336957440 bytes...trying mlock...failed:  insufficient resources.
Allocated 335904768 bytes...trying mlock...failed:  insufficient resources.
Allocated 334852096 bytes...trying mlock...success.  Starting tests...

Testing 334848000 bytes at 0x40301000 (4088 bytes lost to page alignment).

Run    1:
  Test  1:         Stuck Address:  Testing...Passed.
  Test  2:          Random value:  Setting...Testing...Passed.
  Test  3:        XOR comparison:  Setting...Testing...Passed.
  Test  4:        SUB comparison:  Setting...Testing...Passed.
  Test  5:        MUL comparison:  Setting...Testing...Passed.
  Test  6:        DIV comparison:  Setting...Testing...Passed.
  Test  7:         OR comparison:  Setting...Testing...Passed.
  Test  8:        AND comparison:  Setting...Testing...Passed.
  Test  9:  Sequential Increment:  Setting...Testing...Passed.
  Test 10:            Solid Bits:  Testing...Passed.
  Test 11:      Block Sequential:  Testing...  24
FAILURE: 0x18181818 != 0x1c181818 at offset 0x009d200e.
Skipping to next test...
  Test 12:          Checkerboard:  Testing...  41
FAILURE: 0xaaaaaaaa != 0xaeaaaaaa at offset 0x007d580e.
Skipping to next test...
  Test 13:            Bit Spread:  Testing...  19
FAILURE: 0x00280000 != 0x04280000 at offset 0x00a6e80e.
Skipping to next test...
  Test 14:              Bit Flip:  Testing... 101
FAILURE: 0x00001000 != 0x04001000 at offset 0x0014f40e.
Skipping to next test...
  Test 15:          Walking Ones:  Testing...   2
FAILURE: 0x00000004 != 0x04000004 at offset 0x0014f40e.
Skipping to next test...
  Test 16:        Walking Zeroes:  Testing...Passed.
Run    1 completed in 659 seconds (5 tests showed errors).
Das sieht in meinen Augen nicht gut aus, deshalb habe ich testweise memtest auf meiner Workstation laufen lassen - mit ähnlichem Ergebnis. Dort bekomme ich diese Seg-faults aber nicht...

Nun die Frage, ist obige Ausgabe ein sicheres Indiz für kaputten RAM oder gibt es noch andere Ursachen?

Beste Grüße...
Linux is like a Tepee, no Gates, no Windows and Apache inside...

Benutzeravatar
pdreker
Beiträge: 8298
Registriert: 29.07.2002 21:53:30
Lizenz eigener Beiträge: MIT Lizenz
Wohnort: Nürnberg

Beitrag von pdreker » 08.09.2003 04:28:40

Ich würde memtest86 (http://www.memtest86.com) 'mal über Nacht laufen lassen (Bootdiskettenversion!). Wenn das auch Fehler findet, dann solltest Du erstmal mit anderen RAMs testen, ob es die Riegel oder das Board sind....

Patrick
Definitely not a bot...
Jabber: pdreker@debianforum.de

Antworten