Symptoms

DS-65xx reboots once unexpectedly then comes back online with no issues. switchType: 109.1 switchState: Online Fabric OS: v7.4.1b uptime :03:18:40 up 27 min, 1 user, load average: 1.09, 0.60, 0.30errdump -a:2016/10/10-02:51:17:200273, [HAM-1004], 3037/451, CHASSIS, INFO, DFW3-2830130-793765-B, Processor rebooted - Software Fault:Kernel Panic., reboot.c, line: 113, comp:hamd, ltime:2016/10/10-02:51:13:175020 2016/10/10-02:51:20:119799, [EM-5012], 3052/0, CHASSIS, INFO, DFW3-2830130-793765-B, start emd FSS_RECOV_COLD, emfss.c, line: 437, comp:emd, ltime:2016/10/10-02:51:20:116608 2016/10/10-02:51:20:632805, [DIAG-6004], 3055/0, CHASSIS, INFO, DFW3-2830130-793765-B, test_thread: tname porttestd Calling fcn - PID: 1314, parameter.c, line: 1448, comp:insmod, ltime:2016/10/10-02:51:20:630948 2016/10/10-02:51:26:438892, [EM-5012], 3056/0, CHASSIS, INFO, DFW3-2830130-793765-B, end emd FSS_RECOV_ACTIVE (cold), emfss.c, line: 522, comp:emd, ltime:2016/10/10-02:51:26:433133

Cause

Within the SUPPORTSHOW File, the Core file output is generated.The switch had a machine check/i-cache parity error with multiple problematic error codes for the Double Date Rate Synchronous Dynamic Random Access Memory (DDR SDRAM) as seen below.pdshow: ______________________********________________________* File :/core_files/panic/core.pd20161010024344 ** SECTION:CONSOLE_LOG *-----------------------********------------------------============= END OF HEAD & START OF TAIL =========Machine check in kernel mode.I-Cache Parity ErrorPLB41 Arbiter: DDR SDRAM: DDR0_00=0x0000190a DDR SDRAM: DDR0_01=0x01000000 DDR SDRAM: DDR0_31=0x00000000 DDR SDRAM: DDR0_32=0x00000000 DDR SDRAM: DDR0_33=0x00000000 DDR SDRAM: DDR0_34=0x00000008 DDR SDRAM: DDR0_35=0x00000000 DDR SDRAM: DDR0_36=0xffffffff DDR SDRAM: DDR0_37=0xffffffef DDR SDRAM: DDR0_38=0x00000028 DDR SDRAM: DDR0_39=0x00000000 DDR SDRAM: DDR0_40=0x00000000 DDR SDRAM: DDR0_41=0x00000000============= END OF TAIL ========================= 

Resolution

Typically, this type of error indicates a hardware issue.Workaround: Continue to monitor the switch for a repetition in this problem.Fix: Replace the switch.

Support Cases