[asterisk-bugs] [DAHDI-linux 0018142]: The TE122 and dadi produces an unusual high load

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Oct 14 09:48:50 CDT 2010


The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18142 
====================================================================== 
Reported By:                foxfire
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   18142
Category:                   wcte12xp
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2010-10-14 08:33 CDT
Last Modified:              2010-10-14 09:48 CDT
====================================================================== 
Summary:                    The TE122 and dadi produces an unusual high load
Description: 
When starting dahdi_linux and there is a TE122 installed in the machine in
a few seconds the load raizes from 0.00 to over 0.50 .
This happens always, i have no problem with any other digium card only the
TE122.
I stopped all services and only started dahdi.
Disabling the mg2 echocancler does not help.
I consider this major because call quality is affected due to the load
increasing to values.

====================================================================== 

---------------------------------------------------------------------- 
 (0128021) sruffell (administrator) - 2010-10-14 09:48
 https://issues.asterisk.org/view.php?id=18142#c128021 
---------------------------------------------------------------------- 
foxfire:  Most likely your best bet is going to be to contact Digium
technical support for help with triaging this issue.

However, some things I wanted to ask first.  If this only happens with
Asterisk 1.6, what do you mean that the load is still there before loading
Asterisk 1.6?  How are you determining the load is 50% (or was it 0.50%). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-14 09:48 sruffell       Note Added: 0128021                          
2010-10-14 09:48 sruffell       Status                   new => feedback     
======================================================================




More information about the asterisk-bugs mailing list