[asterisk-users] Zaptel/DAHDI error's on PRI

[Sascha Ferley]

Hi

I've been running into a weird issue, which its hard to get any information
on. We successfully setup a R710 system with Asterisk 1.4.22 / libpri 1.4.7,
utilizing a Digium TE121B Pci express card. However we are having some
stability issues and can't seem to trace it down to if it is a card/system
issue or our PRI vendor having a dirty line. I know some will say it is a
old version of asterisk, however this is the one that has been deployed as a
standard everywhere and our vendor supplied custom apps against it (not
relevant to PRI however).
Basically every once in a while ( arbitrarily throughout the day), the PRI
drops and the only way to get it back up is to reboot the system.
Looking at the dmesg logs we get:

wcte12xp0: Missed interrupt. Increasing latency to 4 ms in order to
compensate.
HDLC Receiver overrun on channel WCT1/0/24 (master=WCT1/0/24)

After searching some state that this could be a IRQ issue or a hardware card
issue, however it seems strange as everyone states that it is just a blib
and resets itself, not requiring a full hard reset of the entire system.
Also the card is on its own IRQ as in:

[trixbox proc]# more interrupts
           CPU0       CPU1       CPU2       CPU3       CPU4       CPU5
CPU6       CPU7    
  0:        603          0          0    1471809          0          0
0          0    IO-APIC-edge  timer
  1:          0          0          0          3          0          0
0          0    IO-APIC-edge  i8042
  8:          0          0          0          0          0          0
3          0    IO-APIC-edge  rtc
  9:          0          0          0          0          0          0
0          0   IO-APIC-level  acpi
 12:          4          0          0          0          0          0
0          0    IO-APIC-edge  i8042
 50:          0          0          0         21          0          0
0          0   IO-APIC-level  ehci_hcd:usb1
 58:          0          0          0         50          0          0
0          0   IO-APIC-level  ehci_hcd:usb2, uhci_hcd:usb5
 66:          0          0          0          0          0          0
0          0   IO-APIC-level  uhci_hcd:usb3
 74:          0          0          0          0          0          0
0          0   IO-APIC-level  uhci_hcd:usb4
 82:          0          0          0          0          0          0
0          0   IO-APIC-level  uhci_hcd:usb6
 90:          0          0          0          0          0       8257
0          0   IO-APIC-level  ioc0
 98:          0          0          0          0          0          0
15072          0   IO-APIC-level  ata_piix
138:    1415485          0          0          0          0          0
0          0   IO-APIC-level  wcte12xp0
146:       2535          0          0          0          0          0
0          0       PCI-MSI-X  eth0
154:        131          0          0          0          0          0
0          0       PCI-MSI-X  eth0
162:        325          0          0          0          0          0
0          0       PCI-MSI-X  eth0
170:       1036          0          0          0          0          0
0          0       PCI-MSI-X  eth0
178:        108          0          0          0          0          0
0          0       PCI-MSI-X  eth0
186:        814          0          0          0          0          0
0          0       PCI-MSI-X  eth0
194:        134          0          0          0          0          0
0          0       PCI-MSI-X  eth0
NMI:          0          0          0          0          0          0
0          0 
LOC:    1471806    1471814    1471814    1471813    1471812    1471810
1471809    1471808 

Thus we the next time we had the issue we ran a pri intense debug and
received this:

trixbox*CLI> pri intense debug span 1
Enabled EXTENSIVE debugging on span 1
[Feb 15 00:49:07] Sending Set Asynchronous Balanced Mode Extended
[Feb 15 00:49:07] > [ 00 01 7f ]
[Feb 15 00:49:07] > Unnumbered frame:
[Feb 15 00:49:07] > SAPI: 00  C/R: 0 EA: 0 >  TEI: 000        EA: 1
[Feb 15 00:49:07] >   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous
balanced mode extended) ] > 0 bytes of data
[Feb 15 00:49:08] Sending Set Asynchronous Balanced Mode Extended
[Feb 15 00:49:08] > [ 00 01 7f ]
[Feb 15 00:49:08] > Unnumbered frame:
[Feb 15 00:49:08] > SAPI: 00  C/R: 0 EA: 0>  TEI: 000        EA: 1
[Feb 15 00:49:08] >   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous
balanced mode extended) ] > 0 bytes of data
[Feb 15 00:49:09] Sending Set Asynchronous Balanced Mode Extended
[Feb 15 00:49:09] > [ 00 01 7f ]
[Feb 15 00:49:09] > Unnumbered frame:
[Feb 15 00:49:09] > SAPI: 00  C/R: 0 EA: 0 >  TEI: 000        EA: 1
[Feb 15 00:49:09] >   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous
balanced mode extended) ] > 0 bytes of data
[Feb 15 00:49:10] Sending Set Asynchronous Balanced Mode Extended
[Feb 15 00:49:10] > [ 00 01 7f ]
[Feb 15 00:49:10] > Unnumbered frame:
[Feb 15 00:49:10] > SAPI: 00  C/R: 0 EA: 0 >  TEI: 000        EA: 1
[Feb 15 00:49:10] >   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous
balanced mode extended) ] > 0 bytes of data
[Feb 15 00:49:11] Sending Set Asynchronous Balanced Mode Extended

This repeats endless.

The version of everything:
Asterisk 1.4.22-4 
libpri version: 1.4.7

Does anyone have any suggestions?
Please let me know
Thanks


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100215/b73f63b1/attachment.htm