[vnet] [epair] epair interface stops working after some time

[Reshad Patuck]

​
Hi,

pulling the 'net.link.epair.netisr_maxqlen' down does seem to make this occur faster.
​
When I dropped it to 2 like Kristof did and I have the same symptoms on a box which was not exhibiting the problems manually began to have the same symptoms.
Bumping it back up to 2100 did not restore the functionality (I don't know if it should).
​
I will create a PR for this later today with all the information I have gathered so that we can have it all in one place.
Till then I have still have access to a box which is naturally in this state.
Let me know if there is anything you would like me to check
​
Thanks for the help,
​
Reshad

On 28 March 2018 12:32:44 AM IST, Kristof Provost <kristof at sigsegv.be> wrote:
>On 27 Mar 2018, at 20:59, Reshad Patuck wrote:
>> The current value of 'net.link.epair.netisr_maxqlen' is 2100, I will 
>> make it 210.
>> Will this require a reboot? or can I just change the sysctl and
>reload 
>> the epair module?
>> ​
>You shouldn’t need to reboot or reload the epair module. When I set it 
>to 2 on my box it pretty much immediately lost connectivity over the 
>epair interfaces.
>
>I’d expect you to get hit by the bug relatively quickly now, so be 
>aware of that.
>
>Regards,
>Kristof