Re: "Hard memory error" -- where?

[Michael Lorenz <macallan%netbsd.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Aug 13, 2008, at 5:09 AM, Hauke Fath wrote:

> my trustworthy ss20 crashed yesterday with
>
> Aug 12 19:19:12 pizza /netbsd: store buffer copy-back failure at  
> 0x40332ed4. Retrying...
> Aug 12 19:19:12 pizza /netbsd: memory fault: type  
> 43sfsr=9014<SB,PERR=0,UC,LVL=0,AT=0,FT=5> sfva=0x40332ed4
> Aug 12 19:19:12 pizza /netbsd: panic: hard memory error
> Aug 12 19:19:12 pizza /netbsd: syncing disks...
>
> -- I had extended it with a few more memory modules a month or  
> three ago. It wasn't even hot that day, and the machine does not  
> have any internal drives; 448 MB of RAM though, and 2x SM71.
>
> Is there any way to learn from the panic message _which_ module  
> displays the hard error?

Not without the fault's physical address.

> Or any memory test tool that would provide module information?

Yes, the firmware will do just that.
IIRC all you need to do is to run 'selftest' on the /memory node. I'm  
sure there's an alias for it ( test-memory I think ) but I'm not 100%  
sure of its exact spelling ( might be memory-test or memtest or  
something - try the help command ). Also, I'm not sure if you need to  
change the memtest-megs# PROM variable ( I think it only tells the  
firmware how much memory to test on startup but I'm not sure if it  
has any influence on memory checks run by hand ).
Most OBP versions will tell you outright which slot contains the  
faulty module. Some others will at least give you a physical address,  
you may need the SS20 Service Manual to translate that into a slot  
number ( was available from sun.com last time I checked, if they  
pulled it I can mail you the pdf )

have fun
Michael



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBSKLrdspnzkX8Yg2nAQJBfgf/ftT+pyJ6p6xxaXib97FOt5kcW7MVXaDF
aTdA/KCasCnbB8+8HVST75YFoxMieazxXdy3s0AFQfWRFBas0LNDt00nWNFqhwm3
RdwiaRql3lR7k2iC3h3qb+AWyjPbFHUh3YeWI17Y+GRms3kpegZvhf68hmE3K0d4
hbOuLVd74jiKa/ffbjtxEKLPEUumAL/zVHDDoVKxGzCqVpSHHGb0Smo8yjX1zeH1
Pq6NcRzELj+BKKT7Wqew8Q1D0gJ8TVORhJyB0C6WriETYaLlvy5IhMPDJOGCJX3l
FewL8PGI8hf4zt8/iczznmwFHb3lBKxjSFi7OKzJOEiqWp8yLP8WYw==
=MpsA
-----END PGP SIGNATURE-----