[asterisk-bugs] [Asterisk 0000676]: zaptel driver hard-locks kernel

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=676 
====================================================================== 
Reported By:                akohlsmith
Assigned To:                markster
====================================================================== 
Project:                    Asterisk
Issue ID:                   676
Category:                   Core/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           I did not set the version :( 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 not fixable
Fixed in Version:           
====================================================================== 
Date Submitted:             12-16-2003 12:14 CST
Last Modified:              06-07-2008 10:33 CDT
====================================================================== 
Summary:                    zaptel driver hard-locks kernel
Description: 
This is the second time this has happened in a week.  I have a Duron1300 in
an ECS L7VMM2 motherboard.  The only addon card in it is the T100P and it's
connected to a Carrier Access Channel Bank 1 (12FXS/12FXO).  

The *only* unusual thing I can say about this system is that I do run UML
on it for our intranet (the old intranet box died and we're slowly moving
services over, running it in user-mode linux was the quickest fix).

Anyway I get a kernel panic now and again and ksymoops points to zaptel. 
Both crashes have _identical_ call traces, although the processor registers
have been different.

When I reset the box and it boots up, my channel bank is in a very funky
state -- channels are either very choppy and jittery or they are all
unavailable (CB itself shows all idle, but * can't place any calls -- fast
busies) -- I power-cycle the CB1 and everything's normal again.

The call trace is as follows:
>>EIP; c0115c80 <__wake_up+20/60>   <=====

>>esi; c2158c50 <_end+1d7faec/1fc3aefc>
>>ebp; c88a7a90 <_end+84ce92c/1fc3aefc>
>>esp; c88a7a7c <_end+84ce918/1fc3aefc>

Trace; e00548d8 <[zaptel]process_timers+38/50>
Trace; e004fe2c <[zaptel]zt_receive+6c/f10>
Trace; e007d820 <[wct1xxp]t1xxp_receiveprep+190/360>
Trace; e007c942 <[wct1xxp]t1xxp_interrupt+1b2/1f0>
Trace; c013aa40 <__block_prepare_write+1d0/330>
Trace; c011a12d <qm_refs+13d/190>
Trace; c010a2a8 <do_IRQ+68/b0>
Trace; c010ca48 <call_do_IRQ+5/d>
Trace; c012c8c2 <do_generic_file_write+252/3e0>
Trace; c012cd53 <generic_file_write+103/120>
Trace; c01610b2 <ext3_file_write+22/c0>

Code;  c0115c80 <__wake_up+20/60>
00000000 <_EIP>:
Code;  c0115c80 <__wake_up+20/60>   <=====
   0:   8b 53 fc                  mov    0xfffffffc(%ebx),%edx   <=====
Code;  c0115c83 <__wake_up+23/60>
   3:   8b 02                     mov    (%edx),%eax
Code;  c0115c85 <__wake_up+25/60>
   5:   85 c7                     test   %eax,%edi
Code;  c0115c87 <__wake_up+27/60>
   7:   75 17                     jne    20 <_EIP+0x20>
Code;  c0115c89 <__wake_up+29/60>
   9:   8b 16                     mov    (%esi),%edx
Code;  c0115c8b <__wake_up+2b/60>
   b:   39 f3                     cmp    %esi,%ebx
Code;  c0115c8d <__wake_up+2d/60>
   d:   75 f1                     jne    0 <_EIP>
Code;  c0115c8f <__wake_up+2f/60>
   f:   ff 75 f0                  pushl  0xfffffff0(%ebp)
Code;  c0115c92 <__wake_up+32/60>
  12:   9d                        popf
Code;  c0115c93 <__wake_up+33/60>
  13:   8d 00                     lea    (%eax),%eax

<0>Kernel panic: Aiee, killing interrupt handler!

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

---------------------------------------------------------------------- 
 svnbot - 06-07-08 10:33  
---------------------------------------------------------------------- 
Repository: dahdi
Revision: 310

U   trunk/zconfig.h

------------------------------------------------------------------------
r310 | markster | 2008-06-07 10:33:46 -0500 (Sat, 07 Jun 2008) | 2 lines

Warn of AMD incompatibility with MMX in zconfig.h (bug
http://bugs.digium.com/view.php?id=676)

------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=310 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-07-08 10:33  svnbot         Checkin                                      
06-07-08 10:33  svnbot         Note Added: 0087934                          
======================================================================