[Asterisk-Users] Avoided deadlock

[Richard Lyman]

mattf wrote:

> Hello,
> 
> I had this problem a few months ago on a machine that I did a lot of
> recording on. It was caused by slow disk access time. Asterisk would wait
> for something to write to disk and basically freeze everything. It would
> always eventually happen to the same machine no matter if I wiped it
> completely and did a full reinstall. I fixed it by buying 4 new 320-SCSI
> drives and a new 320SCSI RAID card, no problems since then(6 months).
> 
> I did report this to Digium several times, they were even in my machine a
> few times to monitor it, they had no clue what was causing it, and the
> ast_channel_walk_locked bug has no documentation anywhere about it(not much
> help to look in the code either).
> 
> Hope this helps.
> 
> MATT---
> 
> 
> 
> -----Original Message-----
> From: Bartosz Jozwiak [mailto:bartek at cq-link.sr]
> Sent: Wednesday, December 01, 2004 6:40 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] Avoided deadlock
> 
> 
> 
> 
> 
> 
>>at the same time I have also this notice log.
>>this makes my problem more meaningful. 
>>i think it might be a bug inside *. (am i right?)
>>
>>Dec  1 12:44:46 NOTICE[6189]: Disconnecting call 'SIP/2502-6303' for
>>lack of RTP activity in 4794 seconds
>>Dec  1 12:44:47 NOTICE[6189]: Disconnecting call 'SIP/2502-6303' for
>>lack of RTP activity in 4795 seconds
>>Dec  1 12:44:47 NOTICE[6189]: Disconnecting call 'SIP/2502-6303' for
>>lack of RTP activity in 4795 seconds
>>
>>Paradise Dove
>>
>>
>>>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 warning really mean? I have tones of them!!!!!
>>>does it have any side effect on my * box? 'cose I've recently had
>>>random seg. faults on my box.
>>>I'm using latest CVS -r v1-0
> 
> 
> I have the same problem as you. But so far did not find an asnwer for it.
> 
> Bartosz
i had this issue and it was solved by fresh install of FC2 (i was 
using RH8)