[asterisk-bugs] [Asterisk 0017854]: Error destroying mutex &thread->lock: Device or resource busy

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17854 
====================================================================== 
Reported By:                bwg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17854
Category:                   Channels/chan_iax2
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 273055 
Request Review:              
====================================================================== 
Date Submitted:             2010-08-12 22:29 CDT
Last Modified:              2010-08-16 13:55 CDT
====================================================================== 
Summary:                    Error destroying mutex &thread->lock: Device or
resource busy
Description: 
Hi,

Got these 3 error messages which caused Asterisk to crash :

chan_iax2.c: Error destroying mutex &thread->lock: Device or resource
busy.

sched.c: (ast_sched_del): Error obtaining mutex: Invalid argument

sched.c: (ast_sched_del): mutex '&con->lock' freed more times than we've
locked!

Have attached a CLI trace, iax2.conf dundi.conf but could not get a core
trace.

Cheers,
====================================================================== 

---------------------------------------------------------------------- 
 (0125976) lmadsen (administrator) - 2010-08-16 13:55
 https://issues.asterisk.org/view.php?id=17854#c125976 
---------------------------------------------------------------------- 
If I remove the configuration file from the issue then it cannot be worked
on by a developer. The first person to triage this issue is not necessarily
(and is unlikley to be) the person working on the issue.

Please upload a configuration file that can be left attached to the issue
so we can move this forward. I'm leaving this in feedback until that can be
done.

Also, likely we will need a backtrace of the issue to move this forward.
The chances of us reproducing the issue is unlikely.

~~~~~~~~~~~~~

Thank you for your bug report. In order to move your issue forward, we
require a backtrace from the core file produced after the crash. Please see
the doc/backtrace.txt file in your Asterisk source directory.

Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the
Compiler Flags section, then:

make install

after enabling, reproduce the crash, and then execute the instructions in
doc/backtrace.txt.

When complete, attach that file to this issue report. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-16 13:55 lmadsen        Note Added: 0125976                          
======================================================================