[asterisk-bugs] [JIRA] (ASTERISK-22857) Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211909#comment-211909 ] 

Matt Jordan commented on ASTERISK-22857:
----------------------------------------

On symbols:

It depends on if you've replaced all of the modules that were compiled previously with those that have the symbols. It's possible that some of the modules that are getting loaded weren't compiled with those options.

The deadlock here appears to be occurring when {{defer_full_frame}} is called. Thread 0xb6f6bb90 is blocked while obtaining the lock for {{&to_here->lock}} during {{defer_full_frame}}, while at the same time it holds the {{active_list}} lock.

Unfortunately, what I can't find given the current information is the thread that has itself locked, while holding the {{active_list}} lock. The {{core show locks}} doesn't show this information, which in itself is very odd (as it should), and the {{gdb}} backtrace doesn't show all of the information due to a lack of symbols. Looking at the code, if there was a call to {{signal_condition}} that occurred while {{active_list}}'s lock was held, I would expect this to occur - but I don't see that happening either.

Just to confirm - do you have any patches to {{chan_iax2}}?
                
> Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)
> ----------------------------------------------------------
>
>                 Key: ASTERISK-22857
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22857
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: SVN, 11.6.0
>         Environment: 64 bit CentOS, 4GB RAM
>            Reporter: David Brillert
>            Severity: Critical
>         Attachments: core show locks_gdb thread apply all bt full.txt
>
>
> Full deadlock no call processing, no SIP traffic.
> GDB output DONT_OPTIMIZE DEBUG_THREADS BETTER_BACKTRACES thread apply all bt full.txt attached.  The deadlock occurred overnight while the system was idle.
> It is happening on multiple production servers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira