Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Apr 1996 10:55:10 -0700 (PDT)
From:      "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
To:        scrappy@ki.net (Marc G. Fournier)
Cc:        davidg@Root.COM, current@freebsd.org
Subject:   Re: Can someone explain why...
Message-ID:  <199604141755.KAA23202@GndRsh.aac.dev.com>
In-Reply-To: <Pine.BSI.3.92.960414011550.200E-100000@freebsd.ki.net> from "Marc G. Fournier" at "Apr 14, 96 01:18:24 am"

next in thread | previous in thread | raw e-mail | index | archive | help
> On Sat, 13 Apr 1996, David Greenman wrote:
> 
> >    Simple - you have a memory problem and the part of memory that is caching
> > gcc is wrong. It just happens that the code involved is only exercised when
> > you use -O. It's easy to test this: just reboot your computer and see if the
> > problem goes away. If it persists, then you might have a corrupt gcc binary.
> >
> 	Okay, that works for me...is there anything I can do to a SIMM to
> test it *before* I change it?  Or to test the new one before I even put it
> in?  Trial and Error doesn't seem to be an effective way of fixing this
> problem :(

Find a memory supplier that has a SIMM tester, that is the only true and
accurate way to rule a SIMM good or bad, sans replacing it.   I know these
folks are not easy to find, but check with your local PC distributors
(not retailers), they sometimes have one around.

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604141755.KAA23202>