| Summary: | DAHLIN-00214: Kernel NMI Error (dahdi) | ||
| Reporter: | Vladimir Latyshev (latysheff) | Labels: | |
| Date Opened: | 2010-09-27 01:05:53 | Date Closed: | 2010-09-27 13:02:08 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | wctdm |
| Versions: | 2.2.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| 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. ****** ADDITIONAL INFORMATION ****** Similar cases: https://issues.asterisk.org/view.php?id=6588 http://fonality.com/trixbox/devblog/dahdi-221-update (in the middle of the thread) This is my first bug report, so please help me, what additional info is needed. BTW not sure i've chosen correct Category for this issue :-) | ||
| Comments: | By: Shaun Ruffell (sruffell) 2010-09-27 13:02:08 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. | ||