v-boun...@lists.digium.com
<asterisk-dev-boun...@lists.digium.com> on behalf of Joshua Colp
<jc...@digium.com>
Sent: 16 February 2017 12:33
To: asterisk-dev@lists.digium.com
Subject: Re: [asterisk-dev] Deadlock GIT 13
On Thu, Feb 16, 2017, at 08:20 AM, Ross Beer wrote:
> Unfortunately, the c
On Thu, Feb 16, 2017, at 08:20 AM, Ross Beer wrote:
> Unfortunately, the commit did not resolve the issue.
>
>
> This looks related to a lock inversion between channel hang up and the
> bridging code. There is an issue open for this
>
rds,
Ross
From: asterisk-dev-boun...@lists.digium.com
<asterisk-dev-boun...@lists.digium.com> on behalf of Ross Beer
<ross.b...@outlook.com>
Sent: 08 February 2017 18:17
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Deadlock GIT 13
Hi Mark,
I
f Mark Michelson
<mmichel...@digium.com>
Sent: 08 February 2017 17:55
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Deadlock GIT 13
On 02/08/2017 11:26 AM, Ross Beer wrote:
Hi,
I'm getting a deadlock every so often with asterisk 13 GIT. There are a lot of
low level
On 02/08/2017 11:26 AM, Ross Beer wrote:
Hi,
I'm getting a deadlock every so often with asterisk 13 GIT. There are
a lot of low level locks:
#0 0x7f64ca6f052d in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f64cdcc9700 (LWP 20745))]
#0
Hi,
I'm getting a deadlock every so often with asterisk 13 GIT. There are a lot of
low level locks:
#0 0x7f64ca6f052d in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f64cdcc9700 (LWP 20745))]
#0 0x7f64ca6f052d in nanosleep () at /lib64/libc.so.6
#1
