[asterisk-bugs] [JIRA] Commented: (ASTERISK-20212) Deadlock / TCP SIP Stack

[Mark Michelson (JIRA)]

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

Mark Michelson commented on ASTERISK-20212:
-------------------------------------------

If I don't find anything myself, then I may supply a patch where I've added in extra debugging statements. If I do that, then I'd need for you to get me a debug log when this happens so I can see if there's anything fishy. I'd need to devise such a patch first though. Thanks for offering to help out!

> Deadlock / TCP SIP Stack
> ------------------------
>
>                 Key: ASTERISK-20212
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20212
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/TCP-TLS
>    Affects Versions: 10.7.0
>         Environment: CentOS 5.7 / Asterisk 10.7.0
>            Reporter: Phil Ciccone
>         Attachments: backtrace-threads.txt, core-show-locks.txt
>
>
> We have been experiencing Asterisk deadlocks for the past week, from at the time, what seemed like nowhere. We upgraded to the latest 10.7.0 stable and enabled the debug flag and disabled optimizations in hopes to catch the deadlock. It seems from looking at the locks we have some sort of problem with our TCP connected SIP devices. Things are now starting to make sense as connecting TCP SIP devices is something newer that we started to do. The deadlocks we experience happen anywhere from every-other-day to several times a day, all involving a restart. Would you be so kind as to look at the attached backtrace and locks output?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira