[asterisk-users] HDLC Receiver overrun on Wildcard TE410P

Łukasz Krzyżak lukasz.krzyzak at nao-team.eu
Wed May 5 07:05:34 CDT 2010


and it happened again, I've attached kernel logs from dahdi restart on paste-bin

http://pastebin.com/drg3WD20

to fix this problem, I have to:

stop dahdi and asterisk - /etc/init.d/dahdi stop
remove all dahdi modules - rmmod wct4xxp, dahdi_echocan_mg2, dahdi

load modules - modprobe dahdi, modprobe wct4xxp

start asterisk

after that it works like a charm till next time...

any idea what's happening and what else to check ?

W dniu 30 kwietnia 2010 13:20 użytkownik Łukasz Krzyżak
<lukasz.krzyzak at nao-team.eu> napisał:
> Hello
> I've got small PBX (30 simultaneous connections) based on asterisk
> (1.6.2.6), which uses Stargate 2N ISDN to GSM gate.
>
> It runs ok for day or two, but then I get:
>
> dahdi: HDLC Receiver overrun on channel TE4/0/1/16 (master=TE4/0/1/16)
>
> in my kernel logs, in asterisk i get:
>
> pri show spans
> PRI span 1/0: Provisioned, Down, Active
> PRI span 3/0: Provisioned, In Alarm, Down, Active
>
> (span 3 is not connected to gateway for now)
>
> and I can't make any calls.
>
> My dahdi-channels.conf:
>
> ; Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER)
> group=0,11
> context=from-pstn
> switchtype = euroisdn
> signalling = pri_net
> channel => 1-15,17-31
> context = default
> group = 63
>
> /etc/dahdi/system.conf:
>
> # Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER)
> span=1,0,0,ccs,hdb3,crc4
> # termtype: te
> bchan=1-15,17-31
> dchan=16
> echocanceller=mg2,1-15,17-31
>
> /proc/interrupts:
>
>           CPU0       CPU1       CPU2       CPU3
>   0:        462        313        432          0   IO-APIC-edge      timer
>   1:          3          5          5          3   IO-APIC-edge      i8042
>   8:         32         31         32         34   IO-APIC-edge      rtc0
>   9:          0          0          0          0   IO-APIC-fasteoi   acpi
>  12:         28         27         29         30   IO-APIC-edge      i8042
>  14:          3          3          1          0   IO-APIC-edge      ata_piix
>  15:          0          0          0          0   IO-APIC-edge      ata_piix
>  16:          0          0          0          0   IO-APIC-fasteoi
> uhci_hcd:usb2, uhci_hcd:usb5
>  18:          0          0          0          0   IO-APIC-fasteoi
> uhci_hcd:usb4
>  19:          0          0          0          0   IO-APIC-fasteoi
> uhci_hcd:usb3
>  23:        351        350        200        188   IO-APIC-fasteoi
> ehci_hcd:usb1
>  25:          0          0          0          1   IO-APIC-fasteoi
>  26:       2151       2083  104408008       1985   IO-APIC-fasteoi   eth1
>  51:    1089962    1089895       2940       2910   IO-APIC-fasteoi   cciss0
>  78:     485362     485513     485473  320148527   IO-APIC-fasteoi   wct4xxp
>  NMI:          0          0          0          0   Non-maskable interrupts
>  LOC:   30245307   31461472   20982472   23492748   Local timer interrupts
>  SPU:          0          0          0          0   Spurious interrupts
>  CNT:          0          0          0          0   Performance
> counter interrupts
>  PND:          0          0          0          0   Performance pending work
>  RES:     436674     440302    2195268    1451020   Rescheduling interrupts
>  CAL:        169        265        203        251   Function call interrupts
>  TLB:      43920      44257      50177      52884   TLB shootdowns
>  TRM:          0          0          0          0   Thermal event interrupts
>  THR:          0          0          0          0   Threshold APIC interrupts
>  MCE:          0          0          0          0   Machine check exceptions
>  MCP:       1073       1073       1073       1073   Machine check polls
>  ERR:          3
>  MIS:          0
>
> I manually set irq affinity - eth1 to CPU2, digium card to CPU3, rest
> of common interrupts to CPU0 and CPU1
>
> PBX runs on HP ProLiant DL380 G5 server, OS is Gentoo Linux with 2.6.31 kernel.
>
> Other software versions:
> asterisk - 1.6.2.6
> libpri - 1.4.10.2
> dahdi - 2.2.0.2
>
> any idea what could be the problem / what should I check to diagnose it ?
>
> Luke
>



More information about the asterisk-users mailing list