Bad address error - VTS

From: David Price (dprice@plugnpay.com)
Date: Wed Apr 16 2003 - 11:45:08 EDT


E3500
2.6

When running VTS the following error appears when testing memory causing VTS
to stop testing.

FATAL mem: "read() at address 0x3fffffffff800000 [Board3, Bank0,
Size=2048MB, Intlv=2, MCTL=0x8541b09, MDEC=0x80001f8000000380: ] failed (Bad
address)."

System was originally populated with 1 CPU/Memory board with 2 x 466 CPU's
and 4 Gb RAM on Board 3.

System reports no error messages on boot even with full diagnostics turned
on.

RAM from Bank 0 and Bank 1 were swapped to isolate if the problem was RAM
related.

Error message was the same. Still pointing to same board and bank.

RAM in Bank0 was then replaced.

Error message was the same.

CPU's were removed and installed on a different CPU/Memory Board and
installed in Slot3. "Suspect Board" containing only RAM was then installed
in slot 7.

Error message now changed to point to Board7, Bank0, so error does follow
board.

Earlier the system had been crashing sporadically and repeatedly with
reports of EDP Parity errors which I covered in a different POST. We are
currently unable to get system to crash despite this error being reported by
VTS.

Does anyone know what this error means ?

It would seem to be a board problem but why does the system not report any
errors on boot ? and why does the machine now seem to run fine despite the
error.

Can this type of error cause the CPU to panic and report a Parity error ?

Inquiring minds want to know.

Thank you.

Dave
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:12 EDT