[c-nsp] Bad 720-3BXL?

[Peter Kranz]

A new 3BXL in burn-in keeps dumping crashinfo's.. bad hardware, or IOS
problem?

Details:

IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9-M), Version
12.2(18)SXF11, RELEASE SOFTWARE (fc1)

NAME: "WS-C6506-E", DESCR: "Cisco Systems Catalyst 6500 6-slot Chassis
System"
PID: WS-C6506-E        , VID: V02, SN: SAL10403KDS

NAME: "WS-C6K-VTT-E 1", DESCR: "VTT-E FRU 1"
PID: WS-C6K-VTT-E      , VID:    , SN: SMT1031G183

NAME: "WS-C6K-VTT-E 2", DESCR: "VTT-E FRU 2"
PID: WS-C6K-VTT-E      , VID:    , SN: SMT1030A329

NAME: "WS-C6K-VTT-E 3", DESCR: "VTT-E FRU 3"
PID: WS-C6K-VTT-E      , VID:    , SN: SMT1030A293

NAME: "CLK-7600 1", DESCR: "OSR-7600 Clock FRU 1"
PID: CLK-7600          , VID:    , SN: SMT1029C869

NAME: "CLK-7600 2", DESCR: "OSR-7600 Clock FRU 2"
PID: CLK-7600          , VID:    , SN: SMT1029C869

NAME: "3", DESCR: "WS-X6748-GE-TX CEF720 48 port 10/100/1000mb Ethernet Rev.
2.5"
PID: WS-X6748-GE-TX    , VID: V02, SN: SAL1009EKLH

NAME: "switching engine sub-module of 3", DESCR: "WS-F6700-CFC Centralized
Forwarding Card Rev. 2.1"
PID: WS-F6700-CFC      , VID: V01, SN: SAL1012GFAD

NAME: "4", DESCR: "WS-X6516-GBIC SFM-capable 16 port 1000mb GBIC Rev. 5.5"
PID: WS-X6516-GBIC     , VID:    , SN: SAL0735L0P4

NAME: "5", DESCR: "WS-SUP720-3BXL 2 ports Supervisor Engine 720 Rev. 5.3"
PID: WS-SUP720-3BXL    , VID: V03, SN: SAL1015JPT1

NAME: "msfc sub-module of 5", DESCR: "WS-SUP720 MSFC3 Daughterboard Rev.
2.6"
PID: WS-SUP720         , VID:    , SN: SAL1015JPU9

NAME: "switching engine sub-module of 5", DESCR: "WS-F6K-PFC3BXL Policy
Feature Card 3 Rev. 1.8"
PID: WS-F6K-PFC3BXL    , VID: V01, SN: SAL1015JQ3X

NAME: "WS-C6506-E-FAN 1", DESCR: "Enhanced 6-slot Fan Tray 1"
PID: WS-C6506-E-FAN    , VID: V03, SN: DCH10470698

NAME: "PS 1 WS-CAC-2500W", DESCR: "110/220v AC power supply, 2500 watt 1"
PID: WS-CAC-2500W      , VID:    , SN: ART0817E032

NAME: "PS 2 WS-CAC-2500W", DESCR: "110/220v AC power supply, 2500 watt 2"
PID: WS-CAC-2500W      , VID:    , SN: ART0818E0QM


Latest crash:

%Software-forced reload


Breakpoint exception, CPU signal 23, PC = 0x41D7658C


-Traceback= 41D7658C 41D744D8 418698BC 4186AC78 41AC4E10 41AC4F68 41D68FAC 
$0 : 00000000, AT : 430E0000, v0 : 44AD0000, v1 : 43630000
a0 : 4729CFF8, a1 : 00008100, a2 : 00000000, a3 : 42E10000
t0 : 41D69098, t1 : 34008101, t2 : 41D690C0, t3 : FFFF00FF
t4 : 41D69098, t5 : 0004A049, t6 : 50000000, t7 : 00000000
s0 : 00000000, s1 : 43090000, s2 : 00000000, s3 : 43050000
s4 : 43050000, s5 : 43050000, s6 : 42AF0000, s7 : 42AF0000
t8 : 5001025C, t9 : 00000005, k0 : 00000000, k1 : 00000000
gp : 430E0230, sp : 50010340, s8 : 42AF0000, ra : 41D744D8
EPC  : 41D7658C, ErrorEPC : 41AC9CF0, SREG     : 34008103
MDLO : 00000000, MDHI     : 00000000, BadVaddr : 00000000
DATA_START : 0x42DC0210
Cause 00000824 (Code 0x9): Breakpoint exception

Writing crashinfo to bootflash:crashinfo_20071031-164227

=== Flushing messages (09:42:27 PDT Wed Oct 31 2007) ===

Buffered messages:

Queued messages:
*Oct 31 09:42:27: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console
debugging output.

*Oct 31 09:42:27: %C6K_PLATFORM-2-PEER_RESET: RP is being reset by the SP
*** System received a Software forced crash ***
signal= 0x17, code= 0x24, context= 0x44aca994
  PC = 0x41d690f4, SP = 0x4308c088, RA = 0x4106c330
  Cause Reg = 0x00003c20, Status Reg = 0x34008002
rommon 1 > 
Oct 31 09:42:30: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console
debugging output.

Oct 31 09:42:30: %OIR-SP-6-CONSOLE: Changing console ownership to switch
processor



*** System received an FPU exception ***
signal= 0x8, code= 0x2c, context= 0x42330e64
PC = 0x402d1bac, Cause = 0x1820, Status Reg = 0x34008002


Peter Kranz
Founder/CEO - Unwired Ltd
www.UnwiredLtd.com
Desk: 510-868-1614 x100
Mobile: 510-207-0000
pkranz at unwiredltd.com