Red state Exception
Need help interpreting the followingred state exception:
Error enable reg: 0000.0001.00f0.001f
CPU: 0000.0000.0000.0001
TL=0000.0000.0000.0005 TT=0000.0000.0000.0064
TPC=0000.0000.f000.4c80 TnPC=0000.0000.f000.4c84 TSTATE=0000.0044.8004.1406
TL=0000.0000.0000.0004 TT=0000.0000.0000.0064
TPC=0000.0000.f000.4c80 TnPC=0000.0000.f000.4c84 TSTATE=0000.0044.8004.1406
TL=0000.0000.0000.0003 TT=0000.0000.0000.0064
TPC=0000.0000.f000.4c80 TnPC=0000.0000.f000.4c84 TSTATE=0000.0044.8004.1406
TL=0000.0000.0000.0002 TT=0000.0000.0000.0064
TPC=0000.0000.f000.2fe0 TnPC=0000.0000.f000.2fe4 TSTATE=0000.0044.8000.1506
TL=0000.0000.0000.0001 TT=0000.0000.0000.017f
TPC=0000.0000.f004.8170 TnPC=0000.0000.f004.8174 TSTATE=0000.0044.8000.140
SC Alert: Host System has Reset
6
Message was edited by:
grego122
Message was edited by:
grego122
[951 byte] By [
grego122a] at [2007-11-26 14:53:00]
# 1
Use your system warranty or service contract
and open a service case with Sun's techsupport.
http://www.sun.com/secure/contact/
These forums are only user-to-user conversations among friends.
Sun's techsupport engineers have special software tools to interpret such errors.
All you excerpt tells us that some sort of trap level one event happened
on cpu #1.
(TL1 has very different hash in the error than the other trap levels)
CPU: 0000.0000.0000.0001
.
TL=0000.0000.0000.0001 TT=0000.0000.0000.017f TPC=0000.0000.f004.8170 TnPC=0000.0000.f004.8174 TSTATE=0000.0044.8000.140
What it may actually mean?
Haven't a clue.
# 2
Note that the top 4 levels all have the same trap type (TT) value. That means the trap handler code was causing the same trap it was trying to handle, causing an endless loop which filled up the trap stack, causing the red state exception. This is typically what you see with red state exceptions caused by hardware failures. For that matter, unless you're developing kernel code, it's very likely that any red state exception you see is caused by a hardware problem.
Unfortunately, the trap stack dump doesn't provide any information about what hardware failed. You might try to run the power-on self test with whatever extended diagnostics your system provides, and it might be able to identify the failed component.
If you want to learn more about red state exceptions, download the SPARC V9 architecture manual at http://www.sparc.com/standards/SPARCV9.pdf (399 page pdf) and read the chapters on red state and trap handling. Also, you'll find the files in /usr/include/v9/sys helpful in parsing the trap stack dump.
