Guest

Preview Tool

Cisco Bug: CSCur48521 - Device driver for device 'GAMBIT 1G EP FPGA' detected sequence error

Last Modified

Jun 18, 2017

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

4.3.2.BASE

Description (partial)

Symptom:
Customer see the following errors, and the interface goes down.

LC/0/0/CPU0:Oct 16 11:10:11.544 : pfm_node_lc[288]: %PLATFORM-FCA-2-SEQ_ERROR : Set|lda_server[40990]|EP Controller(0x1046040)|Device driver for device 'GAMBIT 1G EP FPGA' detected sequence error on 'GAMBIT I2C SILAB Bus'. Error status 0xfeedface. Error address 0xfeedface. Error data 0xfeedface. 
LC/0/0/CPU0:Oct 16 11:10:11.581 : lda_server[65]: %L2-SPA-3-POWER_FAILURE : SPA_OK and PWR_OK signal is deasserted on subslot 1   
LC/0/0/CPU0:Oct 16 11:10:11.581 : pfm_node_lc[288]: %PLATFORM-FCA-2-SEQ_ERROR : Clear|lda_server[40990]|EP Controller(0x1046040)|Device driver for device 'GAMBIT 1G EP FPGA' detected sequence error on 'GAMBIT I2C SILAB Bus'. Error status 0xfeedface. Error address 0xfeedface. Error data 0xfeedface. 


RP/0/RSP0/CPU0:Oct 16 11:10:13.138 : shelfmgr[396]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/1 A9K-MPA-20X1GE state:IN-RESET 
LC/0/0/CPU0:Oct 16 11:10:13.200 : lda_server[65]: %L2-SPA-5-OIR_ERROR : SPA (1): A SPA hardware or software error occurred, please contact technical support   
RP/0/RSP0/CPU0:Oct 16 11:10:13.203 : invmgr[256]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/1, state: FAILED 
RP/0/RSP0/CPU0:Oct 16 11:10:14.205 : invmgr[256]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/1, state: UNPOWERED 
RP/0/RSP0/CPU0:Oct 16 11:10:17.260 : invmgr[256]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/1, state: DISABLED 
RP/0/RSP0/CPU0:Oct 16 11:11:18.414 : tclsh[65756]:  %HA_EM-2-LOG: sl_mpareset.tcl: !!! EEM MPA RESET STARTED - Waiting 20 seconds!!!
RP/0/RSP0/CPU0:Oct 16 11:11:38.416 : tclsh[65756]:  %HA_EM-2-LOG: sl_mpareset.tcl: !!! EEM MPA RESET WAIT PERIOD COMPLETE !!!

Conditions:
ASR9001 running 4.3.2.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.