Oh, and reverting to 0.7.0 with no changes to dahdi/system.conf or chan_dahdi.conf brings the boxes back up. dmesg here gives:
dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.0.2 Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 4 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 5 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 6 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 7 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 8 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 9 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 10 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 11 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 12 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 13 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 14 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 15 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 16 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 17 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 18 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 19 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 20 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 21 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 22 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 23 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 24 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 25 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Not installed Port 3: Not installed Port 4: Not installed VPM100: Not Present Booting VPMADT032 VPMADT032: Present and operational (Firmware version 117) wctdm24xxp0: Missed interrupt. Increasing latency to 26 ms in order to compensate. Found a Wildcard TDM: Wildcard TDM410P (4 modules) wctdm24xxp0: Missed interrupt. Increasing latency to 27 ms in order to compensate. dahdi: Registered tone zone 4 (United Kingdom) wctdm24xxp0: Missed interrupt. Increasing latency to 28 ms in order to compensate. wctdm24xxp0: Missed interrupt. Increasing latency to 29 ms in order to compensate. wctdm24xxp0: Missed interrupt. Increasing latency to 30 ms in order to compensate. So it's evidently a DAHDI 2.2.1 issue. But what? Tom > -----Original Message----- > From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] > Sent: 07 April 2010 15:45 > To: 'AstLinux Users Mailing List' > Subject: RE: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > You are getting an explicit timing-related error, but I don't > seem to. For info, here are my DAHDI configs: > > ingrampbx ~ # cat /mnt/kd/dahdi/system.conf > fxsks=1-2 > loadzone=uk > defaultzone=uk > > ingrampbx ~ # cat /mnt/kd/asterisk/chan_dahdi.conf > > ; snipping a lot of content here... > > usecallerid=yes > hidecallerid=no > callwaiting=no > threewaycalling=no > transfer=yes > echocancel=yes > cidsignalling=v23 > cidstart=polarity > callerid=asreceived > restrictcid=no > sendcalleridafter=2 > > rxgain=2.0 > txgain=2.0 > > context=zap1 > signalling=fxs_ks > group=1 > channel => 1 > context=zap2 > channel => 2 > > Anyone see anything wrong with this? dmesg gives this: > > dahdi: Telephony Interface Registered on major 196 > dahdi: Version: 2.2.1 > Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Not > installed Port 3: Not installed Port 4: Not installed > VPM100: Not Present > wctdm24xxp 0000:00:0e.0: Booting VPMADT032 > VPMADT032: Present and operational (Firmware version 120) > Found a Wildcard TDM: Wildcard TDM410P (4 modules) > dahdi: Registered tone zone 4 (United Kingdom) wctdm24xxp > 0000:00:0e.0: Missed interrupt. Increasing latency to 9 ms in > order to compensate. > wctdm24xxp 0000:00:0e.0: Host failed to service card > interrupt within 128 ms which is a hardunderun. > wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency > to 15 ms in order to compensate. > wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency > to 21 ms in order to compensate. > > This is similar to what I have seen in a working system, but > I don't remember reference to "hardunderun". > > Any ideas? > > Thanks > > Tom > > > > -----Original Message----- > > From: Michael Keuter [mailto:li...@mksolutions.info] > > Sent: 07 April 2010 14:28 > > To: tom.chad...@nnpa.org.uk; AstLinux Users Mailing List > > Subject: Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > > > >Hello all > > > > > >A major issue with 0.7.1 seems to have transpired. I > > upgraded six or so > > >boxes last week, two of which use DAHDI. Asterisk seems to > > have failed > > >to run. When I try to start it from the command line, I get: > > > > > >[Apr 7 09:40:18] ERROR[2705]: asterisk.c:3099 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 Zaptel services, you must correctly > > configure DAHDI. > > > > > >DAHDI was working on these boxes in 0.7.0, and Zaptel on > them in 0.6. > > > > > >Can anyone help? > > > > > >Tom > > > > I don't know if it's related, but I tested the vzaphfc driver > > (community driver for single port HFC ISDN cards) with DAHDI > > 2.2.1 in trunk with Asterisk 1.6 .2.6 recently and got similar > > messages: > > > > ---------------------------- > > Apr 7 15:17:31 net4801 local0.err asterisk[1497]: ERROR[1491]: > > res_timing_dahdi.c:172 in dahdi_test_timer: 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 > > suppor > > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to > > 'userbase' (on reload) at line 23. > > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to > > 'vmsecret' (on reload) at line 31. > > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes > to 'hassip' > > (on reload) at line 35. > > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes > to 'hasiax' > > (on reload) at line 39. > > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to > > 'hasmanager' (on reload) at line 47. > > Apr 7 15:17:31 net4801 local0.err asterisk[1497]: ERROR[1491]: > > codec_dahdi.c:620 in find_transcoders: Failed to open > > /dev/dahdi/transcode: No such file or directory Apr 7 > > 15:17:32 net4801 user.info kernel: vzaphfc: card 0: chan B1 > opened as > > ZTHFC1/0/1. > > Apr 7 15:17:32 net4801 user.info kernel: vzaphfc: card 0: > > chan B2 opened as ZTHFC1/0/2. > > Apr 7 15:17:32 net4801 user.info kernel: vzaphfc: card 0: > > chan D opened as ZTHFC1/0/3. > > Apr 7 15:17:32 net4801 user.warn kernel: vzaphfc: card 0: > > chan D: TX FIFO has become empty > > ------------------------------- > > > > But in my case it could also be a configuration issue, I never used > > DAHDI or that driver before with Astlinux. > > What I found out was, that "dahdi_transcode" is also needed and > > "dahdi_dummy" must be loaded after all the drivers. > > > > Michael > > > > http://www.mksolutions.info > > > > -------------------------------------------------------------- > > ---------------- > > Download Intel® Parallel Studio Eval Try the new > software tools > > for yourself. Speed compiling, find bugs proactively, and fine-tune > > applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Astlinux-users mailing list > > Astlinux-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to > > pay...@krisk.org. > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
