[asterisk-users] Fwd: Bad FCS error

Eric "ManxPower" Wieling
Thu, 13 Sep 2007 13:58:14 -0000

This error message means there was corrupted data received from the
card.  This can be caused by many things.  The T-1/E-1 could be having
errors, there could be a bad SmartJack (the telco box on your wall), it
can also be cause by lost or delayed interrupts.

As you can see below your T-1/E-1 card is sharing an IRQ with your
Ethernet card.  This is a Very Bad Thing.  Digium cards and drivers have
gotten much better at sharing interrupts, but I think it is still a bad
idea to have two devices that generate many interrupts on the same IRQ.
  Try moving the card to a different slot.

Jan Prunk wrote:
> ---------- Forwarded message ----------
> From: Jan Prunk <janprunk at gmail.com>
> Date: Sep 13, 2007 3:35 PM
> Subject: Bad FCS error
> To: asterisk-users at lists.digium.com
>
> Hello !
>
> I am getting the following error in asterisk logs:
>
> Sep 11 17:33:30 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on
> Primary D-channel of span 1
> Sep 11 21:45:08 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on
> Primary D-channel of span 1
> Sep 11 23:57:26 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on
> Primary D-channel of span 1
> Sep 12 01:59:01 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on
> Primary D-channel of span 1
> Sep 12 03:52:31 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on
> Primary D-channel of span 1
> Sep 12 04:32:41 NOTICE[2187] chan_zap.c: PRI got event: HDLC Abort (6) on
> Primary D-channel of span 1
>
> The result is that when someone phones, the call gets disrupted, and
> sometimes it breaks.
> I wonder if this was fixed in the latest releases of asterisk.
> I am using asterisk version 1.2.13 on Debian sarge system
> And I am using zaptel module (if its related) 1.2.11
>
> cat /proc/interrupts
>            CPU0       CPU1
>   0: 1327389665          0    IO-APIC-edge  timer
>   1:        240          0    IO-APIC-edge  i8042
>   9:          0          0   IO-APIC-level  acpi
> 169: 1361816047          0   IO-APIC-level  wcte11xp, eth0
> 177:     648682          0   IO-APIC-level  3ware Storage Controller
> 201:          0          0         PCI-MSI  pciehp
> 209:          0          0         PCI-MSI  pciehp
> NMI:          1          0
> LOC: 1327446761 1327446897
> ERR:          0
> MIS:          0
>