* You are viewing Posts Tagged ‘sync source’

Asterisk 10/1.6.1 and Dahdi/Libpri compatilities in BRI /PtmP

Hi,

After an upgrade, I discovered yesterday strange things I would like
to share here.

Basically, I’me comparing platforms:
The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk
1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3
and 2.5, I think).
The second one is a 2.6.32 (Debian Squeeze) platform, with Asterisk
10.5.1, Libpri 1.4.12, Dahdi 2.6.1.
Both are connected to telco BRI lines in TE/PtmP mode through a
Junghanns QuadBRI board (wcb4xxp driver).
Both handle incoming and outgoing calls correctly, as far as I can tell.

But on the second one, though working fine, Dahdi keeps showing alarm
messages such as:
[71765.784120] wcb4xxp 0000:01:0e.0: new card sync source: port 1
[71767.484151] wcb4xxp 0000:01:0e.0: new card sync source: port 1
[71771.184119] wcb4xxp 0000:01:0e.0: new card sync source: port 2
[71794.184164] wcb4xxp 0000:01:0e.0: new card sync source: port 1

and “pri show spans” mostly (but not always) report worrying status:
PRI span 1/0: Down, Active
PRI span 2/0: In Alarm, Down, Active

On the first box “pri show spans” constantly reports the line is up.

On thing to note is I had to forbid hfcmulti in modprobe.d in the
second box to comply with a warning from dahdi. Without that, I could
see this line in the output of lsmod:
mISDN-core

wct4xxp Interrupts not detected with dahdi 2.6, but working ok with 2.5

Hi,

I’ve tried upgrading one of my servers with yum update to the latest dahdi/asterisk, and found out that my 4th gen TE410P is failing the dahdi init with

Running dahdi_cfg: DAHDI startup failed: Input/output error

Rolling back to 2.5 restores the normal operation, and reading the dahdi 2.6 change log I think I’m hitting this bug fix with my mobo/card combo?

2011-12-14 19:02 +0000 [r10379-10380] Shaun Ruffell

With dahdi 2.6 I’m getting this:

#cat /proc/interrupts

209: 1 0 IO-APIC-level wct4xxp

No interrupts?!

#dmesg

kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 209
kernel: wct4xxp 0000:02:01.0: Firmware Version: c01a016c
kernel: wct4xxp 0000:02:01.0: FALC Framer Version: 2.1 or earlier
kernel: wct4xxp 0000:02:01.0: Found a Wildcard: Wildcard TE410P (4th Gen)
kernel: VPM450: echo cancellation for 128 channels
kernel: wct4xxp 0000:02:01.0: VPM450: hardware DTMF disabled.
kernel: wct4xxp 0000:02:01.0: VPM450: Present and operational servicing 4 span(s)

kernel: wct4xxp 0000:02:01.0: TE4XXP: Span 1 configured for CCS/HDB3/CRC4
kernel: wct4xxp 0000:02:01.0: RCLK source set to span 1
kernel: wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
kernel: wct4xxp 0000:02:01.0: TE4XXP: Span 2 configured for CCS/HDB3/CRC4
kernel: wct4xxp 0000:02:01.0: RCLK source set to span 1
kernel: wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
kernel: wct4xxp 0000:02:01.0: TE4XXP: Span 3 configured for CCS/HDB3/CRC4
kernel: wct4xxp 0000:02:01.0: RCLK source set to span 3
kernel: wct4xxp 0000:02:01.0: Recovered timing mode, RCLK set to span 3
kernel: wct4xxp 0000:02:01.0: SPAN 3: Primary Sync Source
kernel: wct4xxp 0000:02:01.0: Interrupts not detected.

With dahdi 2.5 everything is OK:

#cat /proc/interrupts

201: 9157 962863 IO-APIC-level wct4xxp

#dmesg
kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 201
kernel: wct4xxp 0000:02:01.0: Found TE4XXP at base address f2000000, remapped to f887c000
kernel: wct4xxp 0000:02:01.0: Firmware Version: c01a016c
kernel: wct4xxp 0000:02:01.0: Burst Mode: On
kernel: wct4xxp 0000:02:01.0: Octasic Optimizations: Enabled
kernel: wct4xxp 0000:02:01.0: FALC Framer Version: 2.1 or earlier
kernel: wct4xxp 0000:02:01.0: Board ID: 00
kernel: wct4xxp 0000:02:01.0: Reg 0: 0x37554400
kernel: wct4xxp 0000:02:01.0: Reg 1: 0x37554000
kernel: wct4xxp 0000:02:01.0: Reg 2: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 3: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 4: 0x00003101
kernel: wct4xxp 0000:02:01.0: Reg 5: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 6: 0xc01a016c
kernel: wct4xxp 0000:02:01.0: Reg 7: 0x00001f00
kernel: wct4xxp 0000:02:01.0: Reg 8: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 9: 0x00ff0031
kernel: wct4xxp 0000:02:01.0: Reg 10: 0x0000004a
kernel: wct4xxp 0000:02:01.0: Found a Wildcard: Wildcard TE410P (4th Gen)
[snip]
wct4xxp 0000:02:01.0: TE4XXP: Span 1 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010c, CIS = 0080
wct4xxp 0000:02:01.0: RCLK source set to span 1
wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
wct4xxp 0000:02:01.0: TE4XXP: Span 2 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010c, CIS = 0080
wct4xxp 0000:02:01.0: RCLK source set to span 1
wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
wct4xxp 0000:02:01.0: TE4XXP: Span 3 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010d, CIS = 0081
wct4xxp 0000:02:01.0: RCLK source set to span 3
wct4xxp 0000:02:01.0: Recovered timing mode, RCLK set to span 3
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: SPAN 3: Primary Sync Source
wct4xxp 0000:02:01.0: TE4XXP: Span 4 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000d, CIS = 0084
wct4xxp 0000:02:01.0: RCLK source set to span 3
wct4xxp 0000:02:01.0: Recovered timing mode, RCLK set to span 3
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 0088
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 008a
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 0085
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 008a
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000

Junghanns OctoBRI – Invalid sync priority

Hi,

Looking at dmesg, I can see :
[ 45.213205] wcb4xxp 0000:01:07.0: Span 5 has invalid sync priority (5),
removing from sync source list
[ 45.213205] wcb4xxp 0000:01:07.0: Span 6 has invalid sync priority (6),
removing from sync source list
[ 45.213205] wcb4xxp 0000:01:07.0: Span 7 has invalid sync priority (7),
removing from sync source list
[ 45.213205] wcb4xxp 0000:01:07.0: Span 8 has invalid sync priority (8),
removing from sync source list

My setup is :
Lenny
asterisk 1.6.1.18
dahdi svn rev 9503
libpri 1.4.10.2

#lspci -v -n

01:07.0 0204: 1397:16b8 (rev 01)
Subsystem: 1397:b552
Flags: medium devsel, IRQ 17
I/O ports at 3400 [size=8]
Memory at d0110000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Kernel driver in use: wcb4xxp
Kernel modules: wcb4xxp

Though this doesn’t seem cause much trouble, is this a bug ?

Regards