SUMMARY: BAD trap problem on SunBlade/Sol8

From: Christian Iseli <chris_at_ludwig-alpha.unil.ch>
Date: Tue Feb 05 2002 - 03:22:25 EST
Hi,

I wrote: 

> One of my users has a Sun Blade 100/Solaris 8 that just started crashing 
> several times.  This is what I get in the log.  The addr= field looks kinda 
> weird...  What's going on ?

> Jan 10 16:45:50 sib-sun5 savecore: [ID 570001 auth.error] reboot after
>  panic: BAD TRAP: type=34 rp=2a1005257e0 addr=90baddcafe mmu_fsr=0
> Jan 10 19:04:56 sib-sun5 savecore: [ID 570001 auth.error] reboot after
>  panic: BAD TRAP: type=34 rp=2a1007457e0 addr=90baddcafe mmu_fsr=0
> Jan 10 19:08:39 sib-sun5 savecore: [ID 570001 auth.error] reboot after
>  panic: BAD TRAP: type=31 rp=2a100745040 addr=100000008 mmu_fsr=0
> Jan 10 19:11:56 sib-sun5 savecore: [ID 570001 auth.error] reboot after
>  panic: BAD TRAP: type=34 rp=2a1007457e0 addr=baddcafe mmu_fsr=0

This turned out to be a hardware problem.  Sun service came in, changed the 
CPU, and that fixed it.

Thanks to Casper and Vinnie for their help.

Regards,
					Christian
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Tue Feb 5 02:23:11 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:33 EST