We have a Digium TDM400 card with 4 FXS ports. Every so often (roughly once every month or two) it will stop answering incoming calls, but process outgoing calls just fine. Unloading all the zaptel modules and reloading does not help, but does result in the following error logs:

Sep  4 12:32:47 astonish kernel: Removing device entry for Tau32-PCI
Sep  4 12:32:47 astonish kernel: Unloaded kld character device driver
Sep  4 12:32:47 astonish kernel: Zapata Telephony Interface Unloaded
Sep 4 12:32:47 astonish kernel: Warning: memory type zaptel leaked memory on destroy (2 allocations, 32 bytes leaked). Sep 4 12:33:32 astonish kernel: Zapata Telephony Interface Registered on major 196
Sep  4 12:33:32 astonish kernel: Echo Canceller: MG2
Sep 4 12:33:32 astonish kernel: FXS device: vendor=e159 device=1 subvendor=b1d9 Sep 4 12:33:32 astonish kernel: wcfxs0: <Wildcard TDM400P REV I> port 0xd000-0xd0ff mem 0xd0300000-0xd0300fff irq 20 at device 4.0 on pci5 Sep 4 12:33:32 astonish kernel: FXS Attach for wcfxs0: deviceID : 0xe159
Sep  4 12:33:32 astonish kernel: wcfxs0: [FAST]
Sep  4 12:33:32 astonish kernel: Freshmaker version: 73
Sep  4 12:33:32 astonish kernel: Freshmaker passed register test
Sep 4 12:33:33 astonish kernel: VoiceDAA did not bring up ISO link properly!
Sep  4 12:33:33 astonish kernel: Module 0: Not installed
Sep 4 12:33:33 astonish kernel: VoiceDAA did not bring up ISO link properly!
Sep  4 12:33:33 astonish kernel: Module 1: Not installed
Sep 4 12:33:34 astonish kernel: VoiceDAA did not bring up ISO link properly!
Sep  4 12:33:34 astonish kernel: Module 2: Not installed
Sep 4 12:33:34 astonish kernel: VoiceDAA did not bring up ISO link properly!
Sep  4 12:33:34 astonish kernel: Module 3: Not installed
Sep  4 12:33:34 astonish kernel: FXS detach!
Sep  4 12:33:34 astonish kernel: We failed: 5
Sep  4 12:33:34 astonish kernel: device_attach: wcfxs0 attach returned 5


Rebooting the whole machine fixes the problem. FreeBSD 6.2-RELEASE. zaptel-1.4.6_2, Asterisk 1.4.x (the problem has been happening for a while).

Is it possible that the memory leak identified in this log grows over time and eventually causes the kernel/module to exhibit problems? Is there anything we can run to provide better debugging info if this happens again?


Thanks for any help in advance.

Ari Maniatis



-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A


Attachment: PGP.sig
Description: This is a digitally signed message part

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

Asterisk-BSD mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-bsd

Reply via email to