[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-07 15:04 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 


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

---------------------------------------------------------------------- 
 (0121586) kerframil (reporter) - 2010-05-07 15:04
 https://issues.asterisk.org/view.php?id=17289#c121586 
---------------------------------------------------------------------- 
I'm experiencing this problem too. I've applied commits 8560, 8575 (as
applicable to "drivers/dahdi/voicebus/GpakCust.c") and 8576 to a stock
dahdi-2.3.0 base for testing and will report back early next week.

In the meantime, I just wanted to point out something that I noticed in
the kernel ring buffer after rebooting:

[    9.248084] wcte12xp 0000:03:02.0: PCI INT A -> GSI 35 (level, low) ->
IRQ 35
[   10.537270] wcte12xp 0000:03:02.0: Setting up global serial parameters
for E1
[   10.537760] wcte12xp 0000:03:02.0: Found a Wildcard TE122
[   25.379214] wcte12xp 0000:03:02.0: Missed interrupt. Increasing latency
to 9 ms in order to compensate.
[   25.555003] wcte12xp 0000:03:02.0: Missed interrupt. Increasing latency
to 15 ms in order to compensate.
[   25.693790] wcte12xp 0000:03:02.0: Missed interrupt. Increasing latency
to 21 ms in order to compensate.
[   25.696741] wcte12xp 0000:03:02.0: Host failed to service card
interrupt within 128 ms which is a hardunderun.
[   25.733952] wcte12xp 0000:03:02.0: Host failed to service card
interrupt within 128 ms which is a hardunderun.
[   32.206230] wcte12xp 0000:03:02.0: Booting VPMADT032
[   32.561291] wcte12xp 0000:03:02.0: VPM present and operational
(Firmware version 120)
[   55.362964] wcte12xp 0000:03:02.0: Span configured for CCS/HDB3/CRC4

The messages with the timestamps 25.696741 and 25.733952 complain of
failing to service a card interrupt - a message which I have never seen
before. By contrast, here's an excerpt from the prior boot:

[    9.221907] wcte12xp 0000:03:02.0: PCI INT A -> GSI 35 (level, low) ->
IRQ 35
[   10.526093] wcte12xp 0000:03:02.0: Setting up global serial parameters
for E1
[   10.528207] wcte12xp 0000:03:02.0: Found a Wildcard TE122
[   25.154052] wcte12xp 0000:03:02.0: Missed interrupt. Increasing latency
to 9 ms in order to compensate.
[   25.314814] wcte12xp 0000:03:02.0: Missed interrupt. Increasing latency
to 15 ms in order to compensate.
[   25.430977] wcte12xp 0000:03:02.0: Missed interrupt. Increasing latency
to 21 ms in order to compensate.
[   31.926671] wcte12xp 0000:03:02.0: Booting VPMADT032
[   32.281685] wcte12xp 0000:03:02.0: VPM present and operational
(Firmware version 120)

The only change made was the addition of the aforementioned three patches.
I don't know if this is significant, but figured that I should mention it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-07 15:04 kerframil      Note Added: 0121586                          
======================================================================