Xref: utzoo comp.sys.mac.misc:3251 comp.sys.mac.programmer:17458
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cica!iuvax!ux1.cso.uiuc.edu!midway!ellis.uchicago.edu!dwal
From: dwal@ellis.uchicago.edu (David Walton)
Newsgroups: comp.sys.mac.misc,comp.sys.mac.programmer
Subject: Re: MEMORY FAULTS - any way to check ram for intermittent faults??
Keywords: memory ram fault check
Message-ID: <1990Sep13.154744.2277@midway.uchicago.edu>
Date: 13 Sep 90 15:47:44 GMT
References: <1990Sep11.174118.12194@Neon.Stanford.EDU> <615@keele.keele.ac.uk> <1990Sep12.185459.15694@ux1.cso.uiuc.edu>
Sender: news@midway.uchicago.edu (News Administrator)
Distribution: comp
Organization: U. Chicago Computing Organizations, Academic and Public Comp.
Lines: 36

In article <1990Sep12.185459.15694@ux1.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes:

>02 is an address error; the 68000 tried to access a word or longword at
>an odd address, which it can't do.  Chances are the program is using an
>invalid pointer.  Chances further are that this pointer is 0, and that
>your mac dies because the four bytes starting at location 0 are odd.
>
>If nobody is purposefully writing to location 0 (and no one should),
>location 0 will have random junk in it; this is probably why you have
>a problem sometimes and not others.

...

>Try saying "sm 2 0101", continuing (what's the command for that in the
>mini-monitor?) and running the program.  If my guesses are correct, it will
>fail every time.

Um...I think that's a typo.  You mean sm _0_ 0101, don't you?  You
don't want to put this at memory location 2, you want it at 0.

The proper sequence is

	>sm 0 0101 (or any odd four-byte number)
	>g

">" is the ROM debugger prompt.

>Steve Dorner, U of Illinois Computing Services Office




--
David Walton            Internet: dwal@midway.uchicago.edu
University of Chicago   {  Any opinions found herein are mine, not  }
Computing Organizations {  those of my employers (or anybody else). }