Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!purdue!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!rice!sun-spots-request
From: weiser.pa@xerox.com
Newsgroups: comp.sys.sun
Subject: Re: Sun-3/60 memory errors
Message-ID: <890112-100946-12662@Xerox>
Date: 17 Jan 89 22:23:48 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 15
Approved: Sun-Spots@rice.edu
Original-Date: Thu, 12 Jan 89 10:07:49 PST
X-Sun-Spots-Digest: Volume 7, Issue 107, message 12 of 17

Jan L. Peterson writes: "Does anyone know what this message means from the
diagnostic monitor:

Memory test
  Err 2  Addr 0x00001030 Exp 0x7A972C5A
         Obs  0x5A972C5A Module 0x00000000"

I had an error like this, with changing memory addresses, on my 3/60.  In
my case, the kinds of changes were the clue: it was a particular set of
bits that were different, and be doing a little guessing about which simms
were for which address range, I identified the bad simm, checked my guess
by moving the simms around (and watched the bad address range change),
replaced the bad simm (with one from Helios), and all is now perfect.

-mark-