[Asterisk-Dev] Wildcard TDM400P dies every few weeks...cause?

[Rich Adamson]

> > Have you guys tried unloading the modules and reloading them (modprobe
> > -r)?  This usually fixes any problems with my X100p's ..  Might save
> > you a reboot.
> The same works for me, i.e. an unload/load sequence clears the problem
> out.  So now we have:
> - some people experience this problem but not everybody
> - driver unload/load fixes the problem
> That is still not enough to point the finger at either the hardware or
> the software, does it?
> Is anyone familiar enough with the TDM400 driver sources to know if
> there is some debugging that could be stuck in there to help us flush
> this problem out?

You can use the following, but thus far the debug output has not
provided any useful info in terms of diagnosing the problem. Probably
need more debug statements in the src.

Debug of Asterisk Drivers (kernel modules)

In /etc/sysconfig/zaptel, uncomment the debug line.
  TELEPHONY=yes
  # DEBUG=yes

In /etc/syslog.conf, add a line like:
  kern.*  /var/log/kernel 
and then execute:
  kill -SIGHUP `cat /var/run/syslogd.pid`

Notes:
1. The DEBUG=yes is read by  /etc/rc.d/init.d/zaptel and "debug=1" 
is passed to the kernel modules when each module is loaded. (Debug=1 
can be changed to debug=5 or whatever if needed.)
2. The "printk" statements in the modules (e.g., wctdm.c) write to 
the klogd faiclity whick sends the log mesage to syslogd (as a kern 
facility), which is then written to the /var/log/kernel file.