Skip to main content
NetApp Knowledge Base

FAS9000/AFF-A700 PCI NMI panics on same slot after card and motherboard replaced

Views:
156
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

FAS9000
FAS9500
AFF A700
AFF A900
 

Issue

The following conditions must be met:

1) Node continues to panic with the same "PCI Error NMI" or "Uncorrectable Machine Check Error" panic string on a PCI device (can include a device the motherboard in rare cases) in the same slot in the chassis.

Example panics:

Panic String: PCI Error NMI from device(s):ErrSrcID(CorrSrc(0x8460),UCorrSrc(0)), RPT(128,2,0):PLX PCIE 8780 switch on Controller, Br[8780](132,12,0): Link down. 


PANIC : PCI Error NMI from device(s):ErrSrcID(CorrSrc(0x5f20),UCorrSrc(0)), RPT(0,3,0):PLX PCIE 8764 switch in slot 6 on Controller, NETAPP NVRAM10 in slot 6 on Controller, PLX PCIE 8764 switch in slot 6 on Controller, NETAPP NVRAM10 in slot 6 on Controller

PANIC: PCI Error NMI from device(s):PCI Device 111d:806c in slot 2 on Controller, Qlogic FC 8G adapter in slot 2 on Controller, Qlogic FC 8G adapter in slot 2 on Controller

2) The device (PCI card or module) identified as the cause of the PCI NMI/UMCE panic has already been replaced.
 
3) The motherboard has also been replaced.
 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.