-dev@lists.fd.io
Subject: Re: [vpp-dev] : Worker Thread Deadlock Detected from vl_api_clnt_node
Hi Rajith / Dave,
We are on fdio.2005 version and see this same crash when we are doing packet
tracing.
Is there any specific patch/commit that improves the situation of this locking.
If so, Can you
Thanks Rajith for quick reply.
At this point of time, we do not have a luxury of upgrading to 20.09 in a quick
time.
Hi Dave,
Do you have any specific commit in mind that can help us to eliminate this
crash.
Really appreciate your inputs on this.
--
Thanks & Regards,
Murthy
-=-=-=-=-=-=-=-=-=-
Hi Satya,
We migrated to 20.09 in March 2021. The crash has not been observed after
that. Not sure if some commit went between 20.05 and 20.09 that has fixed
or improved the situation.
Thanks,
Rajith
On Fri, Jul 9, 2021 at 10:19 AM Satya Murthy
wrote:
> Hi Rajith / Dave,
>
> We are on fdio.20
Hi Rajith / Dave,
We are on fdio.2005 version and see this same crash when we are doing packet
tracing.
Is there any specific patch/commit that improves the situation of this locking.
If so, Can you please let us know the commit info.
--
Thanks & Regards,
Murthy
-=-=-=-=-=-=-=-=-=-=-=-
Links:
236
>
>
>
> *From:* vpp-dev@lists.fd.io *On Behalf Of *Rajith
> PR via lists.fd.io
> *Sent:* Thursday, December 3, 2020 5:55 AM
> *To:* vpp-dev
> *Subject:* [vpp-dev]: Worker Thread Deadlock Detected from
> vl_api_clnt_node
>
>
>
> Hi All,
>
>
>
>
, 2020 5:55 AM
To: vpp-dev
Subject: [vpp-dev]: Worker Thread Deadlock Detected from vl_api_clnt_node
Hi All,
We have hit a VPP Worker Thread Deadlock issue. And from the call stacks it
looks like the main thread is waiting for workers to come back to their main
loop( ie has taken the barrier
Hi All,
We have hit a VPP Worker Thread Deadlock issue. And from the call stacks it
looks like the main thread is waiting for workers to come back to their
main loop( ie has taken the barrier lock) and one of the two workers is on
spin lock to make an rpc to the main thread.
I believe this lock is
