[Kamailio-Users] kamailio / deadlock3

Henning Westerholt henning.westerholt at 1und1.de
Thu Jan 28 14:06:08 CET 2010

On Thursday 28 January 2010, Aymeric Moizard wrote:
> here is the backtrace I have. unfortunatly without debug symbol!
> I found the same for many of the kamailio process. "sched_yield"
> is pending for ever. My system is a debian/etch.
> #0  0xffffe424 in __kernel_vsyscall ()
> #1  0xb7cef4ac in sched_yield () from /lib/tls/i686/cmov/libc.so.6
> #2  0x080a93fd in tcp_send ()
> #3  0xb7975679 in send_pr_buffer () from /usr/lib/kamailio/modules/tm.so
> #4  0xb79789ac in t_forward_nonack () from /usr/lib/kamailio/modules/tm.so
> #5  0xb7974784 in t_relay_to () from /usr/lib/kamailio/modules/tm.so
> #6  0xb7983a11 in load_tm () from /usr/lib/kamailio/modules/tm.so
> #7  0x081cf810 in mem_pool ()
> #8  0x00000000 in ?? ()
> I guess most t_relay operation towards my "mobipouce.com" domain
> with one IP being down breaks each kamailio process one after the
> other... I'm not sure every such t_relay operation is always breaking
> exactly one thread each time.
> I went through the lock/unlock of tcp_main.c but it seems every
> lock has an unlock at least...

Hi Aymeric,

i remember that we observed this "sched_yield" problems on one old 0.9 system 
after some time (like weeks or month). We did not found the solution in this 
case, after a restart it was gone again.. 

You mentioned in an earlier mail that you see this related to UDP traffic, but 
in the log file and also in your investigations you think its related to TPC?



Viele Grüße,


More information about the sr-users mailing list