[asterisk-bugs] [Zaptel 0011961]: set_tone_zone lock issue

[noreply at bugs.digium.com]

The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.digium.com/view.php?id=11961 
====================================================================== 
Reported By:                aprowant
Assigned To:                sruffell
====================================================================== 
Project:                    Zaptel
Issue ID:                   11961
Category:                   zaptel (the module)
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Zaptel Version:              SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 3819 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-08-2008 23:12 CST
Last Modified:              03-07-2008 15:46 CST
====================================================================== 
Summary:                    set_tone_zone lock issue
Description: 
Zaptel seems to cause a kernel panic with our new te212p (wct4xxp). I have
tried Zaptel 1.4.8 as well as 1.4 from svn. Both eventually kernel panic
(usually with in 10 minutes).

We are running Asterisk 1.4.18 (was using 1.4.17). I have reproduced it on
another server using the same card.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0007620 [patch] hard-safe -> hard-unsafe loc...
====================================================================== 

---------------------------------------------------------------------- 
 sruffell - 03-07-08 15:46  
---------------------------------------------------------------------- 
Which revision of 1.4 from svn did you try? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-07-08 15:46  sruffell       Note Added: 0083627                          
03-07-08 15:46  sruffell       Status                   assigned => feedback
======================================================================