Hi Aaron, On Saturday, 21. February 2015 01:59:35 Brown, Aaron F wrote: > Thanks, that (and the multiple bug write-ups on sourceforge) gave me more > than enough to go on. I was able to replicate it on a handful of systems > in my lab. On effected systems setting up a NAT and stressing the > interfaces with even moderate traffic levels triggers it pretty quickly. > It appears that the NAT part is unnecessary, just setting the systems up > as a software router and running some traffic across it also triggers it > giving the same apparent behavior (tx hang, watchdog timeout trace, port > reset.) > > And with an internal reproduction of the issue I have created an internal > bug report, described my set of reproductions, referenced the similar > external ones and assigned it to our current e1000e developer.
just wanted to quickly check if there has been any progress since the internal bug report has been filed? Cheers, Thomas ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ 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
