SUMMARY: u60 Red State Exception

From: Trent Petrasek <tpetrasek_at_internap.com>
Date: Mon Apr 07 2003 - 17:04:19 EDT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Greetings All!!

Success! I have fixed the problem. I realize I said nothing of memory in my original post. I did, however, swap out memory several times, but it was always "used" memory. I installed four clean modules right out of the static bags and this solved the problem!

Much thanks to Roger Leonard, Gary Trail and Steven Faulconer for the memory suggestions!

Thanks all,


- ----------------------------------------------------------
 Trent Petrasek                 Internap Network Services
 Systems Engineer               IT Services
 tpetrasek@internap.com         404.302.9742

On Mon, Apr 07, 2003 at 04:34:27PM -0400, Trent Petrasek <tpetrasek@internap.com> wrote:
> 
> Greetings Sun Managers,
> 
> This morning I started work on an older model U-60 desktop system. The system has two 450 MHz cpu modules, two 256M memory modules, and two 9G drives.
> 
> When I first powered up the system, it offered many "Red State Exceptions" to me. No problem, I've seen this before on a Netra 1125 which had a CPU problem. So I yank out one of the two CPU modules and power her back up. I get the same error. Ok, I think, it must be the other CPU. So I yank out CPU 2, replacing CPU 1. No go, I get the same error. At this point I've come to the end of my experience with "red state exceptions." 
> 
> I google the problem, searching for help. There is not much out there, and the majority of it is related to CPU. Not wanting to believe I have two bad CPU modules, I hunt down and locate a third 450MHz module and drop it in the box. Unfortunately, as you may have guessed, this did not work either.
> 
> Now I'm frustrated because the problem is not readily apparent. Luckily, I have another u60 box that is down due to power problems. I borrow the motherboard from the machine, installing it into the broken u60. I populate it with working CPUs from the powerless u60 and power it up and I get the same error.
> 
> Ok, I think to myself, it is either the power unit or the SCSI backplane. I unplug the SCSI backplane and all of the miscellaneous front end wiring from the motherboard except power switch and related functions. Upon powering it up, I get the same exact error.
> 
> Here is the error itself:
> 
> RED State Exception
> 
> TL=0000.0000.0000.0005 TT=0000.0000.0000.0064
>    TPC=0000.0000.efff.f9e4 TnPC=0000.0000.efff.f9e8 TSTATE=0000.0044.5604.1400
> TL=0000.0000.0000.0004 TT=0000.0000.0000.0064
>    TPC=0000.0000.efff.f9e4 TnPC=0000.0000.efff.f9e8 TSTATE=0000.0044.5604.1400
> TL=0000.0000.0000.0003 TT=0000.0000.0000.0064
>    TPC=0000.0000.efff.f9e4 TnPC=0000.0000.efff.f9e8 TSTATE=0000.0044.5604.1400
> TL=0000.0000.0000.0002 TT=0000.0000.0000.0064
>    TPC=0000.0000.efff.e334 TnPC=0000.0000.efff.e338 TSTATE=0000.0044.5604.1400
> TL=0000.0000.0000.0001 TT=0000.0000.0000.0064
>    TPC=0000.0000.efff.e764 TnPC=0000.0000.efff.e768 TSTATE=0000.0044.5600.0400
> 
> [rinse .. repeat]
> 
> By this point, I am convinced the problem is the power unit, but I an interested in hearing your opinions about this as well. This hardware is out of warranty and there is no hope of securing a new contract on it. Your guidance is much appreciated.
> 
> Thanks!!!
> 
> 
> ----------------------------------------------------------
>  Trent Petrasek                 Internap Network Services
>  Systems Engineer               IT Services
>  tpetrasek@internap.com         404.302.9742
> 
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+kefT1CLn4SP2qlMRAvb1AJ9wPCCk8YkkCD4eA09MJBS5C0AaNACg1drj
fGs8i19DbBB3Skoa6An6qL0=
=Ct4f
-----END PGP SIGNATURE-----
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Mon Apr 7 17:11:37 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:08 EST