Strange message since 1.4.16

Hello,

I get followings message since Asterisk-1.4.16 until now.

It is in /var/log/asterisk/messages:

[Feb 21 18:56:37] NOTICE[10957] chan_zap.c: Avoiding deadlock…
[Feb 21 18:56:37] NOTICE[10957] chan_zap.c: Avoiding deadlock…
[Feb 21 18:56:37] NOTICE[10957] chan_zap.c: Avoiding deadlock…
[Feb 21 18:56:37] NOTICE[10957] chan_zap.c: Avoiding deadlock…
[Feb 21 18:56:37] NOTICE[10957] chan_zap.c: Avoiding deadlock…
[Feb 21 18:56:37] NOTICE[10957] chan_zap.c: Avoiding deadlock…
[Feb 21 18:56:37] NOTICE[10957] chan_zap.c: Avoiding deadlock…

Usually, when I try to restart Zap channel. I need to do it two times, sometimes Asterisk get core dump.

pbx:/var/log/asterisk# asterisk -r
Asterisk 1.4.17, Copyright © 1999 - 2007 Digium, Inc. and others.
Created by Mark Spencer markster@digium.com
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘core show license’ for details.

Connected to Asterisk 1.4.17 currently running on pbx (pid = 2342)
Verbosity is at least 6
pbxCLI> zap restart
Destroying channels and reloading zaptel configuration.
== Parsing ‘/etc/asterisk/zapata.conf’: Found
== Parsing ‘/etc/asterisk/zapata-channels.conf’: Found
[Mar 9 12:56:06] WARNING[2667]: chan_zap.c:904 zt_open: Unable to specify channel 1: Device or resource busy
[Mar 9 12:56:06] ERROR[2667]: chan_zap.c:7186 mkintf: Unable to open channel 1: Device or resource busy
here = 0, tmp->channel = 1, channel = 1
[Mar 9 12:56:06] ERROR[2667]: chan_zap.c:10527 build_channels: Unable to register channel ‘1’
[Mar 9 12:56:06] WARNING[2667]: chan_zap.c:9824 zap_restart: Reload channels from zap config failed!
[Mar 9 12:56:06] WARNING[2425]: chan_zap.c:4788 zt_read: zt_rec: Bad file descriptor
[Mar 9 12:56:06] WARNING[2425]: chan_zap.c:1643 zt_confmute: zt confmute(0) failed on channel 6: Bad file descriptor
[Mar 9 12:56:06] DEBUG[2425]: chan_zap.c:1574 set_actual_rxgain: Failed to read gains: Bad file descriptor
[Mar 9 12:56:06] WARNING[2425]: chan_zap.c:1608 restore_gains: Unable to restore gains: Bad file descriptor
[Mar 9 12:56:06] WARNING[2425]: chan_zap.c:2586 zt_hangup: Unable to set law on channel 6 to default
[Mar 9 12:56:06] WARNING[2425]: chan_zap.c:1625 zt_set_hook: zt hook failed: Bad file descriptor
[Mar 9 12:56:06] WARNING[2425]: chan_zap.c:2644 zt_hangup: Unable to hangup line Zap/6-1
[Mar 9 12:56:06] WARNING[2425]: chan_zap.c:1351 reset_conf: Failed to reset conferencing on channel 6!
– Hungup ‘Zap/6-1’
== Spawn extension (boldsoft, 99133572, 1) exited non-zero on 'SIP/804-082b8570’
pbx
CLI> zap restart
Destroying channels and reloading zaptel configuration.
== Parsing ‘/etc/asterisk/zapata.conf’: Found
== Parsing ‘/etc/asterisk/zapata-channels.conf’: Found
– Registered channel 1, FXS Kewlstart signalling
– Registered channel 2, FXS Kewlstart signalling
– Registered channel 3, FXS Kewlstart signalling
– Registered channel 4, FXS Kewlstart signalling
– Registered channel 5, FXS Kewlstart signalling
– Registered channel 6, FXS Kewlstart signalling
– Registered channel 7, FXS Kewlstart signalling
– Registered channel 8, FXS Kewlstart signalling
– Registered channel 9, FXO Kewlstart signalling
– Registered channel 10, FXO Kewlstart signalling
– Registered channel 11, FXO Kewlstart signalling
– Registered channel 12, FXO Kewlstart signalling
– Automatically generated pseudo channel

What is problem of Deadlock message and Zap problem?

I’m getting the same problem. We’re having a lot of dropped calls and we see this error often. Does anyone know what the problem is?