similar to: WARNING[4033]: Avoided initial deadlock for 'Zap/63-1', 10 retries! ... + Kernel Panic!

Displaying 20 results from an estimated 50000 matches similar to: "WARNING[4033]: Avoided initial deadlock for 'Zap/63-1', 10 retries! ... + Kernel Panic!"

2006 Feb 08
1
channel.c: Avoided deadlock for '0x91a8b20', 10 retries!
Dear users, Couple of days ago I have updated my * to 1.2.4 with ZAP 1.2.3 Since the upgrade I am having these problems: Feb 7 16:21:18 WARNING[387] channel.c: Avoided deadlock for '0x91a8b20', 10 retries!$ Feb 7 16:23:16 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20', 10 retries!$ Feb 7 16:23:28 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20',
2006 Apr 05
2
What causes deadlock?
Hi What causes deadlock? Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for '0x82acb10', 10 retries! Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for '0x8298160', 10 retries! Here is the portion of the log: Apr 5 14:02:42 NOTICE[23363] chan_zap.c: Got event 18 (Ring Begin)... Apr 5 14:02:42 VERBOSE[23363] logger.c: -- Executing
2007 Apr 05
2
PRI DCHAN Errors
Hey all, I had a user complaining of calls which were dropping mid-conversation. I looked into the time of one of the calls, and saw the following: Apr 4 12:13:03 WARNING[6670] chan_zap.c: No D-channels available! Using Primary channel 28 as D-channel anyway! Apr 4 12:13:05 WARNING[6660] channel.c: Avoided initial deadlock for '0x82b8430', 10 retries! Apr 4 12:13:05 WARNING[6660]
2007 Jan 10
1
VIA EPIA DeadLock Issues
Greetings, I've been having a large number of deadlock issues lately on chan_sip occurring only on VIA EPIA ML6000 boards. I'm curious if anyone else is having similar issues. My Config (have multiple systems all running the same hardware with the same problem) VIA EPIA ML6000 1GB RAM 80GB HDD Various Digium Cards (T1 and TDM cards) Trixbox 1.2.2 (though running stock asterisk code)
2010 Nov 24
2
Avoided deadlock Error
My Asterisk is Asterisk 1.2.30.2 currently running on viciserver the problem is : Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided deadlock for '0x861f6d8', 9 retries! Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided deadlock for '0x85a6420', 9 retries! Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided
2007 Jan 27
1
Via EPIA channel_find_locked: Avoided initial deadlock
In asterisk 1.2 branch SVN 51363 zaptel svn 1980 libpri svn 393 addons svn 332 My equipment is a Via EPIA minit-itx CN10000 1.2ghz, 1gb ram and a tdm400p (4fxo). A call comes from zap, a SIP ulaw receives the call, talks for a while and when SIP users tries to park the call, then dozens of... WARNING[3853]: channel.c:781 channel_find_locked: Avoided initial deadlock for '0x91bb840', 10
2006 Jan 31
2
Asterisk hangs on 1.2.1
Anyone have any idea what's causing this or how to debug it? I'm pretty sure the root cause is with chan_sccp.so, but not sure how to prove it. I recently upgraded from CVS-head to 1.2.1 and the chan_sccp from 12-17-2005. Now, once or twice a week, I get this on the console: Jan 31 10:39:08 WARNING[10586]: channel.c:784 channel_find_locked: Avoided deadlock for '0xbf1013e0',
2007 Aug 30
0
WARNING[22292]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82f2fe0', 9 retries!
Hello! I clear remarks in Makefile: DEBUG_THREADS = -DDEBUG_THREADS -DDETECT_DEADLOCKS But same things in CLI: Aug 30 18:16:31 WARNING[22292]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82f2fe0', 9 retries! -- Zap/32-1 is proceeding passing it to Zap/31-1 -- Zap/32-1 is ringing -- Accepting call from '2177' to '7141278' on channel
2004 Dec 01
6
Avoided deadlock
Dec 1 12:08:43 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! what does this
2010 Feb 25
1
Deadlock while using MGCP on Asterisk
Hello all, I'm running Asterisk 1.2.35 with chan_mgcp activated. The process host around 2,4K users. Along the day I've got some debug reports like : Feb 24 22:25:42 DEBUG[28546] channel.c: Avoiding deadlock for 'MGCP/aaln/1 at 028421223635-1' Feb 24 22:29:04 DEBUG[28670] channel.c: Avoiding initial deadlock for 'MGCP/aaln/1 at 028421223635-1' Then, at
2008 Aug 11
1
deadalocks in asterisk
hi, i am recieving deadlocks frequently and its calls are getting hanged . Aug 11 13:13:53 WARNING[6367] channel.c: Avoided initial deadlock for '0xb6692258', 10 retries! Aug 11 13:13:54 WARNING[6367] channel.c: Avoided initial deadlock for '0xb6692258', 10 retries! Aug 11 13:13:54 WARNING[6367] channel.c: Avoided initial deadlock for '0xb78e5be8', 10 retries! Aug 11
2007 Mar 23
3
SIP/IAX peers UNREACHABLE and audio loss
Hi all, I'm having a problem with some Asterisk servers interconnected with each other using IAX (I also tried with SIP without solving the problem) Sometimes, with apparently no reason, some peers become UNREACHABLE (I have qualify=yes in iax.conf) and REACHABLE again as soon as another qualify test is made. Our users are also complaining about audio loss during their calls, apparently
2008 Jan 09
1
Help! channel_find_deadlocked: Avoided initial deadlock for ...
Hope someone can help. I have a situation where asterisk is sending a SIP CANCEL message before the Dial() timeout has hit. It doesn't always do it. Normally, we send an INVITE to the ITSP. They respond with a 100 Trying, then a 180 Ringing, or 183 Session Progress. It seems to be at this point that Asterisk starts the dial timer. Normally, when no more replies have been received by the dial
2006 Jan 10
1
avoided deadlock/channel already in use
Hello! After upgrading my production machine to 1.2.1(used to be 1.2.0) on friday i experienced strange behaviour yesterday, i received deadlock-avoided-messages and channels refusing to hangup on span1(used for inbound calls), both messages in all cases paired: Jan 9 17:40:01 WARNING[30003] chan_zap.c: Ring requested on channel 0/17 already in use on span 1. Hanging up owner. Jan 9 17:40:01
2009 Sep 08
2
1.2 AGI Deadlock
I am running 1.2.34 (also tried on 1.2.32) and whenever I launch an AGI, I get the "avoided deadlock" message below. *CLI> == Spawn extension (CONTEXT3, 6080, 8) exited non-zero on 'SIP/3211-1-081c40a8' -- Executing NoOp("SIP/3211-1-081c40a8", "") in new stack -- Executing AGI("SIP/3211-1-081c40a8", "diallocal.agi") in new
2007 May 29
2
channel_find_locked: Avoided deadlock
Hi i have 20 people calling agents calling when ever they calling i get this below error May 30 00:46:57 WARNING[2840]: channel.c:785 channel_find_locked: Avoided deadlock for '0x8b2f50', 10 retries! and the voice go choppy, and voice breakages iam using Latest SVN, any suggestion to come over this problem ram -------------- next part -------------- An HTML attachment was scrubbed...
2005 May 26
1
deadlock
All out of the blue I get these errors? Any Ideas why Please help May 26 09:54:28 WARNING[3964]: channel.c:507 ast_channel_walk_locked: Avoided initial deadlock for 'SIP/301-b9d0', 10 retries! May 26 09:54:30 WARNING[3964]: channel.c:507 ast_channel_walk_locked: Avoided initial deadlock for 'SIP/301-b9d0', 10 retries! May 26 09:54:33 WARNING[3964]: channel.c:507
2005 Jan 20
2
Chan_Capi initial deadlock
Hello, I am using chan_capi 0.3.5 and Asterisk CVS-v1-0-12/29/04-15:32:48 on a SuSE Linux 9.0 with Kernel 2.4.21-99-default In the system is a AVM C4 with one port connected to PSTN at PTP BRI and another one to an ISDN PBX with an PMP BRI. The system is running fine, but I have regualary this error, and then chan_capi is not working anymore. Jan 18 15:29:46 WARNING[2919]: Avoided initial
2006 May 17
2
Diverse servers
I currently have a single server with a few SIP and IAX upstreams for origination and termination with IAX clients. I am adding a second server that will have a much higher capacity and will be handling a larger call volume. However, this second server is not going to be geographically near the first. It will largely share the same upstreams. I would like for this to be an integrated system
2006 Nov 22
0
channel_find_locked: Avoided deadlock ... messages - What to do?
What are these? Nov 22 09:35:23 WARNING[7127]: channel.c:787 channel_find_locked: Avoided deadlock for '0xf6c06778', 10 retries! Nov 22 09:35:24 WARNING[7127]: channel.c:787 channel_find_locked: Avoided deadlock for '0xf6c06778', 10 retries! Nov 22 09:35:24 WARNING[7127]: channel.c:787 channel_find_locked: Avoided deadlock for '0xf6c06778', 10 retries! Nov 22 09:35:25