[Sunhelp] Decypering panic messages

[Wayn Schmieder]

The error message is indicating multiple SIMMS, SIMM U0901 U0902 U0903
U0904.  I dont think this is likely, my guess with out breaking out the
status register  (AFSR) is that you have some sort of memory map problem.
This would also be indicated by "privileged" in the error message.  The type
of box would be a factor in determining if its a motherboard or CPU.   A
quick and dirty check would be to do a power up while holding STOP D, this
will initiate a fairly extensive set of power up diags.

----- Original Message -----
From: "Dale Ghent" <daleg at elemental.org>
To: <sunhelp at sunhelp.org>
Sent: Tuesday, May 16, 2000 12:37 PM
Subject: Re: [Sunhelp] Decypering panic messages


> On Tue, 16 May 2000, Bill Bradford wrote:
>
> | Would y'all say this is bad CPU, bad RAM, or both?
> |
> | # grep panic messages
> | May 15 18:30:23 oradev1 unix: panic[cpu0]/thread=0x30023e80: CPU0
Multiple
> | Privileged UE Error: AFSR 0x00000001 80300000 AFAR 0x00000000 81007050
> | SIMM U0901 U0902 U0903 U0904
>   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> What kind of box is this? It's calling out a whole bank of slots.
>
> I ran into this same problem last week on a e4500. It turned out that the
> Kingston RAM installed on all but one of the CPU boards was
> defective. Replaced it with Sun barcode RAM and things were great. I was
> able to reliably reproduce the panic running the VTS kmem test.
>
> If you have a mix of manufacturers for your DIMMS then try making
> everything from the same maker, or better yet, try all Sun.
>
> /dale
>
> _______________________________________________
> SunHELP maillist  -  SunHELP at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/sunhelp
>