[asterisk-users] VIA EPIA DeadLock Issues

[Raymond McKay]

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)
Asterisk Versions 1.2.12 - 1.2.14 - with and without metermaid patch

Problem seems to happen more on systems that use parking lots.  The system will run for around 24 hours or so fine, and then mysteriously, without any errors leading up to it,  will stop being able to send calls to the chan_sip.  System from that point on reports the following in the logs.

Dec 13 12:07:04 DEBUG[16415] chan_zap.c: Took Zap/1-1 off hook
Dec 13 12:07:04 VERBOSE[16415] logger.c:     -- Executing Wait("Zap/1-1", "1") in new stack
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 WARNING[2049] channel.c: Avoided initial deadlock for '0x9896848', 10 retries!
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80'
Dec 13 12:07:04 WARNING[2049] channel.c: Avoided initial deadlock for '0x9896848', 10 retries!

attempting to stop asterisk from the CLI causes the CLI to become unresponsive and a trace shows chan_sip goes into a mutex_wait state. 

Anybody seen this? Have a fix?

Raymond McKay
President
RAYNET Technologies LLC
http://www.raynettech.com
(860) 693-2226 x 31
Toll Free (877) 693-2226
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070110/8b9e87f4/attachment-0001.htm