SUMMARY: Sun Blade 2000 crash with Fatal Error

I had several replies, asking for further information.  The intent 
seemed to be to gather more information; that somehow it the host wasn't 
logging enough or to the right place.  However, this just appears to be 
all that is logged or reported, even on the console.

So, as far as the error messages, I'm considering this an unsolved mystery.

However, I did reinstall the host with Solaris 10 10/08 and used zfs for 
the root file system.  It's been up for almost 7 days now.  While not 
out of the woods, I'm cautiously optimistic.  If it crashes like this 
again, we'll just put it out to pasture.  Perhaps, though, something was 
buggered with the previous OS install.

thanks for all those who helped.

Tom Lieuallen
Oregon State University

Tom Lieuallen wrote:
> We have a Sun Blade 2000 that has started crashing lately, sometimes 
> multiple times per day.  There are no error messages reported in dmesg 
> or /var/adm/messages.  No report of why it crashed during the following 
> boot.  No core dumps or crash dumps.
> 
> We finally hooked it up to a serial console.  When it crashes, we get 
> these messages:
> 
> Fatal Error reported by: (Cpu0) (Cpu1)
> CPU0 AFSR: 8000000000000  AFAR: 7ffec002030
> CPU1 AFSR: 8000000000000  AFAR: 40004602000
> Probing system devices
> 
> Fatal Error reported by: (Cpu0) (Cpu1)
> CPU0 AFSR: 8000000000000  AFAR: 7ffec002030
> CPU1 AFSR: 8000000000000  AFAR: 40004602000
> 
> Every time, just those two blocks.  And always (so far) the same #'s for 
> AFSR and AFAR.
> 
> I've been googling, but other people with anything similar to this are 
> blessed with having more error messages before or after this.  Can 
> anyone decipher this?
> 
> Thank you for any ideas.
> 
> Tom Lieuallen
> Oregon State University
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers