OPERATIONAL DEFECT DATABASE
...
...
The device reloads with the reset reason of "kernel-panic." This applies to kernel panics with and without PCIE issues recorded on dmesg-mtdoops. Reason: Kernel Panic System version: 13.1(2m) Service: system crash Reset Reason for this card: Image Version : 13.1(2m) Reset Reason (LCM): Unknown (0) at time Thu Jul 5 10:45:48 2018 Reset Reason (SW): Kernel Panic (19) at time Thu Jul 5 10:42:16 2018 Service (Additional Info): system crash Reset Reason (HW): Kernel Panic (19) at time Thu Jul 5 10:45:48 2018 Reset Cause (HW): 0x04 at time Thu Jul 5 10:45:48 2018 Reset internal (HW): 0x00 at time Thu Jul 5 10:45:48 2018
Kernal Panic on an affected version
None, device should return after the reload
On the Non-Fixed Releases: ====================== Kernal Panic failures could be SW or HW related, on the old versions, and due to PCIE electrical idle feature enabled by default, there is no way to tell if the failure is SW or HW related. On the Fixed Releases, the following are introduced: ========================================= ++ Fix for existing sources of kernel panic issues ++ This applies to both kernel panic with and without PCIE errors recorded on the dmesg-mtdoops ++ Increased clarity of the reason for the kernel panic (whether it is software or hardware related) ++ If the cause of the kernel panic is due to hardware issue, there will now be proper identification of which device is causing the error
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
