Skip to main content
NetApp Knowledge Base

Panic  due to Ethernet T62100-CR card

Views:
390
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • Dual 40/100G Ethernet card T62100-CR

Issue

  • Fatal error against the card, follow up by the panic. Example:
Wed Jun 03 21:23:59 +0200 [node_name: intr: netif.fatal.err:alert]: The network device in slot 1 encountered fatal error e1a/e1b.
Wed Jun 03 21:34:06 +0200 [node_name: wafl_exempt03: sk.panic:alert]: Panic String: WAFL hung for n02_data. in SK process wafl_exempt03 on release 9.7P3 (C)
Fri Jun 05 07:28:52 +0200 [node_name: intr: netif.fatal.err:alert]: The network device in slot 1 encountered fatal error e1a/e1b.
Fri Jun 05 08:03:16 +0200 [node_name: splog_main: mgr.stack.string:notice]: Panic string: WAFL hung for n02_root. in SK process wafl_exempt12 on release 9.7P3 (C)
Tue Jun 09 10:45:33 +0200 [node_name: intr: netif.fatal.err:alert]: The network device in slot 1 encountered fatal error e1a/e1b.
Tue Jun 09 11:20:11 +0200 [node_name: splog_main: mgr.stack.string:notice]: Panic string: WAFL hung for n02_root. in SK process wafl_exempt10 on release 9.7P3 (C)
  • PANIC string example:
PANIC  : PCI Error NMI from device(s):ErrSrcID(CorrSrc(0x3860),UCorrSrc(0x18)), RPT(0,3,0):PLX PCIE 8780 switch on Controller, PCI Device 1425:600d in slot 5 on Controller.
 
  • Boot message example:

SRAM: PCI slot5 had error, turning on slot LED.

 

 
 
Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support