[asterisk-bugs] [Zaptel 0010593]: Zaptel crashes kernel - zt_init_tone_state

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10593 
====================================================================== 
Reported By:                jmhunter
Assigned To:                mattf
====================================================================== 
Project:                    Zaptel
Issue ID:                   10593
Category:                   zaptel (the module)
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     assigned
Zaptel Version:             1.4.5.1  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-29-2007 13:02 CDT
Last Modified:              11-05-2007 16:20 CST
====================================================================== 
Summary:                    Zaptel crashes kernel - zt_init_tone_state
Description: 
When zaptel is compiled and installed on my system, any use of my TDM400P
card will eventually lead to a kernel crash - see attached trace.

The problem is reproducible by simply picking up a Zap channel handset. It
won't always crash straight away, though. Sometimes it takes longer to
crash, sometimes it's quicker - and I also get some really strange
"dialtones" varying from complete silence, through loud single tones, right
up to weird multiple tones similar to a fax or modem.

I don't believe this to be a hardware issue, as this system has been rock
solid under an older version of zaptel. The older zaptel versions no longer
compile cleanly under current kernels, however, so it's time for me to bite
the bullet and try to track down the cause of the crash.

Any suggestions gratefully received - where do I start?!
====================================================================== 

---------------------------------------------------------------------- 
 jmhunter - 11-05-07 16:20  
---------------------------------------------------------------------- 
Many apologies for not providing feedback sooner - I've just reviewed the
notes on this bug and realised there is no response listed after I tried
patch4! I am certain I did post a response, but I can't find it here any
longer so I'll summarise below.

I have been running Zaptel SVN-branch-1.4-r2972M with patch4 above for
approx. 6 weeks now, and have not experienced any issues whatsoever. For me
at least, patch4 has fixed the problem completely - thank you!

The chan_zap warning that I got (mentioned above) turned out to be a
configuration error on my part. When reloading chan_zap.so, the module does
not parse the "signalling=" lines from zapata.conf, and prints a warning to
that effect (telling me that chan_zap is ignoring these config lines). I
had therefore removed the "signalling=" lines from zapata.conf, believing
them to be redundant. Until my server crashed and I had to reboot it, they
were indeed redundant - they are processed on module load but not module
reload. That's a seperate issue with chan_zap, however, and not for this
bug report!

I have not yet tried patch5, as my system has been running perfectly with
patch4 since Sep 22nd. If you would like me to test it out (it seems a lot
more code? does it do anything differently?) then please let me know - but
in the meantime this is a resounding vote in favour of including patch4.

Thanks for the patch - works a treat! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-05-07 16:20  jmhunter       Note Added: 0073158                          
======================================================================