On Mon, Jul 30, 2018 at 1:25 PM, Àbéjídé Àyodélé <abejideayod...@gmail.com> wrote: > Hi Alex, > > Thanks for responding! > >> Have you been seeing this as a >> reproducible issue or is this something that has only occurred once? > > It has occurred 3 times so far, we usually stop the hosts we see the issue > on for a long while which is probably why we don't see it that frequent, it > has occurred on 3 different hosts so far.
Is it always the OOM errors followed by the Tx timeout? >> If you are running at just 9600 baud you may want to >> see if you can configure a higher speed so that you can flush out the >> logs quick enough to avoid long delays in serial output. > > We are configured at 11520 baud, let me know if you need more information > from me, I'll be willing to re-enable the load on the host if you need me to. > > Abejide Ayodele > It always seems impossible until it's done. --Nelson Mandela What interface are you actually using to receive the log messages? Is it an actual serial connection or is it something like serial over LAN? Do you know if you have any sort of flow control enabled or anything that might delay displaying the message? Also what volume of logs are you sending over the serial interface? My main concern is that it seems like the logging of the errors is causing CPU stalls so once that is solved I believe the ixgbe Tx timeouts should be resolved as well. - Alex ------------------------------------------------------------------------------ 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
