[asterisk-bugs] [Asterisk 0014057]: Deadlock chan_dahdi.c and channel.c

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14057 
====================================================================== 
Reported By:                rtrauntvein
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   14057
Category:                   Channels/chan_dahdi
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-10 17:13 CST
Last Modified:              2008-12-11 13:51 CST
====================================================================== 
Summary:                    Deadlock chan_dahdi.c and channel.c
Description: 
I have an asterisk system that has been deadlocking on a weekly basis at
least once, and we cant seem to reliably reproduce it. It is a production
system with about 25 users that is being constantly used.

Running zaptel 1.4.12.1 with a TE220 card.
(Planning on installing the DAHDI release over the weekend as next
troubleshooting step)
====================================================================== 

---------------------------------------------------------------------- 
 (0096234) putnopvut (administrator) - 2008-12-11 13:51
 http://bugs.digium.com/view.php?id=14057#c96234 
---------------------------------------------------------------------- 
My opinion is that v2 of the patch is safe to apply and will likely cause
you to not see the issue any more.  The problem is that there is still an
extremely narrow window of time under which the deadlock may still occur,
so the problem is not guaranteed to be gone just by using v2 of the patch.

You can interpret the above however you wish :)
I'm going to continue to work on this issue and try to find another way of
finding a good way of resolving this deadlock. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-11 13:51 putnopvut      Note Added: 0096234                          
======================================================================