Summit200 crash, need a hand deciphering log 2

[hoffmandarren]

Hi Everyone,
One of my Summit 200-48 switch took a crashed last Friday. Looking at the logs I can see when it happend. Can anyone help me decipher these log entrees. My guess is that gbic on port 50 died, but I can no longer repro the failure. Do these log entrees point to anything?

07/27/2007 11:05.56 <CRIT:SYST> Task: 0x871c4c50 "tPortUtilization"

07/27/2007 11:05.56 <CRIT:SYST> Error address: 0x075f022b, Error ID: 0x0000

07/27/2007 11:05.56 <CRIT:SYST> Cause Register: 0x0000001c

07/27/2007 11:05.56 <CRIT:SYST> Status Register: 0x10008301

07/27/2007 11:05.56 <CRIT:SYST> Exception Program Counter: 0x806c15a4

07/27/2007 11:05.56 <CRIT:SYST> Data bus error

07/27/2007 11:05.56 <CRIT:SYST> Task tPortUtilization(871c4c50) failed

07/27/2007 11:05.52 <CRIT:SYST> Task: 0x871c9f60 "tCardTask"

07/27/2007 11:05.52 <CRIT:SYST> Access Address : 0x075f022b

07/27/2007 11:05.52 <CRIT:SYST> Cause Register: 0x30000010

07/27/2007 11:05.52 <CRIT:SYST> Status Register: 0x10008301

07/27/2007 11:05.52 <CRIT:SYST> Exception Program Counter: 0x8033e554

07/27/2007 11:05.52 <CRIT:SYST> Address load Exception

07/27/2007 11:05.52 <CRIT:SYST> Task tCardTask(871c9f60) failed

07/27/2007 11:05.52 <WARN:SYST> Unit 1 DMA checked. Status word = 0x000c0003, RX packets = 92228698, TX packets = 36790107.

 

[gigaspeed]

I had a similar issue with a 200-24. I also thought it was gbic-related, but Extreme support said it wasn't. We had the switch replaced. My log showed the following:

06/06/2007 14:10:55.93 <Warn:SYST> Task: 0x83a82ef0 "tnetFdb"
06/06/2007 14:10:55.93 <Warn:SYST> Error address: 0x3e7db453, Error ID: 0x0000
06/06/2007 14:10:55.93 <Warn:SYST> Cause Register: 0x0000001c
06/06/2007 14:10:55.93 <Warn:SYST> Status Register: 0x10008301
06/06/2007 14:10:55.93 <Warn:SYST> Exception Program Counter: 0x803cfd18
06/06/2007 14:10:55.93 <Warn:SYST> Data bus error
06/06/2007 14:10:55.93 <Crit:SYST> Task tnetFdb(83a82ef0) failed

Not sure if your switch is still working or not...ours was sporadic, but certain ports worked. Unreliable though, so we called it in for service.

 

[rn4it]

If you can console into it run the following command.
run diagnostics extended

once it's completed use the following command

show diagnostics

You'll probably see some failures. port the resaults if you like.