On Wed, Mar 30, 2016 at 10:00 AM, Sowmini Varadhan <sowmini.varad...@oracle.com> wrote: > On (03/29/16 23:44), Alexander Duyck wrote: >> This patch has been sanity checked only. I cannot yet guarantee it >> resolves the original issue that was reported. I'll try to get a >> reproduction environment setup tomorrow but I don't know how long that >> should take. > > I tried this out with rds-stress on my test-pair, unfortunately, I > still see the Tx hang. > > Setting up the test is quite easy- for reference, the instructions > are here: > https://sourceforge.net/p/e1000/mailman/message/34936766/
Yeah. The patch was sort of a knee-jerk reaction to being told that the patch referenced caused a regression. From what I can tell that is not the case as I am also seeing the Tx hangs when I run the test with the frames being linearized. I'll do some research this morning to see if I can find a root cause. Unfortunately the malicious driver detection isn't very well documented so I can't be certain what is causing it to be triggered. - Alex
