Skip to main content
NetApp Knowledge Base

CONTAP-419128: MCC-IP node changes can cause a system panic during RDMA connection cleanup

  1. Last updated
  2. Save as PDF
Views:
1
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
metrocluster
Last Updated:

Issue

In an MCC-IP configuration, repeated RDMA peer updates and connection cleanup can cause the deferred RDMA cleanup thread to run for an extended period without yielding. If the thread remains busy long enough, the system can panic with the following message:
thread (defer_thr) on cpu 6 hung for 4001 milliseconds in process defer_thr on release 9.12.1P12 (C)
Similar reports include this message on other CPUs and releases. 

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.