[asterisk-bugs] [Asterisk 0016608]: [patch] Deadlock on &(&channels)->lock

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16608 
====================================================================== 
Reported By:                sergee
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   16608
Category:                   Channels/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Target Version:             1.6.0.28
Asterisk Version:           SVN 
JIRA:                       SWP-732 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 237060 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-14 15:04 CST
Last Modified:              2010-04-15 17:02 CDT
====================================================================== 
Summary:                    [patch] Deadlock on &(&channels)->lock
Description: 
I've got 2 deadlocks in 3 days. It happens in a peak hours, with more then
a hundred calls in the system.

I've got 2 files 1 with "core show locks" - from the first deadlock (the
day before yesterday), second file - with output from gdb (intho thread,
thread apply all bt, thread apply all bt full) - from today's deadlock.
====================================================================== 

---------------------------------------------------------------------- 
 (0120519) tilghman (administrator) - 2010-04-15 17:02
 https://issues.asterisk.org/view.php?id=16608#c120519 
---------------------------------------------------------------------- 
1.  If you have no problems without any of these patches, then we can close
this issue with no patches.

2.  If you aren't receiving RTP, that would certainly explain why the RTP
timeout is occurring.  This suggests some other interaction is not properly
occurring with the Zoiper client.  Please provide SIP traces for both
calls. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-15 17:02 tilghman       Note Added: 0120519                          
======================================================================