Skip to main content
NetApp Knowledge Base

CONTAP-100782: Serial console displays "irdma_event_handler" messages following a reboot

Views:
19
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Issue

  • After a system reboot (including shutdown), irdma related "spam" messages are displayed in the console.

irdma_event_handler:315 event_handler LINK CHANGE (1) on pf 0 (0)
irdma_event_handler:326 PF: 0 (0), state: 1, speed: 0
irdma_event_handler:315 event_handler LINK CHANGE (1) on pf 2 (1)
irdma_event_handler:326 PF: 2 (1), state: 1, speed: 0
irdma_event_handler:315 event_handler LINK CHANGE (1) on pf 0 (0)
irdma_event_handler:326 PF: 0 (0), state: 2, speed: 25000000000
e0b: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: True, Flow Control: None
irdma_event_handler:315 event_handler LINK CHANGE (1) on pf 2 (1)
irdma_event_handler:326 PF: 2 (1), state: 2, speed: 25000000000
e0a: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: RS-FEC, Autoneg: True, Flow Control: None
System rebooting...
  • The messages appear even after conducting diagnostics, swapping cables between e0a and e0b, and removing/reinserting the motherboard.
  • All diagnostic test results indicate PASS and the Fault LED is also turned off.

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.