ср, 25 сент. 2019 г. в 03:31, Jay Vosburgh :
>
> Алексей Захаров wrote:
> [...]
> >Right after reboot one of the slaves hangs with actor port state 71
> >and partner port state 1.
> >It doesn't send lacpdu and seems to be broken.
> >Setting link down and up again fixes slave state.
> [...]
>
>
чт, 26 сент. 2019 г. в 23:01, Jay Vosburgh :
>
> Aleksei Zakharov wrote:
>
> >чт, 26 сент. 2019 г. в 07:38, Jay Vosburgh :
> >>
> >> Aleksei Zakharov wrote:
> >>
> >> >ср, 25 сент. 2019 г. в 03:31, Jay Vosburgh :
> >> >>
> >> >> Алексей Захаров wrote:
> >> >> [...]
> >> >> >Right after reboot one
> -Original Message-
> From: Aleksei Zakharov [mailto:zaha...@selectel.ru]
> Sent: 2019年9月25日 19:02
> To: Jay Vosburgh
> Cc: netdev@vger.kernel.org; zhangsha (A)
> Subject: Re: Fwd: [PATCH] bonding/802.3ad: fix slave initialization states
> race
>
> ср, 25
Aleksei Zakharov wrote:
>чт, 26 сент. 2019 г. в 07:38, Jay Vosburgh :
>>
>> Aleksei Zakharov wrote:
>>
>> >ср, 25 сент. 2019 г. в 03:31, Jay Vosburgh :
>> >>
>> >> Алексей Захаров wrote:
>> >> [...]
>> >> >Right after reboot one of the slaves hangs with actor port state 71
>> >> >and partner por
чт, 26 сент. 2019 г. в 07:38, Jay Vosburgh :
>
> Aleksei Zakharov wrote:
>
> >ср, 25 сент. 2019 г. в 03:31, Jay Vosburgh :
> >>
> >> Алексей Захаров wrote:
> >> [...]
> >> >Right after reboot one of the slaves hangs with actor port state 71
> >> >and partner port state 1.
> >> >It doesn't send lac
Aleksei Zakharov wrote:
>ср, 25 сент. 2019 г. в 03:31, Jay Vosburgh :
>>
>> Алексей Захаров wrote:
>> [...]
>> >Right after reboot one of the slaves hangs with actor port state 71
>> >and partner port state 1.
>> >It doesn't send lacpdu and seems to be broken.
>> >Setting link down and up again f
ср, 25 сент. 2019 г. в 03:31, Jay Vosburgh :
>
> Алексей Захаров wrote:
> [...]
> >Right after reboot one of the slaves hangs with actor port state 71
> >and partner port state 1.
> >It doesn't send lacpdu and seems to be broken.
> >Setting link down and up again fixes slave state.
> [...]
>
>
Алексей Захаров wrote:
[...]
>Right after reboot one of the slaves hangs with actor port state 71
>and partner port state 1.
>It doesn't send lacpdu and seems to be broken.
>Setting link down and up again fixes slave state.
[...]
I think I see what failed in the first patch, could you test
From: Aleksei Zakharov
Date: Wed, 18 Sep 2019 16:05:45 +0300
> Once a while, one of 802.3ad slaves fails to initialize and hangs in
> BOND_LINK_FAIL state. Commit 334031219a84 ("bonding/802.3ad: fix slave
> link initialization transition states") checks slave->last_link_up. But
> link can still h
сб, 21 сент. 2019 г. в 10:06, Jay Vosburgh :
>
> Алексей Захаров wrote:
>
> >>
> >> Jay Vosburgh wrote:
> >> [...]
> >> > In any event, I think I see what the failure is, I'm working up
> >> >a patch to test and will post it when I have it ready.
> >>
> >> Aleksei,
> >>
> >>
Алексей Захаров wrote:
>>
>> Jay Vosburgh wrote:
>> [...]
>> > In any event, I think I see what the failure is, I'm working up
>> >a patch to test and will post it when I have it ready.
>>
>> Aleksei,
>>
>> Would you be able to test the following patch and see if it
>> resol
>
> Jay Vosburgh wrote:
> [...]
> > In any event, I think I see what the failure is, I'm working up
> >a patch to test and will post it when I have it ready.
>
> Aleksei,
>
> Would you be able to test the following patch and see if it
> resolves the issue in your testing? Th
Jay Vosburgh wrote:
[...]
> In any event, I think I see what the failure is, I'm working up
>a patch to test and will post it when I have it ready.
Aleksei,
Would you be able to test the following patch and see if it
resolves the issue in your testing? This is against curr
Алексей Захаров wrote:
>чт, 19 сент. 2019 г. в 11:00, Jay Vosburgh :
>>
>> Алексей Захаров wrote:
>>
>> >> >Once a while, one of 802.3ad slaves fails to initialize and hangs in
>> >> >BOND_LINK_FAIL state. Commit 334031219a84 ("bonding/802.3ad: fix slave
>> >> >link initialization transition state
чт, 19 сент. 2019 г. в 11:00, Jay Vosburgh :
>
> Алексей Захаров wrote:
>
> >> >Once a while, one of 802.3ad slaves fails to initialize and hangs in
> >> >BOND_LINK_FAIL state. Commit 334031219a84 ("bonding/802.3ad: fix slave
> >> >link initialization transition states") checks slave->last_link_up.
Алексей Захаров wrote:
>> >Once a while, one of 802.3ad slaves fails to initialize and hangs in
>> >BOND_LINK_FAIL state. Commit 334031219a84 ("bonding/802.3ad: fix slave
>> >link initialization transition states") checks slave->last_link_up. But
>> >link can still hang in weird state.
>> >After p
> >Once a while, one of 802.3ad slaves fails to initialize and hangs in
> >BOND_LINK_FAIL state. Commit 334031219a84 ("bonding/802.3ad: fix slave
> >link initialization transition states") checks slave->last_link_up. But
> >link can still hang in weird state.
> >After physical link comes up it send
Aleksei Zakharov wrote:
>Once a while, one of 802.3ad slaves fails to initialize and hangs in
>BOND_LINK_FAIL state. Commit 334031219a84 ("bonding/802.3ad: fix slave
>link initialization transition states") checks slave->last_link_up. But
>link can still hang in weird state.
>After physical link
Once a while, one of 802.3ad slaves fails to initialize and hangs in
BOND_LINK_FAIL state. Commit 334031219a84 ("bonding/802.3ad: fix slave
link initialization transition states") checks slave->last_link_up. But
link can still hang in weird state.
After physical link comes up it sends first two LAC
19 matches
Mail list logo
