> There shouldn't be any need. Basically what you want to check for is > to make sure those logs have the same pattern with OOM errors followed > by the rcu_sched warning about detecting a CPU stall. If that is the > case that is the most likely root cause for the Tx hangs that are > being reported.
This assessment is correct. > Otherwise you might take a look at > seeing if you can resolve the OOM condition so that you aren't sending > enough logs to the serial console to trigger the stall Spoken to some of my colleagues and we are exploring disabling the oom_killer. Thanks for your response and help! Abejide Ayodele It always seems impossible until it's done. --Nelson Mandela ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
