On Tue, 2017-03-21 at 12:57 +0200, Leon Romanovsky wrote: > From: Jack Morgenstein <jackm@xxxxxxxxxxxxxxxxxx> > > A warning message during SRIOV multicast cleanup should have actually > been > a debug level message. The condition generating the warning does no > harm > and can fill the message log. > > In some cases, during testing, some tests were so intense as to swamp > the > message log with these warning messages, causing a stall in the > console > message log output task. This stall caused an NMI to be sent to all > CPUs > (so that they all dumped their stacks into the message log). > Aside from the message flood causing an NMI, the tests all passed. > > Once the message flood which caused the NMI is removed (by reducing > the > warning message to debug level), the NMI no longer occurs. > > Sample message log (console log) output illustrating the flood and > resultant NMI (snippets with comments and modified with ... instead > of hex digits, to satisfy checkpatch.pl): [ snip ] Thanks, applied. -- Doug Ledford <dledford@xxxxxxxxxx> GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
