|Summary:||ASTERISK-16561: Error destroying mutex &thread->lock: Device or resource busy|
|Reporter:||Barry GATEFAIT (bwg)||Labels:|
|Date Opened:||2010-08-12 22:29:01||Date Closed:||2011-06-07 14:00:33|
|Environment:||Attachments:||( 0) dundi.conf|
( 1) full.23aug10.txt
( 2) gdb_23aug10.txt
( 3) iax.conf
( 4) locks_23aug10.txt
( 5) Pb_locks_13aout10.txt
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.
****** ADDITIONAL INFORMATION ******
/root/asterisk-svn/include/asterisk/lock.h:461 __ast_pthread_mutex_destroy: chan_iax2.c line 11295 (iax2_process_thread_cleanup): Error destroying mutex &thread->lock: Device or resource busy.
/root/asterisk-svn/include/asterisk/lock.h:599 __ast_pthread_mutex_lock: sched.c line 472 (ast_sched_del): Error obtaining mutex: Invalid argument
[Aug 13 11:34:34] ERROR: /root/asterisk-svn/include/asterisk/lock.h:705 __ast_pthread_mutex_unlock: sched.c line 493 (ast_sched_del): mutex '&con->lock' freed more times than we've locked!
[Aug 13 11:34:34] ERROR: /root/asterisk-svn/include/asterisk/lock.h:733 __ast_pthread_mutex_unlock: sched.c line 493 (ast_sched_del): Error releasing mutex: Invalid argument
|Comments:||By: Barry GATEFAIT (bwg) 2010-08-12 22:44:08|
Please copy conf file and remove from issue.
By: Leif Madsen (lmadsen) 2010-08-16 13:55:56
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:
after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt.
When complete, attach that file to this issue report. Thanks!