[asterisk-bugs] [Zaptel 0011652]: zaptel and wct4xxp load problems

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=11652 
====================================================================== 
Reported By:                master
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   11652
Category:                   wct4xxp
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     closed
Zaptel Version:              1.2.22.1  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             12-28-2007 21:41 CST
Last Modified:              12-29-2007 04:38 CST
====================================================================== 
Summary:                    zaptel and wct4xxp load problems
Description: 
I have a TE405P working for 2 years, and I upgraded zaptel, libpri and
asterisk from 1.2.21 to the latest 1.2.22.1. The modules will not load and
I get this  in dmesg. 

lsmod gives
Module                  Size  Used by
wct4xxp               309861  1
zaptel                184996  5 wct4xxp

I cannot remove the modules with modprobe -f.

--------- dmesg ------------------
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.2.22
Zaptel Echo Canceller: KB1
Found TE4XXP at base address fdffe000, remapped to f8834000
TE4XXP version c01a0164, burst OFF, slip debug: OFF
FALC version: 00000005, Board ID: 00
Reg 0: 0x36d5b400
Reg 1: 0x36d5b000
Reg 2: 0xffffffff
Reg 3: 0x00000000
Reg 4: 0x00000000
Reg 5: 0x00000000
Reg 6: 0xc01a0164
Reg 7: 0x00001f00
Reg 8: 0x00000000
Reg 9: 0x00ff0000
Reg 10: 0x00000000
TE4XXP: Launching card: 0
TE4XXP: Setting up global serial parameters
zt_rbs: Don't know RBS signalling type 504063 on channel TE4/0/1/1
Unable to handle kernel NULL pointer dereference at virtual address
0000002c
printing eip:
f89653b6
*pde = 00000000
Oops: 0000 [http://bugs.digium.com/view.php?id=1]
SMP
Modules linked in: wct4xxp zaptel
CPU:    0
EIP:    0060:[<f89653b6>]    Not tainted VLI
EFLAGS: 00010086   (2.6.15-gentoo-r1)
EIP is at t4_echocan+0x16/0x490 [wct4xxp]
eax: f69003e8   ebx: f69003e8   ecx: f6900034   edx: ffffffed
esi: 00000000   edi: f8964500   ebp: 00000000   esp: f6dddd74
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 1893, threadinfo=f6ddc000 task=f70195b0)
Stack: 00000000 00000000 c011ee27 f8852aa4 f6dddd90 f8847f8f f8852aa4
0007b0ff
      f69003ec 00000000 f69003e8 00000000 f8964500 00000000 f8847179
f69003e8
      00000000 00000000 00000000 00000000 00000082 00000001 f69003e8
00000292
Call Trace:
[<c011ee27>] printk+0x17/0x20
[<f8847f8f>] zt_hangup+0xbf/0x240 [zaptel]
[<f8964500>] t4_dacs+0x0/0x200 [wct4xxp]
[<f8847179>] close_channel+0x2f9/0x320 [zaptel]
[<f88474ce>] zt_chan_reg+0xae/0xf0 [zaptel]
[<f884ce25>] zt_register+0xd5/0x2a0 [zaptel]
[<f8979798>] t4_launch+0x78/0x1d0 [wct4xxp]
[<f8979c0e>] t4_init_one+0x31e/0x520 [wct4xxp]
[<f8972760>] t4_interrupt_gen2+0x0/0x2b40 [wct4xxp]
[<c0232ad5>] __pci_device_probe+0x65/0x80
[<c0232b1f>] pci_device_probe+0x2f/0x60
[<c029cd5b>] driver_probe_device+0x3b/0xd0
[<c029ce70>] __driver_attach+0x0/0x50
[<c029ceb3>] __driver_attach+0x43/0x50
[<c029c28d>] bus_for_each_dev+0x5d/0x80
[<c029cee6>] driver_attach+0x26/0x30
[<c029ce70>] __driver_attach+0x0/0x50
[<c029c7e3>] bus_add_driver+0x83/0xf0
[<c0232de5>] __pci_register_driver+0x75/0xb0
[<f8831017>] t4_init+0x17/0x25 [wct4xxp]
[<c013c1d2>] sys_init_module+0x142/0x1f0
[<c01030bf>] sysenter_past_esp+0x54/0x75


====================================================================== 

---------------------------------------------------------------------- 
 mvanbaak - 12-29-07 04:38  
---------------------------------------------------------------------- 
There has been a lot of changes in the kernel for timers and schedulars.
That might be the problem.

Closing on reporters request 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-29-07 04:38  mvanbaak       Status                   new => closed       
12-29-07 04:38  mvanbaak       Note Added: 0076146                          
======================================================================