[asterisk-bugs] [DAHDI-linux 0018059]: Kernel NMI Error (dahdi)

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18059 
====================================================================== 
Reported By:                latysheff
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   18059
Category:                   wctdm
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
JIRA:                        
Reviewboard Link:            
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-09-27 01:05 CDT
Last Modified:              2010-09-27 13:02 CDT
====================================================================== 
Summary:                    Kernel NMI Error (dahdi)
Description: 
Getting this kernel error during boot up, then server hangs and reboots
(again and again):
"Uhhuh. NMI received for unknown reason 35 on CPU 0"

Error repeats on 2 different servers (Centos 5) with 2 different tel cards
(Wildcard TE210P and TE410P). Machine with newer hardware freezes sparsely,
while older (with TE210P) - immediately after boot.

What I was able to find out is that version 2.2.0.2 of dahdi doesn't
produce this error. All later versions starting from 2.2.1 onwards do. No
matter, compiled or installed from digium .rpms
Tried different kernels too.
====================================================================== 

---------------------------------------------------------------------- 
 (0127431) sruffell (administrator) - 2010-09-27 13:02
 https://issues.asterisk.org/view.php?id=18059#c127431 
---------------------------------------------------------------------- 
latysheff:  Thanks for opening the bug report.  I looked through the code
differences between 2.2.0.2 and 2.2.1 in the wct4xxp driver and nothing
stuck out at me.  The best course of action now is to open a case with
Digium technical support and they can help you collect any additional
information and triage this. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-27 13:02 sruffell       Note Added: 0127431                          
2010-09-27 13:02 sruffell       Status                   new => resolved     
2010-09-27 13:02 sruffell       Resolution               open => suspended   
2010-09-27 13:02 sruffell       Assigned To               => sruffell        
2010-09-27 13:02 sruffell       Status                   resolved => closed  
======================================================================