thr3ads.net - asterisk users - [asterisk-users] wct4xxp Interrupts not detected with dahdi 2.6, but working ok with 2.5 [Mar 2012]

If this information is useful, please help other people find it:
Share via:

Vahan Yerkanian

2012-Mar-16 19:13 UTC

[asterisk-users] 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 <sruffell at
digium.com>


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

Shaun Ruffell

2012-Mar-22 19:25 UTC

head link

[asterisk-users] wct4xxp Interrupts not detected with dahdi 2.6, but working ok with 2.5

On Fri, Mar 16, 2012 at 11:13:14PM +0400, Vahan Yerkanian
wrote:> 
> 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?
Vahan,

Just closing out this public thread. dahdi-linux 2.6.1 will contain
what fixed this issue on your machine. I committed onto both trunk
[1] and onto the 2.6 branch [2].

[1] http://svnview.digium.com/svn/dahdi?view=revision&revision=10559
[2] http://svnview.digium.com/svn/dahdi?view=revision&revision=10565

Thanks again for your help,
SHaun

-- 
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org

asterisk users - Mar 2012 - wct4xxp Interrupts not detected with dahdi 2.6, but working ok with 2.5

[asterisk-users] wct4xxp Interrupts not detected with dahdi 2.6, but working ok with 2.5

[asterisk-users] wct4xxp Interrupts not detected with dahdi 2.6, but working ok with 2.5