RE: [Asterisk-Users] Chan_Capi initial deadlock

2005-02-03 Thread Felix Deierlein
Hi,

I had applied the patch and it got much better. Now I only have problems
every two days

eb  3 14:04:12 WARNING[23065]: channel.c:472 ast_channel_walk_locked:
Avoided initial deadlock for 'CAPI[contr1/1429092]/279', 10 retries!
Feb  3 14:04:12 WARNING[23065]: channel.c:472 ast_channel_walk_locked:
Avoided initial deadlock for 'CAPI[contr1/1429092]/279', 10 retries!
Feb  3 14:04:12 WARNING[23065]: channel.c:472 ast_channel_walk_locked:
Avoided initial deadlock for 'CAPI[contr1/1429092]/279', 10 retries!


Any idea?


Regards

Felix 


  Jan 18 16:00:09 WARNING[2919]: Avoided initial deadlock for
  'CAPI[contr1/1429092]/128', 10 retries!
 
  2.) Patch to chan_capi
  I did not tried it. The patch should solute that problems and enable
  faxing? Has anybody experiences with it? If there is a 
 problem why is
  not kapejod solving that?
 
 You should try :)
 
 If you don't want the fax support, you can just change this line :
 
 --- original/chan_capi.c Fri Aug 13 12:07:28 2004
 +++ chan_capi/chan_capi.c Wed Oct 27 18:55:32 2004
 @@ -556,7 +556,7 @@
   }
   }
   // wait for the B3 layer to go down
 - while (i-state != CAPI_STATE_CONNECTED) {
 + while ((i-state != CAPI_STATE_CONNECTED)  (i-state !=
 CAPI_STATE_DISCONNECTED)) {
   usleep(1);
   }
  }
 
 kapejod is (was ?) quite unresponsive.
 
 -- 
 Carl
 
 ___
 Asterisk-Users mailing list
 Asterisk-Users@lists.digium.com
 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
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Chan_Capi initial deadlock

2005-02-03 Thread Carl Sempla
On Thursday, 03 February, 2005 13:54 : Felix Deierlein
[EMAIL PROTECTED] wrote:

 I had applied the patch and it got much better. Now I only have
 problems every two days

 eb  3 14:04:12 WARNING[23065]: channel.c:472 ast_channel_walk_locked:
 Avoided initial deadlock for 'CAPI[contr1/1429092]/279', 10 retries!
 Feb  3 14:04:12 WARNING[23065]: channel.c:472 ast_channel_walk_locked:
 Avoided initial deadlock for 'CAPI[contr1/1429092]/279', 10 retries!
 Feb  3 14:04:12 WARNING[23065]: channel.c:472 ast_channel_walk_locked:
 Avoided initial deadlock for 'CAPI[contr1/1429092]/279', 10 retries!

 Any idea?

When you have this message, attach gdb to asterisk and type :
thread apply all bt
in the list, select the lastest asterisk function, just before libc, and
type frame (this number).
Example :

(gdb) thread apply all bt

Thread 13 (Thread 19469 (LWP 3466)):
#0  0x4016bde1 in nanosleep () from /lib/libc.so.6
#1  0x40195e8e in usleep () from /lib/libc.so.6
#2  0x402af5f2 in capi_activehangup (c=0x40508ba8) at chan_capi.c:563
#3  0x402af7c7 in capi_hangup (c=0x40508ba8) at chan_capi.c:606
#4  0x0805945c in ast_hangup (chan=0x40508ba8) at channel.c:741
#5  0x08072b7f in ast_pbx_run (c=0x40508ba8) at pbx.c:1968
#6  0x08079036 in pbx_thread (data=0x40508ba8) at pbx.c:1980
#7  0x400200ba in pthread_start_thread () from /lib/libpthread.so.0

(gdb) frame 2
#2  0x402af5f2 in capi_activehangup (c=0x40508ba8) at chan_capi.c:563
563 usleep(1);


And past the results of these commands.

Good luck

-- 
Carl


___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[Asterisk-Users] Chan_Capi initial deadlock

2005-01-20 Thread Felix Deierlein
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 deadlock for
'CAPI[contr1/1429092]/128', 10 retries!

Jan 18 16:00:09 WARNING[2919]: Avoided initial deadlock for
'CAPI[contr1/1429092]/128', 10 retries!

I have searched the archives and found two hints:
1.) Hard disk   
2.) Patch to chan_capi

To 1.)
I do not think that is the problem. It is an older PIII 500 but with only 5
users there should not be a problem?
top shows 92 to 98 % processor idle time.

To 2.)
I did not tried it. The patch should solute that problems and enable faxing?
Has anybody experiences with it? If there is a problem why is not kapejod
solving that?

I hope you could help me, I have some really angry customers.

Regards 

Felix

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Chan_Capi initial deadlock

2005-01-20 Thread Carl Sempla
On Thursday, 20 January, 2005 14:42 : Felix Deierlein
[EMAIL PROTECTED] wrote:

 Jan 18 16:00:09 WARNING[2919]: Avoided initial deadlock for
 'CAPI[contr1/1429092]/128', 10 retries!

 2.) Patch to chan_capi
 I did not tried it. The patch should solute that problems and enable
 faxing? Has anybody experiences with it? If there is a problem why is
 not kapejod solving that?

You should try :)

If you don't want the fax support, you can just change this line :

--- original/chan_capi.c Fri Aug 13 12:07:28 2004
+++ chan_capi/chan_capi.c Wed Oct 27 18:55:32 2004
@@ -556,7 +556,7 @@
  }
  }
  // wait for the B3 layer to go down
- while (i-state != CAPI_STATE_CONNECTED) {
+ while ((i-state != CAPI_STATE_CONNECTED)  (i-state !=
CAPI_STATE_DISCONNECTED)) {
  usleep(1);
  }
 }

kapejod is (was ?) quite unresponsive.

-- 
Carl

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users