Guest

Preview Tool

Cisco Bug: CSCup64475 - Traceback seen on ingressq, fabricq driver ASIC SCAN initialization

Last Modified

Jun 10, 2018

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

5.3.0.BASE

Description (partial)

Traceback seen on ingressq, fabricq driver ASIC SCAN initialization -  %PLATFORM-CIH-3-COMMON_ERROR : Attaching ASIC SCAN info failed: cannot find ASIC SCAN cause for leaf
This traceback will be seen on after XR comes up and spawns ingressq/fabricq drivers. During driver initialization, asic scan feature is initialized which includes initialization of ASIC SCAN cause tree and this tree should be in sync with CIH interrupt tree of that particular driver.

Symptom:
CIH interrupt tree and ASIC SCAN cause tree should be in sync. They are not in sync right now. 


Conditions:
This will only occur once asic scan feature for INBAR is enabled/committed.
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.