C/B-Series f/w 6.42.12.0007 Reset with "event_data" error after Many Messages logged

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 14715 

Products
C5-Series, firmware 6.42.12.0007
C3-Series, firmware 6.42.12.0007
B5-Series, firmware 6.42.12.0007
B3-Series, firmware 6.42.12.0007 

Symptoms
Many messages displayed (for any reason) in the current.log, followed by a system reboot event. 

The current.log (5487) displays a register-rich set of BackTraces, plus a "Fault(0x00000300)" reset cause; for example:
<57> MAY 11 18:33:46 2012 STK1 BOOT[268430624]: bootos.c(1405) 316 %%
Start of Code - Build:06.42.12.0007 Date:Thu Apr 26 16:06:55 2012
BackTrace-r0 = 0x00000000 r1 = 0x06b957b0 r2 = 0x00000000 r3 = 0x00000000
BackTrace-r4 = 0x00003030 r5 = 0x00000050 r6 = 0x00000001 r7 = 0x053e0c3a
BackTrace-r8 = 0x01d70000 r9 = 0x00000000 r10 = 0x00022440 r11 = 0x00000111
BackTrace-r12 = 0x011d330c r13 = 0x00000000 r14 = 0x00000000 r15 = 0x00000001
BackTrace-r16 = 0x00000000 r17 = 0x06b95920 r18 = 0x00000000 r19 = 0x00000dad
BackTrace-r20 = 0x06b97750 r21 = 0x00000003 r22 = 0x0163947d r23 = 0x01d70000
BackTrace-r24 = 0x06b957d0 r25 = 0x00000001 r26 = 0x00000007 r27 = 0x053e0a38
BackTrace-r28 = 0x0000007a r29 = 0x053e0a8c r30 = 0x000000a0 r31 = 0x06b957e0
BackTrace-lr = 0x005c5c04 pc = 0x005c5c0c msr = 0x00000000
<110> MAY 11 18:34:08 2012 STK1 BOOT[138232616]: edb_bxs.c(1226) 326 %%
Last switch reset caused by Fault(0x00000300) SRR0(0x005C5C0C) SRR1(0x0000B030)
DMISS(0x00000000) IMISS(0x00000000) DAR(0x00000000) DSISR(0x0A000000)
The sysDmp (13650) file states "Task Name: CPLD_Status" and the diagnostic points to "event_data"; for example:
Detailed erred task information
---------------------------------
Calling Stack:

------------
Task ID: 0x6b97750
Task Name: CPLD_Status
PC: 0x11d8a64
PendQ: 0x6acaa34
SP: 0x2d6428c

0x11d8a64: taskSuspend (0x11d8628) + 0x43c
0x100525c: log_fault_nvram (0x1004f74) + 0x2e8
0x101514c: event_data (0x1014f38) + 0x214
0x1014f38: event_data (0x1014f38) + 0x0
Symbol not found for 0x2d332053
Cause
Running out of buffers due to an excessive amount of log messaging. 

Solution
Upgrade to firmware 6.42.13.0002 or higher.
Release notes state, in the 'Firmware Changes and Enhancements' section:
17111    Addressed a buffer allocation issue due to excessive amount of log messages reported on a stack member unit. This resulted in an exception fault and reset with message "Last switch reset caused by Fault(0x00000300) SRR0(0x005C5C0C) SRR1(0x0000B030) DMISS(0x00000000) IMISS(0x00000000) DAR(0x00000000) DSISR(0x0A000000)".
Photo of FAQ User

FAQ User, Official Rep

  • 13,610 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.