[asterisk-bugs] [Asterisk 0011165]: Deadlock in channel.c
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Nov 13 23:51:31 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11165
======================================================================
Reported By: callguy
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11165
Category: Channels/General
Reproducibility: random
Severity: block
Priority: normal
Status: feedback
Asterisk Version: 1.4.13
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 11-05-2007 14:18 CST
Last Modified: 11-13-2007 23:51 CST
======================================================================
Summary: Deadlock in channel.c
Description:
We had what appears to be a new deadlock in channel.c today. output of core
show locks attached.
======================================================================
----------------------------------------------------------------------
enst - 11-13-07 23:51
----------------------------------------------------------------------
dklima: when I find the dead lock
core show locks
=== Thread ID: 1102494016 (pbx_thread started at [ 2627] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock http://bugs.digium.com/view.php?id=0 (channel.c):
MUTEX 5009 ast_channel_lock
&chan->lock 0x2aaad804dab8 (1)
=== Thread ID: 1076197696 (do_monitor started at [15443]
chan_sip.c restart_monitor())
=== ---> Lock http://bugs.digium.com/view.php?id=0 (chan_sip.c): MUTEX 15144
sipsock_read &netlock
0x2aaabca29580 (1)
=== ---> Lock http://bugs.digium.com/view.php?id=1 (chan_sip.c): MUTEX 4526
find_call &p->lock
0x2aaad804bc60 (2)
=== ---> Lock http://bugs.digium.com/view.php?id=2 (channel.c): MUTEX 5041
ast_channel_trylock &chan->lock
0x2aaad804dab8 (1)
then use 'gdb asterisk pidnum' debug the thread 1076197696 ,
3 0x00002aaabc7c1f22 in __ast_pthread_mutex_lock (filename=0x2aaabc815c13
"chan_sip.c", lineno=2133, func=0x2aaabc816a0f "__sip_ack",
I find in func __sip_ack try to lock the same lock which is locked by
find_call 0x2aaad804bc60
Issue History
Date Modified Username Field Change
======================================================================
11-13-07 23:51 enst Note Added: 0073625
======================================================================
More information about the asterisk-bugs
mailing list