This started showing up a few upgrades ago. It always avoids a deadlock, for SIP and IAX, it's friggin annoying but I don't see any actual issues, everything works as normal.
The most common device it "avoids" a deadlock on is my Cisco 3640 router. I have 6 Voice T1/PRI's plugged into it, it converts it to/from SIP. My Asterisk server will go to push a call to the Cisco via SIP and I get that message quite often, but the call goes through perfectly. Seems like a waste to log it if nothing is actually wrong and everything works normal. I can't seem to find out if it's giving me a warning about something that should not occur. I've rebooted the Cisco 3640 and my Asterisk server to no Avail. I'm using a Super Micro Celeron 2.8ghz w/ 512mb of RAM and a 40gb IDE hard drive, running Gentoo 2004.3; No digium hardware, just zaptel/zaprtc w/ rtcsetup running in the background. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paradise Dove Sent: Tuesday, January 25, 2005 3:10 PM To: [EMAIL PROTECTED]; Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Avoided deadlock it would help to know all the possible causes for this warning, something like: - kernel - hardware latency (MB, cpu, ...) - buggy sip device - lack of resource - ... just let us know if anybody knows. thanks, Paradise Dove On Mon, 24 Jan 2005 11:28:34 -0600, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Brian West wrote: > > >Repeat after me... WARNING != ERROR. This is just letting you know that it > >walked the channel list and did avoid a dead lock by not trying to grab a > >lock on a channel that's already locked. > > > > if (ast_mutex_trylock(&l->lock)) { > > if (retries < 10) > > ast_log(LOG_DEBUG, "Avoiding initial deadlock for > >'%s'\n", l->name); > > else > > ast_log(LOG_WARNING, "Avoided initial deadlock for '%s', > >%d retries!\n", l->name, retries); > > > > > >Read the code it tells you... channel.c > > > >bkw > > > > > > > >>I'd suggest posting a bug if you haven't already and if you have purchased > >>any Digium products I would recommend calling them as well. The > >>ast_channel_walk_locked error is a rare and hard to diagnose problem and > >>the > >>bug trackers and Digium would be the best people to help you. > >> > >> > > > > > >_______________________________________________ > >Asterisk-Users mailing list > >[email protected] > >http://lists.digium.com/mailman/listinfo/asterisk-users > >To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > > _______________________________________________ > Asterisk-Users mailing list > [email protected] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
