Summary: Sparc 20 keeps rebooting with fatal system fault: sipr=40000000

Hi,
    Special thanks to the following people for their
prompt response -------------
Paul Theodoropoulos, Parkins Larye , Sandwich Maker,
Jaehne Richard and Sanchia Baker

Most of the responses suggested that the problem
seemed to originate due to CPU problem as highlighted
from the message log 
fatal system fault: sipr=40000000
Async Fault from module 0: afsr b302000 afar=8b78580

Since both systems are located in the same quadrant, 
power fluctuations or some static discharge seem to be
the most likely cause.

In retrospect I changed the defective CPU's on both
the systems. This seems to have resolved the problem
as the systems have been quite stable after that. 

Regards,
Amit 

> Summary of the problem I had seen ----------------

> >I have two Sparc 20 stations running Solaris 2.6.
> >Recently both the systems started rebooting by
> >themselves. The messages captured from one of the
> >station are as follows -
> >
> >dump on /dev/dsk/c0t3d0s1 size 524372K
> >fatal system fault: sipr=40000000
> >Async Fault from module 0: afsr b302000
> afar=8b78580
> >aerr0 0 aerr1=0
> >MMU sfsr=b302000: No Error on user data fetch at
> level
> >0
> >         M-Bus Undefined Error
> >MXCC Error Register:
> >panic: Fatal Asynchronous Fault
> >
> >syncing file systems...WARNING: tmp_putapage: err 5
> >
> >WARNING: tmp_putapage: err 5
> >
> >  569WARNING: tmp_putapage: err 5
> >WARNING: tmp_putapage: err 5


__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers