[asterisk-bugs] [DAHDI-linux 0013930]: dahdi_dummy does not tick on some systems

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13930 
====================================================================== 
Reported By:                tzafrir
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   13930
Category:                   dahdi_dummy
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2008-11-19 08:34 CST
Last Modified:              2008-11-27 18:20 CST
====================================================================== 
Summary:                    dahdi_dummy does not tick on some systems
Description: 
On some systems dahdi_dummy (or ztdummy, in the case of Zaptel) fails to
"tick" DAHDI and hence DAHDI does not provide a working timing source.

Indications that DAHDI (Zaptel) provides no timing source:

1. dahdi_test (zttest) does not give an error on startup, but hangs.
2. Asterisk >= 1.4.20 fails to start, and gives the ugly "no timing
source" error message:

ERROR[10981]: asterisk.c:3036 main: Asterisk has detected a problem
with your DAHDI configuration and will shutdown for your protection.
You have options:
        1. You only have to compile DAHDI support into Asterisk if you
need it.  One option is to recompile without DAHDI support.
        2. You only have to load DAHDI drivers if you want to take
advantage of DAHDI services.  One option is to unload DAHDI modules if
you don't need them.
        3. If you need DAHDI services, you must correctly configure
DAHDI.

An indication that dahdi_dummy should be the timing source for dahdi could
be:

  lsmod | grep ^dahdi
  dahdi                 231888  1 dahdi_dummy

Or to see that /proc/dahdi/1 is dahdi_dummy and is listed as "MASTER".


I have seen various suggestions on how to solve this. None seems to be a
silver bullet. 
====================================================================== 

---------------------------------------------------------------------- 
 (0095586) nullpointer (reporter) - 2008-11-27 18:20
 http://bugs.digium.com/view.php?id=13930#c95586 
---------------------------------------------------------------------- 
dont know if this will help, but i have the same issue (dahdi doesnt seem
to "tick"); i will try and offer what few details i have.

asterisk 1.6.0.1
dahdi-linux 2.0.0
dahdi-tools 2.0.0
libpri 1.4.7
spandsp 0.0.6

CentOS 5.2 on an IBM 326 server (64 bit dual proc 2 GHZ opteron, dual disk
in RAID1 config)

[root at localhost asterisk]# uname -a
Linux localhost.localdomain 2.6.18-92.1.18.el5
http://bugs.digium.com/view.php?id=1 SMP Wed Nov 12 09:19:49
EST 2008 x86_64 x86_64 x86_64 GNU/Linux

i have added these entries to /etc/modprobe.d/dahdi

options dahdi debug=1
options dahdi_dummy debug=2

doing "service dahdi start" and tailing /var/log/messages gives:

Nov 27 13:44:52 localhost kernel: dahdi: Telephony Interface Registered on
major 196
Nov 27 13:44:52 localhost kernel: dahdi: Version: 2.0.0
Nov 27 13:44:52 localhost kernel: dahdi: Registered Span 1
('DAHDI_DUMMY/1') with 0 channels
Nov 27 13:44:52 localhost kernel: dahdi: Span ('DAHDI_DUMMY/1') is new
master
Nov 27 13:44:52 localhost kernel: dahdi_dummy: RTC rate is 1024
Nov 27 13:44:52 localhost kernel: dahdi: Registered tone zone 0 (United
States / North America)

and no "tick" debug info - no more debug info from dahdi after hours pass


[root at localhost modprobe.d]# lsmod | grep ^dahdi
dahdi_dummy            38984  0 
dahdi                 231760  1 dahdi_dummy

[root at localhost modprobe.d]# cat  /proc/dahdi/1
Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: RTC) 1" (MASTER) 


both of these entries are as expected (i assume)

however, the following results in nothing being returned (i am a noob - is
this bad?)

strings /lib/modules/2.6.18-92.1.18.el5/dahdi/dahdi.ko | grep source

worth noting i have no telephony hardware installed, so i have followed
the advice on this bug: http://bugs.digium.com/view.php?id=13966

i commented out all the modules in /etc/dahdi/modules, and added 
noload => codec_dahdi.so

to /etc/asterisk/modules.conf

thanks for all you do - even tho i am a noob, i REALLY appreciate how
wonderful asterisk is! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-27 18:20 nullpointer    Note Added: 0095586                          
======================================================================