Summary:ASTERISK-27840: Deadlock bridge_channel.c line 2660 (bridge_channel_internal_join)
Reporter:David Brillert (aragon)Labels:
Date Opened:2018-05-04 13:01:53Date Closed:2018-05-21 17:44:38
Versions:13.21.0 Frequency of
duplicatesASTERISK-27094 res_fax: Deadlock when using Local channels and fax gateway
Environment:EL6 x64Attachments:( 0) thread-traces.1.txt
Description:Asterisk 13.21 is frequently deadlocking in chan_sip
Attaching core show locks output and gdb thread apply all bt in attachment thread-traces.1.txt
Comments:By: Asterisk Team (asteriskteam) 2018-05-04 13:01:54.151-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: George Joseph (gjoseph) 2018-05-07 08:50:34.714-0500

Hi David,

Did this just start happening with asterisk 13.21 or has this happened with earlier versions?

Can you get us the full backtrace/lock information?

By: David Brillert (aragon) 2018-05-07 08:56:13.259-0500

The server was previously Asterisk 11.25
Upgrading the customer to 13.21 and the deadlocks were very frequent.
Downgraded him back to 11.25

After looking at the core show locks I think this might be a duplicate of ASTERISK-27094

By: George Joseph (gjoseph) 2018-05-07 09:05:32.466-0500

It does look like the locks are in the same place.  I realize you reverted the customer but if you could still get us the full backtrace/lock info on 13.21 it'd help greatly.

By: David Brillert (aragon) 2018-05-07 09:08:39.239-0500


The deadlock info is already attached to the bug report

Scroll down past the core show locks output and you will see the full gdb trace.

By: George Joseph (gjoseph) 2018-05-07 09:11:47.220-0500

Sorry David,  That has only partial info.  The backtrace isn't a "full" backtrace and we need to see what else is going on in the process at a detailed level.


By: David Brillert (aragon) 2018-05-07 09:17:39.737-0500

Sorry wasn't aware of ast_coredumper.  That is new to me.
Also sorry that this customer will have to remain on Asterisk 11 until I can reproduce this deadlock on a non production system.  Until then I hope the gdb output can help.

By: David Brillert (aragon) 2018-05-09 15:12:13.766-0500

Well now I can reproduce the deadlock 100% of the time so I put the details into my parent ticket ASTERISK-27094
Done on my lab system so I can quickly test anything required.

By: Richard Mudgett (rmudgett) 2018-05-21 17:44:38.134-0500

Closing as duplicate of ASTERISK-27094