GbE2c L2/L3 Ethernet Blade Switch Rebooted because of software PANIC

Sauer_1 — Sat, 14 Nov 2009 19:31:12 GMT

After power failure the ethernet switches are continually rebooting due to a "software PANIC": Error dancing through process 94.

Has anyone a hint how this issue could be resolved?

Initializing Production Mode ...

*** Angus DUO ***

Base MAC Address = xx:xx:xx:xx:xx:xx

PCI unit 0: Dev 0xb300, Rev 0x12, Chip BCM56300_B1, Driver BCM56304_B0
SOC unit 0 attached to PCI device BCM56300_B1

GEA initialized for unit 0 . . . . . . . . . . . . . . . . . . . . DONE
GbE2c L2/L3 Ethernet Blade Switch for HP c-Class BladeSystem
Rebooted because of software PANIC.
Booting complete 7:00:00 Sun Jan 1, 2006:
Version 2.0.0 from FLASH image1, active config block.

Jan 1 7:00:00 NOTICE system: Port 7 is disabled because of a mismatch.

Jan 1 7:00:00 NOTICE system: Port 8 is disabled because of a mismatch.

Jan 1 7:00:00 NOTICE system: Port 15 is disabled because of a mismatch.

Jan 1 7:00:00 NOTICE system: Port 16 is disabled because of a mismatch.

Jan 1 7:00:01 NOTICE system: FI-SFP missing at port SFP21

Jan 1 7:00:01 NOTICE system: FI-SFP missing at port SFP22

Jan 1 7:00:01 NOTICE system: FI-SFP missing at port SFP23

Jan 1 7:00:01 NOTICE system: FI-SFP missing at port SFP24

Warning: With VLAN 1 disabled, certain ports will no longer
belong to any VLAN and will automatically be moved to
the default VLAN.

bcm_vlan_destroy : Invalid identifier[-13] at file nt_bcm_vlan.c line 315
Could not attach to thread 96.
Could not attach to thread 97.

Display MP Crash Info
BackTrace Catch Signal 11->SIGSEGV
Register Dump
GPR_R0 -> 192e00
GPR_R1 -> 7fff1838
GPR_R2 -> 44422482
GPR_R3 -> ffffffff
GPR_R4 -> 20004c0a
GPR_R5 -> 7fff1810
GPR_R6 -> 708
GPR_R7 -> 0
GPR_R8 -> 5460
GPR_R9 -> 7fff18c0
GPR_R10 -> 708
GPR_R11 -> 5460
GPR_R12 -> 2000000
GPR_R13 -> 10946a70
GPR_R14 -> 7fff19e8
GPR_R15 -> 48
GPR_R16 -> 10b6ad70
GPR_R17 -> 0
GPR_R18 -> 4
GPR_R19 -> 10b96b98
GPR_R20 -> 10b96b98
GPR_R21 -> 2
GPR_R22 -> 10b6ad70
GPR_R23 -> 10b96b28
GPR_R24 -> 30
GPR_R25 -> 0
GPR_R26 -> 10b70000
GPR_R27 -> 1
GPR_R28 -> 10b383f4
GPR_R29 -> 1
GPR_R30 -> 10940000
GPR_R31 -> 7fff1838
PC -> 10483438

Stack BackTrace
0x10483438: soc_l2x_sync_delete + 0xd0 (0, 7fff18c0, 708, 10df3fc8, 1fff, 0) + [24;80H [24;80H
0x1048340c: soc_l2x_sync_delete + 0xa4 (0, 1094350c, 10000, 1, 0, 220019) + 60
0x1053089c: bcm_fb_l2_addr_delete + 0x150 (0, 1094350c, 10000, 1078150c, 105307 [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H
0x10346d20: bcm_esw_l2_addr_delete + 0xdc (0, 1094350c, 10ae4, 0, 10346c44, 7ff [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H [24;80H
0x10302fcc: bcm_l2_addr_delete + 0xb0 (1094350c, 10240, 0, fffffff3, 20424428, [24;80H [24;80H
0x103b1340: nt_bcm_l2_addr_delete + 0x5c (10bb0c82, 7fff1978)
0x1002fea4: dc_bss_l2_addr_delete + 0x10 (28, 220019, 2e000001, 1c, 0, 0) + 20
0x1018a23c: vlan_destroy + 0x78 (1, 1, 0, 1, 0, 7fff19e8)
0x100092a8: remove_vlan_in_global + 0x98 (0, 0, 0, 10ba24c8, b9a0, 10d1a33c) + [24;80H [24;80H
0x10007b50: vlan_status_change + 0x7d0 (1, 10001, 10001, 10001, 10001, 10001) + [24;80H [24;80H [24;80H
0x1018afbc: vlan_cfg_apply + 0xcf8 (3, 10940864, 10, ffa6350, ffee668, ffa6760) [24;80H [24;80H [24;80H [24;80H [24;80H
0x101b2e18: main_cfg_apply + 0x3cc (1, 2, 4, 5, 10940000, 10940000) + 10
0x10196e84: cfg_load + 0x2e8 (1f, 0, 1, 18, 1, 10940000) + 10
0x10015218: init_done_ch + 0x15c (5354434b, 10d1df64)
0x1001a140: init_done + 0x68 (0, 0, 0, 0, 0, 0) + d35526c3
0x1016aee4: swap_context + 0x108
Error dancing through process 94

SIGSEGV(11) in thread DONE(tid=78, cmd=11141121)
.
.
.

Jan 1 7:00:14 NOTICE system: System Reset from signal panic

**** System Reset from signal panic ****

Memory Test ......

Production Mode
Memory Test ......................................................... PASSED
Extended Memory Test ................................................ SKIPPED
Flash Initialization ................................................ PASSED
I2C Initialization .................................................. PASSED
ENV Initialization ............................................

topic GbE2c L2/L3 Ethernet Blade Switch Rebooted because of software PANIC in Switches, Hubs, and Modems

GbE2c L2/L3 Ethernet Blade Switch Rebooted because of software PANIC