Guest

Preview Tool

Cisco Bug: CSCvt90166 - ACI Leaf rebooted with reset-reason "kernel panic" 4.2(2f)

Last Modified

Jun 16, 2020

Products (1)

  • Cisco Nexus 9000 Series Switches

Known Affected Releases

14.2(2f)

Description (partial)

Symptom:
Switch rebooted with following reset reason. 

<pre>
*************** module reset reason (1) *************
0) At 2020-03-24T12:31:20.398-05:00
    Reason: kernel-panic
    Service:system crash
    Version: 14.2(2f)
</pre>
<pre>
----------------------------
    Module:  1
----------------------------


Last log in OBFL was written at time Wed Mar 25 11:46:53 2020



Reset Reason for this card:
	Image Version : 14.2(2f)
	Reset Reason (LCM): Unknown (0) at time Tue Mar 24 12:43:44 2020
	Reset Reason (SW): Kernel Panic (19) at time Tue Mar 24 12:31:21 2020
	  Service (Additional Info): system crash
	Reset Reason (HW): Kernel Panic (19) at time Tue Mar 24 12:43:44 2020
	Reset Cause (HW): 0x0c at time Tue Mar 24 12:43:44 2020
	Reset internal (HW): 0x00 at time Tue Mar 24 12:43:44 2020


Last log in OBFL was written at time Tue Mar 24 11:47:07 2020
</pre>

Conditions:
show logging onboard stack-trace << shows following output.

<pre>
<6>[6998079.298862] <7><{fc2}>vsan 730, vlan12

<6>[6998079.298867] <7><{fc2}>Transmitting packet on tx_dev: ffff88083329e1c0, len = 84

<6>[6998079.299922] <7><{fc2}> fc2_add_vegas2_hdr_aci vhe->vsan : 730 <7><{fc2}>proto: 0x8906

<6>[6998079.299927] <7><{fc2}>Received FCoE Packet

<6>[6998679.327218] <7><{fc2}>FC2 DI 0xffc0, SI 0xffc0

<6>[6998679.327223] <7><{fc2}>Sup hi prio idx from fcfwd_idx_from_intf: 0xffff

<6>[6998679.327225] <7><{fc2}>SI set in Vegas hdr: 0xffff

<6>[6998679.327228] <7><{fc2}>vsan 730, vlan12

<6>[6998679.327234] <7><{fc2}>Transmitting packet on tx_dev: ffff88083329e1c0, len = 84

<6>[6998679.328201] <7><{fc2}> fc2_add_vegas2_hdr_aci vhe->vsan : 730 <7><{fc2}>proto: 0x8906

<6>[6998679.328212] <7><{fc2}>Received FCoE Packet

<6>[6999279.360307] <7><{fc2}>FC2 DI 0xffc0, SI 0xffc0

<6>[6999279.360311] <7><{fc2}>Sup hi prio idx from fcfwd_idx_from_intf: 0xffff

<6>[6999279.360313] <7><{fc2}>SI set in Vegas hdr: 0xffff

<6>[6999279.360316] <7><{fc2}>vsan 730, vlan12

<6>[6999279.360322] <7><{fc2}>Transmitting packet on tx_dev: ffff88083329e1c0, len = 84

<6>[6999279.361376] <7><{fc2}> fc2_add_vegas2_hdr_aci vhe->vsan : 730 <7><{fc2}>proto: 0x8906

<6>[6999279.361387] <7><{fc2}>Received FCoE Packet

<0>[6999381.436836] MACHINE CHECK ERROR

<0>[6999381.436838] MACHINE CHECK ERROR

<0>[6999381.436839] MACHINE CHECK ERROR

<0>[6999381.436840] MACHINE CHECK ERROR

<0>[6999381.436842] MACHINE CHECK ERROR

<0>[6999381.436844] MACHINE CHECK ERROR

<0>[6999381.436845] MACHINE CHECK ERROR

<0>[6999381.436847] MACHINE CHECK ERROR

<0>[6999381.436848] MACHINE CHECK ERROR

<0>[6999381.436852] MACHINE CHECK ERROR

<0>[6999381.436854] MACHINE CHECK ERROR

<0>[6999381.436855] MACHINE CHECK ERROR

<2>[6999381.437207] cctrli: SUP/TOR NMI handler called. cmd: 1

<2>[6999381.437207] cctrli: SUP/TOR NMI handler called

<0>[6999381.437213] @@@cctrli: wrote 2 to scratch RR

<0>[6999381.437996] nvram_klm wrote rr=2 rr_str=(null) to nvram

<0>[6999381.437997] (1585071080.399201) (03-24-2020 17:31:20 UTC) cctrl_cmn_reset_ports_handler: send signal to bfdc begin.

<0>[6999381.438061] Sending SIGUSR1 signal to bfdc process

<6>[6999382.349250] sbridge: HANDLING MCE MEMORY ERROR

<6>[6999382.404569] CPU 9: Machine Check Exception: 5 Bank 7: be00000000010091

<0>[6999382.430183] (1585071081.391304) (03-24-2020 17:31:21 UTC) cctrl_cmn_reset_ports_handler: send signal to bfdc end.

<0>[6999382.430185] cctrl_cmn_reset_sfp_qsfp_phy_ports/1224: cctri2: disable all nl intr notify

<0>[6999382.430194] Sending SIGUSR1 signal to port_client process

<0>[6999382.430234] (1585071081.391355) (03-24-2020 17:31:21 UTC)cctrl2 card_index=21135, link flap done.

<0>[6999382.430235] Kernel panic - not syncing: FPGA watchdog
</pre>
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.