[asterisk-bugs] [DAHDI-linux 0017289]: VPMADT032 is crashing after upgarde to 2.3.0

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17289 
====================================================================== 
Reported By:                isaacgal
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   17289
Category:                   wcte12xp
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2010-05-05 03:09 CDT
Last Modified:              2010-05-17 10:05 CDT
====================================================================== 
Summary:                    VPMADT032 is crashing after upgarde to 2.3.0
Description: 
just finished upgrading from 2.1.04 to 2.3.0 and calls strated to drop from
time to time. 

I noticed the following in the console log:

wcte12xp 0000:02:08.0: VPMADT032 is reenabled.
wcte12xp 0000:02:08.0: VPMADT032 is non-responsive.  Resetting.
wcte12xp 0000:02:08.0: VPM present and operational (Firmware version 120)
wcte12xp 0000:02:08.0: Error pinging DSP (2)
wcte12xp 0000:02:08.0: Failed to configure the ports.  Retrying.
wcte12xp 0000:02:08.0: VPM present and operational (Firmware version 120)
wcte12xp 0000:02:08.0: VPMADT032 is reenabled.
wcte12xp 0000:02:08.0: VPMADT032 is non-responsive.  Resetting.
wcte12xp 0000:02:08.0: VPM present and operational (Firmware version 120)
wcte12xp 0000:02:08.0: VPMADT032 is reenabled.
wcte12xp 0000:02:08.0: VPMADT032 is non-responsive.  Resetting.
wcte12xp 0000:02:08.0: VPM present and operational (Firmware version 120)
wcte12xp 0000:02:08.0: VPMADT032 is reenabled.
wcte12xp 0000:02:08.0: VPMADT032 is non-responsive.  Resetting.
wcte12xp 0000:02:08.0: VPM present and operational (Firmware version 120)
wcte12xp 0000:02:08.0: VPMADT032 is reenabled.
wcte12xp 0000:02:08.0: VPMADT032 is non-responsive.  Resetting.
wcte12xp 0000:02:08.0: VPM present and operational (Firmware version 120)
wcte12xp 0000:02:08.0: VPMADT032 is reenabled.
wcte12xp 0000:02:08.0: VPMADT032 is non-responsive.  Resetting.
wcte12xp 0000:02:08.0: VPM present and operational (Firmware version 120)
wcte12xp 0000:02:08.0: VPMADT032 is reenabled.
wcte12xp 0000:02:08.0: VPMADT032 is non-responsive.  Resetting.

i guess there is a bug in the 2.3.0 and VPMADT032 that causes it because
going back to 2.2.0.2 and this issue doesnt happen anymore eventhough new
issues arrived with faxing and echo cancellation, but atleast calls are not
dropping anymore.

the VPMADT032 firmware is 120
asterisk 1.4.30 


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

---------------------------------------------------------------------- 
 (0121976) tomchadwin (reporter) - 2010-05-17 10:05
 https://issues.asterisk.org/view.php?id=17289#c121976 
---------------------------------------------------------------------- 
I have two 2.3.0 boxes. On one, I have:

dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.3.0
wctdm24xxp 0000:00:0e.0: Port 1: Installed -- AUTO FXO (FCC mode)
wctdm24xxp 0000:00:0e.0: Port 2: Not installed
wctdm24xxp 0000:00:0e.0: Port 3: Not installed
wctdm24xxp 0000:00:0e.0: Port 4: Not installed
wctdm24xxp 0000:00:0e.0: VPM100: Not Present
wctdm24xxp 0000:00:0e.0: Host failed to service card interrupt within 128
ms which is a hardunderun.
wctdm24xxp 0000:00:0e.0: Booting VPMADT032
wctdm24xxp 0000:00:0e.0: VPM present and operational (Firmware version
120)
wctdm24xxp 0000:00:0e.0: Found a Wildcard TDM: Wildcard TDM410P (0 digital
modules, 1 analog module)
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 5 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 11 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 17 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 23 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
dahdi: Registered tone zone 4 (United Kingdom)
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.

This seems similar to my previously working 2.2.0.2 (2.2.1 crashed
Asterisk in my set-up). The other box, however, has this:

dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.3.0
wctdm24xxp 0000:00:0e.0: Port 1: Installed -- AUTO FXO (FCC mode)
wctdm24xxp 0000:00:0e.0: Port 2: Installed -- AUTO FXO (FCC mode)
wctdm24xxp 0000:00:0e.0: Port 3: Not installed
wctdm24xxp 0000:00:0e.0: Port 4: Not installed
wctdm24xxp 0000:00:0e.0: VPM100: Not Present
wctdm24xxp 0000:00:0e.0: Host failed to service card interrupt within 128
ms which is a hardunderun.
wctdm24xxp 0000:00:0e.0: Booting VPMADT032
wctdm24xxp 0000:00:0e.0: VPMADT032 Failed! Unable to ping the DSP (2)!
wctdm24xxp 0000:00:0e.0: Found a Wildcard TDM: Wildcard TDM410P (0 digital
modules, 2 analog modules)
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 5 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: Host failed to service card interrupt within 128
ms which is a hardunderun.
dahdi_echocan_mg2: Registered echo canceler 'MG2'
wctdm24xxp 0000:00:0e.0: Host failed to service card interrupt within 128
ms which is a hardunderun.
dahdi: Registered tone zone 4 (United Kingdom)
eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 11 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 17 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: Missed interrupt. Increasing latency to 23 ms in
order to compensate.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.
wctdm24xxp 0000:00:0e.0: ERROR: Unable to service card within 25 ms and
unable to further increase latency.

The VPMADT032 fails to boot. Ignore the MG2 line - trying software e/c on
this box, as I now have terrible echo without the hw e/c.

Is this related? Or do I just have one duff VPMADT032? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-17 10:05 tomchadwin     Note Added: 0121976                          
======================================================================