Re: Bonding driver fails to enable second interface if updelay is non-zero

2017-07-24 Thread Benjamin Gilbert
On Mon, Jul 24, 2017 at 2:34 PM, Mahesh Bandewar (महेश बंडेवार) wrote: > Having said that, the proposed solution (Cong's patch) should fix it, please > give it a try so that this fix can be formalized. The patch fixes the problem for me. Thanks! --Benjamin Gilbert

Re: Bonding driver fails to enable second interface if updelay is non-zero

2017-07-24 Thread Cong Wang
On Thu, Jul 20, 2017 at 7:07 PM, Benjamin Gilbert wrote: > [resend] > > Hello, > > Starting with commit de77ecd4ef02ca783f7762e04e92b3d0964be66b, and > through 4.12.2, the bonding driver in 802.3ad mode fails to enable the > second interface on a bond device if updelay is non-zero. dmesg says: >

Bonding driver fails to enable second interface if updelay is non-zero

2017-07-20 Thread Benjamin Gilbert
[resend] Hello, Starting with commit de77ecd4ef02ca783f7762e04e92b3d0964be66b, and through 4.12.2, the bonding driver in 802.3ad mode fails to enable the second interface on a bond device if updelay is non-zero. dmesg says: [ 35.825227] bond0: Setting xmit hash policy to layer3+4 (1) [ 35.8