[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-10 14:32 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 


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

---------------------------------------------------------------------- 
 (0121679) kerframil (reporter) - 2010-05-10 14:32
 https://issues.asterisk.org/view.php?id=17289#c121679 
---------------------------------------------------------------------- 
One working day elapsed and over 449 calls outbound alone, notching up
almost 12 hours of call time. At this point, I would have expected the
"VPMADT032 is non-responsive" complaint to have arisen up to maybe a dozen
times but it has not. Tentatively, I'd say that the aformentioned patches
seem to have addressed the bug. The only thing that seems odd compared to
the unpatched instance is the hardunderrun warning that occurs during
initialisation, as mentioned in the previous comment. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-10 14:32 kerframil      Note Added: 0121679                          
======================================================================