Had an RSP4 crash with the following sh context output:
========= Context ======================
RSP Software (RSP-PV-M), Version 12.0(14)S5, EARLY DEPLOYMENT RELEASE
SOFTWARE (fc1)
TAC Support: http://www.cisco.com/cgi-bin/ibld/view.pl?i=support
Compiled Thu 17-May-01 14:05 by ninahung
Signal = 8, Code = 0x2C, Uptime 12w5d
$0 : 00000000, AT : 612F0000, v0 : 3E8429CC, v1 : 61BC6848
a0 : 61BC6848, a1 : 61BC656C, a2 : 00000083, a3 : 613B025C
t0 : 00000030, t1 : 3400E705, t2 : 34008704, t3 : FFFF00FF
t4 : 00000083, t5 : 3E840024, t6 : 00000400, t7 : FFFFFFFF
s0 : 60419F54, s1 : 616A4470, s2 : 3400C985, s3 : 612F02C4
s4 : 00000080, s5 : 00000000, s6 : 61BA7C9C, s7 : 616A4470
t8 : 602D2DCC, t9 : 00000000, k0 : 6859E5EC, k1 : 602DA190
gp : 611202C0, sp : 616A4410, s8 : 00000000, ra : 6132D280
EPC : 6132D2A0, SREG : 3400E707, Cause : 2000002C
Error EPC : 60436A3C, BadVaddr : 8A206455
Have never seen signal 8 type before. The following URL suggests that
sig 8 is an FPU exception as opposed to the more common unspecified
parity error.
http://www.cisco.com/warp/public/63/vipcodes.html
1) Can I conclude that there is an FPU component to the RSP CPU, and
that failure of this component caused this crash directly?
2) Would the recommended course of action be to replace the RSP? Have
had 2 other parity crashes (SIG=20) 1 on the other RSP & 1 on a VIP in
the past 6 months; am wondering if this sig 8 crash could be root cause
of the sig=20s or vice versa.
3) Can anyone provide specifics regarding sig 8 crashes? Have searched
all over CCO for sig 8, FPU exception, etc. with unsatisfying results.
Thanks for any input.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:32 EDT