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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
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:                     closed
JIRA:                        
Reviewboard Link:            
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-10-14 08:33 CDT
Last Modified:              2010-12-02 08:51 CST
====================================================================== 
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.

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

---------------------------------------------------------------------- 
 (0129274) sruffell (administrator) - 2010-12-02 08:51
 https://issues.asterisk.org/view.php?id=18142#c129274 
---------------------------------------------------------------------- 
Just taking another note here:  I was digging around the kernel sources
about something unrelated when I came across a comment about threads in
interruptible sleeps are not added the load averages.  I then looked in the
kernel/sched.c:calc_load_fold_active function in the linux kernel and see
that threads in uninterruptible sleeps are actually added to the load
average.

Sooooo...it'll probably be worth changing the wait_for_completion_timeout
calls in t1_getreg to wait_for_completion_interruptible_timeout in order to
reduce the impact of the alarm checking thread on the global load average. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-02 08:51 sruffell       Note Added: 0129274                          
======================================================================