[asterisk-bugs] [DAHDI-linux 0015070]: BUG: soft lockup - CPU#0 stuck for 10s! @dahdi_receive

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15070 
====================================================================== 
Reported By:                bill_mcgonigle
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   15070
Category:                   dahdi (the module)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
JIRA:                        
Resolution:                 fixed
Fixed in Version:           2.3.0
====================================================================== 
Date Submitted:             2009-05-08 18:21 CDT
Last Modified:              2009-09-23 23:00 CDT
====================================================================== 
Summary:                    BUG: soft lockup - CPU#0 stuck for 10s!
@dahdi_receive
Description: 
I'm running the elastix distribution, which recently switched from zaptel
to dahdi, I believe.

Now I frequently experience system unresponsiveness (console/net/etc) and
get these messages on the console and in dmesg.  dahdi_receive seems to be
on the top of the stack in each case.

Kernel is: 2.6.18-92.1.22.el5
Asterisk is: 1.4.24.1-0

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

---------------------------------------------------------------------- 
 (0111296) sruffell (administrator) - 2009-09-23 23:00
 https://issues.asterisk.org/view.php?id=15070#c111296 
---------------------------------------------------------------------- 
I'm going to assume that this was related to the dahdi_dummy commit that is
in both the trunk and the 2.2 branch
(https://origsvn.digium.com/svn/dahdi/linux/branches/2.2@6934)

So this will be the next 2.2 release after 2.2.0.2 and when 2.3.0 comes
out. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-23 23:00 sruffell       Note Added: 0111296                          
2009-09-23 23:00 sruffell       Status                   assigned => resolved
2009-09-23 23:00 sruffell       Fixed in Version          => 2.3.0           
2009-09-23 23:00 sruffell       Resolution               reopened => fixed   
======================================================================