[asterisk-bugs] [Asterisk 0017261]: 1.4.31rc1 Deadlock: Tried and failed to get Lock #1 (chan_dahdi.c): MUTEX 1063 pri_grab &pri->lock 0xe09684

Mon May 10 10:59:16 CDT 2010

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17261 
====================================================================== 
Reported By:                aragon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17261
Category:                   Channels/chan_dahdi
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.31-rc1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-29 08:53 CDT
Last Modified:              2010-05-10 10:59 CDT
====================================================================== 
Summary:                    1.4.31rc1 Deadlock: Tried and failed to get Lock
https://issues.asterisk.org/view.php?id=1 (chan_dahdi.c): MUTEX 1063 pri_grab
&pri->lock 0xe09684
Description: 
*1.4.31rc1 SVN (sorry, not sure which SVN version) deadlocks.
This has happened only once under moderate call volume but I am reporting
this issue regardless.
CentOS5.4 Xeon 2.4GHz
1GB RAM

deadlock.txt info attached includes core show locks
gdb thread apply all bt
Not optimized

====================================================================== 

---------------------------------------------------------------------- 
 (0121640) lmadsen (administrator) - 2010-05-10 10:59
 https://issues.asterisk.org/view.php?id=17261#c121640 
---------------------------------------------------------------------- 
Hmmm maybe? That issue was only resolved in trunk though... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-10 10:59 lmadsen        Note Added: 0121640                          
======================================================================