[asterisk-bugs] [DAHDI-linux 0013967]: kernel oopses with similar stack traces

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13967 
====================================================================== 
Reported By:                bergolth
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   13967
Category:                   wct4xxp
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2008-11-25 03:48 CST
Last Modified:              2008-11-25 07:34 CST
====================================================================== 
Summary:                    kernel oopses with similar stack traces
Description: 
My asterisk-box running asterisk-1.4.22 and fedora kernel
2.6.26.5-28.fc8PAE and 2.6.26.6-49.fc8PAE constantly crashes after
several days, leaving the same stack-trace every time. (Attached.)
Zaptel versions 1.4.11 and 1.4.12 also show the same problem.

The crashes appear after a few days, I couldn't trigger them with
phone calls.

kernel-PAE-2.6.24.4-64.fc8 together with a zaptel SVN version from
2008-08-05 worked fine. (An earlier version had stack overflow
problems with this kernel.)

Unfortunately the stack traces seem to be subsequent errors following
a memory corruption so I suppose the stack traces won't be very
informative.

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

---------------------------------------------------------------------- 
 (0095480) blitzrage (administrator) - 2008-11-25 07:34
 http://bugs.digium.com/view.php?id=13967#c95480 
---------------------------------------------------------------------- 
I have a feeling that you may need to provide some valgrind output if it is
indeed memory corruption.

I've assigned this issue to sruffell for now, but please reassign if this
is not correct. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-25 07:34 blitzrage      Note Added: 0095480                          
======================================================================