Okay - I believe I've root-caused this problem, and it goes back to an older version of a patch to ib_mad. The older version of the patch had been integrated into our in-house builds and resulted in ib_mad generating a new MAD response whenever it received an undeliverable MAD response. The version of the patch actually committed in OFED 1.5.4.1 (http://www.mail-archive.com/[email protected]/msg10855.html) does not have this problem so no further action is needed.
-----Original Message----- From: Hefty, Sean [mailto:[email protected]] Sent: Thursday, February 09, 2012 2:57 AM To: Mike Heinz; [email protected] Cc: Todd Rimmer Subject: RE: Possibly serious bug in ib_mad: processing packets from ibping can consume 100% of CPU and may leave user processes locked in umad_recv > Subject: Possibly serious bug in ib_mad: processing packets from > ibping can consume 100% of CPU and may leave user processes locked in > umad_recv Is there a chance that the low level driver is asking to send the MAD to itself over and over again? This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
