[asterisk-bugs] [Asterisk 0011080]: SIP channel stops processing calls, but no apparent deadlock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11080 
====================================================================== 
Reported By:                callguy
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   11080
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-24-2007 15:58 CDT
Last Modified:              12-05-2007 11:18 CST
====================================================================== 
Summary:                    SIP channel stops processing calls, but no apparent
deadlock
Description: 
Approximately once per week we are seeing asterisk stop processing SIP
calls. The behavior is the same as a deadlock, but core show locks does not
show any evidence that there is a deadlock. 

The only way to resolve is to restart asterisk. 

output of:
core show locks
info thread
thread apply all bt

from the running process is attached.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0011165 Deadlock in channel.c
====================================================================== 

---------------------------------------------------------------------- 
 callguy - 12-05-07 11:18  
---------------------------------------------------------------------- 
russell: the issue that we're all having is that when this occurs, the
console locks up as well and there's no way to get any output of core show
locks (or any output of any sort). That's why we've been looking at the gdb
output from the running process, at least it give some clue since we can't
get the lock debugging info in this case. 

I've only had a single instance where I was able to capture core show
locks (which  is posted to bug 11165). The backtrace on that running
process shows it to be the same issue as what's posted here. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-05-07 11:18  callguy        Note Added: 0074834                          
======================================================================