[asterisk-bugs] [Zaptel 0011961]: set_tone_zone lock issue
noreply at bugs.digium.com
noreply at bugs.digium.com
Sat Feb 9 14:24:58 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11961
======================================================================
Reported By: aprowant
Assigned To:
======================================================================
Project: Zaptel
Issue ID: 11961
Category: zaptel (the module)
Reproducibility: always
Severity: crash
Priority: normal
Status: new
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: 02-09-2008 14:24 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.
======================================================================
----------------------------------------------------------------------
aprowant - 02-09-08 14:24
----------------------------------------------------------------------
Possible as it could explain why it is not reproduce able if i make a half
dozen calls at once. Maybe someone disconnects and a call is sent to that
channel while still locked? Any way I could test this to verify? Can the
locks debugging code be disabled?
I attached the full crash dump as crash.txt.
Issue History
Date Modified Username Field Change
======================================================================
02-09-08 14:24 aprowant Note Added: 0081978
======================================================================
More information about the asterisk-bugs
mailing list