[asterisk-users] Possible Dahdi compile problem

Doug dsc3507 at yahoo.com
Sat Apr 12 10:57:36 CDT 2014


Sorry the extra post was a mistake.

Dahdi is required by Asterisk for pseudo and timing purposes in my application even though no modules are installed. 


It is not a hardware problem but rather I suspect something in the kernel<>dahdi or kernel<>asterisk interface as they are compiled agains one another. The fact that it works for awhile then crashes is kind of strange. I was just wondering if a kernel compile mismatch would show up immediately or do something like this? 

 
Doug


On Friday, April 11, 2014 8:28 PM, John Novack <jnovack at stromberg-carlson.org> wrote:
 
Possible hardware issue?
>If you are not using DAHDI, why are you installing it?
>
>
>Did you intend to add some information to this post that was made
      earlier today?
>
>John Novack
>
> 
>Doug wrote:
>
>
>>
>>I am having problems with system crashes in a dahdi/asterisk compile.  The is on a Beaglebone Black running Debian 3.8.13 kernel.
>>>
>>>Dahdi is patched and asterisk is also custom
                          so this must be compiled from source. I
                          believe I have the proper header and source
                          files for the running kernel. Both dahdi and
                          asterisk compile and install. When run
                          asterisk runs for anywhere from 10 minutes to
                          a half hour or more and crashes. This is a
                          complete system crash requiring a reboot.
                          There are no indications of why it crashed. No
                          messages and analyzing memory and other
                          parameters before the crash show nothing
                          unusual. 
>>>
>>> This same package arrangement works fine on
                          several other platforms so I discount a
                          problem in the code.
>>>
>>>On thing that may give a clue is that when
                          dahdi is installed it creates and puts its
                          modules in  /lib/modules/3.8.13   The system
                          modules are in /lib/modules/3.8.13-bone43   -
                          the bone43 is the patched 3.8.13 kernel for
                          the Beagle Black. The patches are installed in
                          the sources but dahdi insists on putting the
                          modules in 3.8.13  and they are not found
                          there.
>>>
>>>I have to mv  /lib/modules/3.8.13/dahdi  to
                          /lib/modules/3.8.13-bone43  and then do a 
                          depmod -a 3.8.13-bone43
>>>
>>>Then dahdi installs. I do not use any dahdi
                          modules so no modules install.
>>>
>>>In asterisk I get the following -
>>>
>>>beaglebone*CLI> dahdi show status
>>>Description                             
                          Alarms     IRQ        bpviol     CRC4  
>>>
>>>beaglebone*CLI> dahdi show channels
>>>   Chan Extension  Context         Language  
                          MOH Interpret
>>> pseudo            default                   
                          default
>>>
>>>
>>>If dahdi installs and at least appears to work
                          with asterisk does that mean that it is
                          compiled correctly? I am trying to figure out
                          what might be causing this problem.
>>>
>>> 
>>>Doug
>>>WA3DSP
>>>
>>>
>>>
>>>
>>
>>
>
>--  Dog is my Co-pilot
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140412/b6903004/attachment.html>


More information about the asterisk-users mailing list