[Home]

Summary:DAHLIN-00038: [patch] oops at loading tor2
Reporter:heyuqi (heyuqi)Labels:
Date Opened:2008-09-16 05:59:24Date Closed:2008-12-01 10:25:18.000-0600
Priority:BlockerRegression?No
Status:Closed/CompleteComponents:Utilities/NewFeature
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) tor2_dahdi_2.diff
( 1) tor2_dahdi.diff
Description:Several users report issues with loading the tor2 module.

BUG: unable to handle kernel NULL pointer dereference at 00000000
IP: [<e08e3de6>] :tor2:tor2_probe+0x4b4/0x962

...

Call Trace:
[<c017ca5d>] sysfs_create_link+0x85/0xc8
[<c01f5d61>] kobject_get+0xf/0x13
[<c01ff9fa>] pci_device_probe+0x36/0x57
[<c024faad>] driver_probe_device+0xb5/0x126
[<c024fbae>] __driver_attach+0x0/0x83
[<c024fbfe>] __driver_attach+0x50/0x83
[<c024f0ae>] bus_for_each_dev+0x34/0x56
[<c024f948>] driver_attach+0x11/0x13
[<c024fbae>] __driver_attach+0x0/0x83
[<c024f76d>] bus_add_driver+0x8a/0x1a5
[<c017c17d>] sysfs_addrm_finish+0x13/0x163
[<c024fd95>] driver_register+0x45/0x99
[<c01ffb90>] __pci_register_driver+0x2b/0x57
[<e088c015>] tor2_init+0x15/0x26 [tor2]
[<c0130477>] sys_init_module+0x1414/0x1575
[<e089e201>] dahdi_lboname+0x0/0x14 [dahdi]
[<c01504af>] sys_read+0x3c/0x63
[<c01040aa>] sysenter_past_esp+0x5f/0x85

****** ADDITIONAL INFORMATION ******

Quoting one of the reports:

I have also experianced this on my system:
uname -a
Linux mplsmnlyds1a 2.6.25-gentoo-r8 #2 Sun Oct 5 18:53:21 CDT 2008 i686 AMD Sempron(tm) 3000+ AuthenticAMD GNU/Linux



dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.0.0
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 19
Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xdfffb000/0xdfffa800 irq 19
Xilinx Chip successfully loaded, configured and started!!
Tormenta 2 Quad T1/PRI Card
BUG: unable to handle kernel NULL pointer dereference at 00000000
IP: [<e08e3de6>] :tor2:tor2_probe+0x4b4/0x962
*pde = 00000000
Oops: 0002 [#1]
Modules linked in: tor2(+) dahdi
Comments:By: Tzafrir Cohen (tzafrir) 2008-09-17 09:20:41

what is the output of:

lsmod | grep dahdi
ls /dev/dahdi*
ls /sys/class/dahdi
By: heyuqi (heyuqi) 2008-09-17 21:30:42

[root@asterisk dev]# lsmod | grep dahdi   (nothing output)
[root@asterisk dev]# ls /dev/dahdi*
ls: /dev/dahdi*: No such file or directory
[root@asterisk dev]# ls /sys/class/dahdi
ls: /sys/class/dahdi: No such file or directory
By: John Bigelow (jbigelow) 2008-09-20 02:10:12

It doesn't look like you have any dahdi drivers loaded.
By: heyuqi (heyuqi) 2008-09-22 03:50:23

I check it again,that dahdi drivers was not loaded,then I install dahdi-linux again,and reboot system.

Unfortunately,I found info below and system cannot boot:

EIP:[<f89ef008>] tor2_probe+0x553/0xalf [tor2] ss:ESP0068:f7f94e00
<0>Kernel panic - not syncing:Fatal exception
By: Tzafrir Cohen (tzafrir) 2008-09-22 04:06:51

Do you have such a card? Or any other zaptel/dahdi hardware?
By: heyuqi (heyuqi) 2008-09-22 04:09:20

Yes,I have Atcom 4port e1 card,when I used it with zaptel,everthing is ok.Does there have some conflict?


By: Shane Young (shanermn) 2008-10-15 06:56:11

I have also experianced this on my system:
uname -a
Linux mplsmnlyds1a 2.6.25-gentoo-r8 #2 Sun Oct 5 18:53:21 CDT 2008 i686 AMD Sempron(tm) 3000+ AuthenticAMD GNU/Linux



dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.0.0
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 19
Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xdfffb000/0xdfffa800 irq 19
Xilinx Chip successfully loaded, configured and started!!
Tormenta 2 Quad T1/PRI Card
BUG: unable to handle kernel NULL pointer dereference at 00000000
IP: [<e08e3de6>] :tor2:tor2_probe+0x4b4/0x962
*pde = 00000000
Oops: 0002 [#1]
Modules linked in: tor2(+) dahdi

Pid: 4600, comm: modprobe Not tainted (2.6.25-gentoo-r8 #2)
EIP: 0060:[<e08e3de6>] EFLAGS: 00010286 CPU: 0
EIP is at tor2_probe+0x4b4/0x962 [tor2]
EAX: de20f000 EBX: 00000000 ECX: e08e3ddf EDX: de20f000
ESI: 00000000 EDI: ddab73c8 EBP: ddab6000 ESP: de397df8
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process modprobe (pid: 4600, ti=de396000 task=de204ac0 task.ti=de396000)
Stack: ddaad1b0 ddaad210 00000000 00000000 c017ca5d de92dc30 de415bb0 00000000
      c01f5d61 e08f68b0 e08f6880 de92cc00 de92cce0 c01ff9fa de92cc54 00000000
      e08f68b0 c024faad de92cc54 de85d200 e08f68b0 c024fbae c024fbfe 00000000
Call Trace:
[<c017ca5d>] sysfs_create_link+0x85/0xc8
[<c01f5d61>] kobject_get+0xf/0x13
[<c01ff9fa>] pci_device_probe+0x36/0x57
[<c024faad>] driver_probe_device+0xb5/0x126
[<c024fbae>] __driver_attach+0x0/0x83
[<c024fbfe>] __driver_attach+0x50/0x83
[<c024f0ae>] bus_for_each_dev+0x34/0x56
[<c024f948>] driver_attach+0x11/0x13
[<c024fbae>] __driver_attach+0x0/0x83
[<c024f76d>] bus_add_driver+0x8a/0x1a5
[<c017c17d>] sysfs_addrm_finish+0x13/0x163
[<c024fd95>] driver_register+0x45/0x99
[<c01ffb90>] __pci_register_driver+0x2b/0x57
[<e088c015>] tor2_init+0x15/0x26 [tor2]
[<c0130477>] sys_init_module+0x1414/0x1575
[<e089e201>] dahdi_lboname+0x0/0x14 [dahdi]
[<c01504af>] sys_read+0x3c/0x63
[<c01040aa>] sysenter_past_esp+0x5f/0x85
=======================
Code: 00 00 00 00 eb 47 8b 54 24 0c b8 60 f0 4f c0 8b 74 24 1c 8b 9c 95 44 07 00 00 ba d0 00 00 00 e8 03 96 86 df c1 e6 02 01 f3 85 c0 <89> 03 0f 84 92 04 00 00 8b 5c 24 0c 31 c0 b9 23 02 00 00 03 b4
EIP: [<e08e3de6>] tor2_probe+0x4b4/0x962 [tor2] SS:ESP 0068:de397df8
---[ end trace dbac70f672af8a35 ]---
By: Tzafrir Cohen (tzafrir) 2008-10-15 12:14:07

Replacing the original description with a new one.

Can anybody confirm success with a tor2 card?
By: Tzafrir Cohen (tzafrir) 2008-10-15 12:16:50

This is a different bug, needs to be re-confirmed
By: Roman Yeryomin (leroi05) 2008-10-15 14:58:52

I have the same issue

[ 2333.876751] dahdi: Telephony Interface Registered on major 196
[ 2333.876754] dahdi: Version: 2.0.0
[ 2333.880733] ACPI: PCI Interrupt 0000:04:01.0[A] -> Link [LNKB] -> GSI 15 (level, low) -> IRQ 15
[ 2333.880744] Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xfebef000/0xfebee800 irq 15
[ 2333.993184] Xilinx Chip successfully loaded, configured and started!!
[ 2333.993237] Tormenta 2 Quad E1/PRA Card
[ 2333.993239] BUG: unable to handle kernel NULL pointer dereference at 00000000
[ 2333.993295] IP: [<f8c4468f>] :tor2:tor2_probe+0x77f/0xca5
[ 2333.993331] *pdpt = 0000000036881001 *pde = 0000000000000000
[ 2333.993334] Oops: 0002 [#1]
[ 2333.993358] Modules linked in: tor2(+) dahdi crc_ccitt nf_conntrack_ipv4 xt_state nf_conntrack xt_limit xt_comment iptable_filter ip_tables x_tables loop evdev
[ 2333.993480]
[ 2333.993506] Pid: 6097, comm: modprobe Not tainted (2.6.25.18 #1)
[ 2333.993539] EIP: 0060:[<f8c4468f>] EFLAGS: 00010286 CPU: 0
[ 2333.993572] EIP is at tor2_probe+0x77f/0xca5 [tor2]
[ 2333.993603] EAX: f6443000 EBX: 00000000 ECX: f8c4468b EDX: f6443000
[ 2333.993637] ESI: 00000000 EDI: f68b8000 EBP: 00000000 ESP: f69e5da4
[ 2333.993670]  DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
[ 2333.993702] Process modprobe (pid: 6097, ti=f69e4000 task=f6879640 task.ti=f69e4000)
[ 2333.993737] Stack: f8c56340 f68b8000 febef000 febee800 0000000f f7ce98d0 c01aa813 f8c57b38
[ 2333.993810]        00000080 00000800 00000800 00000000 c01ab56f f68b8000 f78474c0 00000000
[ 2333.993887]        c01f6a4f f8c43f10 f7d04c00 f8c57a80 c0434200 c02060d6 f7d04c54 00000000
[ 2333.993961] Call Trace:
[ 2333.994018]  [<c01aa813>] sysfs_add_one+0x43/0xa0
[ 2333.994057]  [<c01ab56f>] sysfs_create_link+0x6f/0xd0
[ 2333.994094]  [<c01f6a4f>] kobject_get+0xf/0x20
[ 2333.994140]  [<f8c43f10>] tor2_probe+0x0/0xca5 [tor2]
[ 2333.994178]  [<c02060d6>] pci_device_probe+0x56/0x80
[ 2333.994180]  [<c02537d1>] driver_probe_device+0x81/0x170
[ 2333.994180]  [<c033f8f1>] klist_next+0x51/0xb0
[ 2333.994180]  [<c02539f6>] __driver_attach+0x76/0x80
[ 2333.994180]  [<c0252b7a>] bus_for_each_dev+0x3a/0x60
[ 2333.994180]  [<c0206080>] pci_device_probe+0x0/0x80
[ 2333.994180]  [<c0253656>] driver_attach+0x16/0x20
[ 2333.994180]  [<c0253980>] __driver_attach+0x0/0x80
[ 2333.994180]  [<c02534f1>] bus_add_driver+0x1a1/0x220
[ 2333.994180]  [<c0206020>] pci_device_remove+0x0/0x40
[ 2333.994180]  [<c0206080>] pci_device_probe+0x0/0x80
[ 2333.994180]  [<c0253b7b>] driver_register+0x3b/0xe0
[ 2333.994180]  [<c02062c6>] __pci_register_driver+0x36/0x70
[ 2333.994180]  [<f8c03018>] tor2_init+0x18/0x2d [tor2]
[ 2333.994180]  [<c0137383>] sys_init_module+0x113/0x1740
[ 2333.994180]  [<f8c11480>] dahdi_lboname+0x0/0x20 [dahdi]
[ 2333.994180]  [<c015d831>] do_mmap_pgoff+0x351/0x380
[ 2333.994180]  [<c0105eca>] sys_mmap2+0xca/0xd0
[ 2333.994180]  [<c0103af6>] sysenter_past_esp+0x5f/0x85
[ 2333.994180]  =======================
[ 2333.994180] Code: 7d da 8b 54 24 3c b8 e0 b0 44 c0 8b 4c 24 34 8d 34 ad 00 00 00 00 8b 9c 91 44 07 00 00 ba d0 00 00 00 e8 a5 70 52 c7 01 f3 85 c0 <89> 03 0f 84 2b fb ff ff 8b 7c 24 34 31 c0 b9 23 02 00 00 8b 5c
[ 2333.994180] EIP: [<f8c4468f>] tor2_probe+0x77f/0xca5 [tor2] SS:ESP 0068:f69e5da4
[ 2333.994183] ---[ end trace 624a8a24d234bf12 ]---
[ 2334.016712] dahdi_dummy: Trying to load High Resolution Timer
[ 2334.016775] dahdi_dummy: Initialized High Resolution Timer
[ 2334.016856] dahdi_dummy: Starting High Resolution Timer
[ 2334.016917] dahdi_dummy: High Resolution Timer started, good to go

lsmod
Module                  Size  Used by
tor2                   89933  1
dahdi                 194440  1 tor2
crc_ccitt               2304  1 dahdi
nf_conntrack_ipv4      17800  3
xt_state                2688  3
nf_conntrack           62756  2 nf_conntrack_ipv4,xt_state
xt_limit                2816  1
xt_comment              2048  9
iptable_filter          3584  1
ip_tables              13328  1 iptable_filter
x_tables               16516  4 xt_state,xt_limit,xt_comment,ip_tables
loop                   17796  0
evdev                  11776  0

ls -la /dev/dahdi/
total 0
drwxr-xr-x  2 root root      120 2008-10-15 22:28 .
drwxr-xr-x 10 root root    13380 2008-10-15 22:28 ..
crw-rw----  1 root root 196, 254 2008-10-15 22:28 channel
crw-rw----  1 root root 196,   0 2008-10-15 22:28 ctl
crw-rw----  1 root root 196, 255 2008-10-15 22:28 pseudo
crw-rw----  1 root root 196, 253 2008-10-15 22:28 timer


tor2 module cannot be unloaded, even with rmmod -f
By: Tzafrir Cohen (tzafrir) 2008-10-15 15:28:32

So it prints "Tormenta 2 Quad E1/PRA Card" from line 538 but doesn't print "Detected Card number:" on line 562 .

My bet is on:

 if (!(tor->chans[x][f] = kmalloc(sizeof(*tor->chans[x][f]), GFP_KERNEL))) {

We should kmalloc chans[x] first, right?
By: Roman Yeryomin (leroi05) 2008-10-15 15:54:19

Maybe, this is new code comparing to zaptel
Well, who can write the code? I can test it right now...
By: Shane Young (shanermn) 2008-10-15 16:08:05

I have tried loading the tor2 on a couple of different (amd and intel) with gentoo and ubuntu and I get the same results.

If you'd like access to a machine with a tor2 card, let me know.
By: Tzafrir Cohen (tzafrir) 2008-10-16 06:17:46

Wow, that part of tor2 looks bad indeed.

Somebody wrote a nice faults handler, and yet in case of no memory, it just returns -ENOMEM and frees no resource. It always returns -ENODEV regardless of the issue. Ah, and the original null pointer issue.

The patch I uploaded attempts, sadly, to handle them all instead of a specific patch for each issue. I also changed every message that indicates a failure of loading the module to KERN_ERR .
By: heyuqi (heyuqi) 2008-10-17 01:14:56

I patch the tor2 ,then install Quad e1 card.But Linux stop when running at 'satring undev [ok]' , not found some Call Trace Info . When I remove the card , Linux run normally.
My card is Atcom AX-4E

[root@asterisk ~]# uname -a
Linux asterisk 2.6.18-92.1.10.el5 #1 SMP Tue Aug 5 07:41:53 EDT 2008 i686 i686 i386 GNU/Linux

[root@asterisk ~]# asterisk -r
Asterisk 1.6.0-rc6, Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.6.0-rc6 currently running on asterisk (pid = 2859)
Verbosity is at least 3
asterisk*CLI> dahdi show status
Description                              Alarms  IRQ    bpviol CRC4   Fra Codi Options  LBO
DAHDI_DUMMY/1 (source: RTC) 1            UNCONFI 0      0      0      CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
asterisk*CLI>


By: Tzafrir Cohen (tzafrir) 2008-10-17 06:04:32

What do you mean by "linux stop"? System completly hanged at boot time? Do you see any message?

Can you move the module somewhere elase and try to boot with the card and then load the module? Do you see any message on the console?
By: Roman Yeryomin (leroi05) 2008-10-17 10:29:25

I've patched one of my asterisks but it didn't come online after reboot. I can get there only on Monday (20 of october) to see what happened there. I have one more to patch but don't want to lose another one
By: heyuqi (heyuqi) 2008-10-21 01:07:26

While I have patched , System hanged at boot time I don't see any message.

You said to move the module. Is that mean uninstall dahdi? Because I cannot stop modules using modprod .
By: Shane Young (shanermn) 2008-10-21 04:24:26

This looks better:
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.0.0
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 19
Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xdfffb000/0xdfffa800 irq 19
Xilinx Chip successfully loaded, configured and started!!
Tormenta 2 Quad T1/PRI Card
Detected Card number: 0
Tor2: Launching card: 0
Registered Tormenta2 PCI
By: Shane Young (shanermn) 2008-10-21 04:24:52

This also seems to work now:
# dahdi_cfg -vvvvv          
DAHDI Tools Version - 2.0.0

DAHDI Version: 2.0.0
Echo Canceller(s):
Configuration
======================

SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 3: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 4: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: FXO Kewlstart (Default) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Slaves: 02)
Channel 03: FXO Kewlstart (Default) (Slaves: 03)
Channel 04: FXO Kewlstart (Default) (Slaves: 04)
Channel 05: FXO Kewlstart (Default) (Slaves: 05)
Channel 06: FXO Kewlstart (Default) (Slaves: 06)
Channel 07: FXO Kewlstart (Default) (Slaves: 07)
Channel 08: FXO Kewlstart (Default) (Slaves: 08)
Channel 09: FXO Kewlstart (Default) (Slaves: 09)
Channel 10: FXO Kewlstart (Default) (Slaves: 10)
Channel 11: FXO Kewlstart (Default) (Slaves: 11)
Channel 12: FXO Kewlstart (Default) (Slaves: 12)
Channel 13: FXO Kewlstart (Default) (Slaves: 13)
Channel 14: FXO Kewlstart (Default) (Slaves: 14)
Channel 15: FXO Kewlstart (Default) (Slaves: 15)
Channel 16: FXO Kewlstart (Default) (Slaves: 16)
Channel 17: FXO Kewlstart (Default) (Slaves: 17)
Channel 18: FXO Kewlstart (Default) (Slaves: 18)
Channel 19: FXO Kewlstart (Default) (Slaves: 19)
Channel 20: FXO Kewlstart (Default) (Slaves: 20)
Channel 21: FXO Kewlstart (Default) (Slaves: 21)
Channel 22: FXO Kewlstart (Default) (Slaves: 22)
Channel 23: FXO Groundstart (Default) (Slaves: 23)
Channel 24: FXO Loopstart (Default) (Slaves: 24)
Channel 25: FXO Kewlstart (Default) (Slaves: 25)
Channel 26: FXO Kewlstart (Default) (Slaves: 26)
Channel 27: FXO Kewlstart (Default) (Slaves: 27)
Channel 28: FXO Kewlstart (Default) (Slaves: 28)
Channel 29: FXO Kewlstart (Default) (Slaves: 29)
Channel 30: FXO Groundstart (Default) (Slaves: 30)
Channel 31: FXO Loopstart (Default) (Slaves: 31)
Channel 32: FXO Kewlstart (Default) (Slaves: 32)
Channel 33: FXO Kewlstart (Default) (Slaves: 33)
Channel 34: FXO Kewlstart (Default) (Slaves: 34)
Channel 35: FXO Kewlstart (Default) (Slaves: 35)
Channel 36: FXO Kewlstart (Default) (Slaves: 36)
Channel 37: FXO Kewlstart (Default) (Slaves: 37)
Channel 38: FXO Kewlstart (Default) (Slaves: 38)
Channel 39: FXO Kewlstart (Default) (Slaves: 39)
Channel 40: FXO Kewlstart (Default) (Slaves: 40)
Channel 41: FXS Kewlstart (Default) (Slaves: 41)
Channel 42: FXS Kewlstart (Default) (Slaves: 42)
Channel 43: FXS Kewlstart (Default) (Slaves: 43)
Channel 44: FXS Kewlstart (Default) (Slaves: 44)
Channel 45: FXS Kewlstart (Default) (Slaves: 45)
Channel 46: FXS Kewlstart (Default) (Slaves: 46)
Channel 47: FXS Kewlstart (Default) (Slaves: 47)
Channel 48: FXS Kewlstart (Default) (Slaves: 48)
Channel 49: FXO Kewlstart (Default) (Slaves: 49)
Channel 50: FXO Kewlstart (Default) (Slaves: 50)
Channel 51: FXO Kewlstart (Default) (Slaves: 51)
Channel 52: FXO Kewlstart (Default) (Slaves: 52)
Channel 53: FXO Kewlstart (Default) (Slaves: 53)
Channel 54: FXO Kewlstart (Default) (Slaves: 54)
Channel 55: FXO Kewlstart (Default) (Slaves: 55)
Channel 56: FXO Kewlstart (Default) (Slaves: 56)
Channel 57: FXO Kewlstart (Default) (Slaves: 57)
Channel 58: FXO Kewlstart (Default) (Slaves: 58)
Channel 59: FXO Kewlstart (Default) (Slaves: 59)
Channel 60: FXO Kewlstart (Default) (Slaves: 60)
Channel 61: FXO Kewlstart (Default) (Slaves: 61)
Channel 62: FXO Kewlstart (Default) (Slaves: 62)
Channel 63: FXO Kewlstart (Default) (Slaves: 63)
Channel 64: FXO Kewlstart (Default) (Slaves: 64)
Channel 65: FXO Kewlstart (Default) (Slaves: 65)
Channel 66: FXO Kewlstart (Default) (Slaves: 66)
Channel 67: FXO Kewlstart (Default) (Slaves: 67)
Channel 68: FXO Kewlstart (Default) (Slaves: 68)
Channel 69: FXO Kewlstart (Default) (Slaves: 69)
Channel 70: FXO Kewlstart (Default) (Slaves: 70)
Channel 71: FXO Kewlstart (Default) (Slaves: 71)
Channel 72: FXO Kewlstart (Default) (Slaves: 72)

72 channels to configure.

Changing master of channel 3 from 25 to 3
Changing master of channel 4 from 26 to 4
Changing master of channel 5 from 27 to 5
Changing master of channel 6 from 28 to 6
Changing master of channel 7 from 29 to 7
Changing signalling on channel 8 from FXO Groundstart to FXO Kewlstart
Changing master of channel 8 from 30 to 8
Changing signalling on channel 9 from FXO Loopstart to FXO Kewlstart
Changing master of channel 9 from 31 to 9
Changing master of channel 10 from 32 to 10
Changing master of channel 11 from 33 to 11
Changing master of channel 12 from 34 to 12
Changing master of channel 13 from 35 to 13
Changing master of channel 14 from 36 to 14
Changing master of channel 15 from 37 to 15
Changing master of channel 16 from 38 to 16
Changing master of channel 17 from 39 to 17
Changing master of channel 18 from 40 to 18
Changing signalling on channel 19 from FXS Kewlstart to FXO Kewlstart
Changing master of channel 19 from 41 to 19
Changing signalling on channel 20 from FXS Kewlstart to FXO Kewlstart
Changing master of channel 20 from 42 to 20
Changing signalling on channel 21 from FXS Kewlstart to FXO Kewlstart
Changing master of channel 21 from 43 to 21
Changing signalling on channel 22 from FXS Kewlstart to FXO Kewlstart
Changing master of channel 22 from 44 to 22
Changing signalling on channel 23 from FXS Kewlstart to FXO Groundstart
Changing master of channel 23 from 45 to 23
Changing signalling on channel 24 from FXS Kewlstart to FXO Loopstart
Changing master of channel 24 from 46 to 24
Changing signalling on channel 30 from FXO Kewlstart to FXO Groundstart
Changing signalling on channel 31 from FXO Kewlstart to FXO Loopstart
Changing signalling on channel 41 from FXO Kewlstart to FXS Kewlstart
Changing signalling on channel 42 from FXO Kewlstart to FXS Kewlstart
Changing signalling on channel 43 from FXO Kewlstart to FXS Kewlstart
Changing signalling on channel 44 from FXO Kewlstart to FXS Kewlstart
Changing signalling on channel 45 from FXO Groundstart to FXS Kewlstart
Changing signalling on channel 46 from FXO Loopstart to FXS Kewlstart
By: Shane Young (shanermn) 2008-10-21 04:33:40

It appears that the patch is working.  Everything seems to come up correctly and I have carrier on all 4 spans now.
By: Tzafrir Cohen (tzafrir) 2008-10-21 04:41:30

shanermn: did you just install the tor2 module and modprobe it?

Any other reports, either way?
By: Shane Young (shanermn) 2008-10-21 04:56:27

I initially installed the tor2 module with the rest of dahdi, but it failed to load.  I downloaded and applied the patch and now the module appears to load correctly.  I can modprobe tor2 and it loads, however if I do a rmmod tor2 it seems to crash pretty hard.

Kernel panic, not syncing.

Need to hard reset the system.


By: Roman Yeryomin (leroi05) 2008-10-21 15:58:16

I've visited that patched asterisk which didn't come up online after reboot.
Screens are available here:
http://wiz.lv/tor2/
By: Tzafrir Cohen (tzafrir) 2008-10-22 05:00:32

leori05: that looks like an oops from the context of the modprobe context. Does it leave the system hung?
By: Roman Yeryomin (leroi05) 2008-10-22 10:53:29

Sometimes yes, but only if I press Ctrl-Alt-Del.
By: heyuqi (heyuqi) 2008-10-23 04:49:38

I move the tor2, then boot system with card. The system can starup normally, then move tor2 to the original place and modprobe tor2 module, the system hung up .

Call Trace
[<>] sprintf+0x1d/0x20
[<>] tor2_probe+0x802/0xa6f [tor2]
[<>] pci_match_device+0x10/0xac
[<>] __driver_attach+0x0/0x6b
[<>] pci_device_probe_device+0x36/0x57
[<>] driver_probe_device+0x42/0x92
[<>] __driver_attach+0x44/0x6b
[<>] bus_for_eatch_dev+0x37/0x59
[<>] driver_attach+0x11/0x13
[<>] __driver_attach+0x0/0x6b
[<>] bus_add_driver+0x64/0xfd
[<>] __pci_register_driver+0x3e/0x58
[<>] tor2_init+1x10/0x21 [tor2]
[<>] sys_init_module+1x10b5/0x1a60
[<>] dahdi_lboname+0x0/0x14 [dahdi]
[<>] audit_syscall_entry+0x14b/0x17d
[<>] syscall_call+0x7/0xb


By: Tzafrir Cohen (tzafrir) 2008-10-24 06:11:06

The trace suggests that one of the two sprintf-s in init_tor() is to blame. I can't find anything wrong there. Thus I added some extra debug prints in that function .

The patch tor2_dahdi_2.diff includes the previous changes with those extra debug prints.
By: Tzafrir Cohen (tzafrir) 2008-10-28 17:05:16

Can anybody try this?
By: heyuqi (heyuqi) 2008-10-28 23:01:05

When I modprobe tor2 ,appear follow Info.(Otherwise,can these info save in any log file?)  

list_del corruption prev_next should bu f1405c60 ,but was c16bd6000
-----[cut here]-----

kernel BUB at /ib/list_debug.c:65!
invaild opcode: 0000[#1]
SMP
last sysfs file: /class/dahdi/dahdi/24/dev
Modules linked in:tor2(U) IPV6 xfrm_nalog crypto_api autofs4 hidp rfcomm l2cap bluetooth sunrpc xpp_usb(U) xpp(U) dahdi_dummy(U) wctdm(U) wcfxo(U) wcte12xp(U) wct4xxp(U) dm_multipath video sbs backlight i2c_ec button battery asus_acpi ac parport_pc lp partport sg i6300esb floppy pcspkr i2c_i801 e1000 dahdi(U) crc_citt i2c_core ide_cd cdrom i82857p_edac edac_mc dm_snapshot dm_zero dm_mirror
dm_mod ata_piix libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd
cpu: 0
EIP: 0060: [<04e79f4>] Tainted:G VLI
EFLAGS: 00010046 (2.6.18-92.1.10.e15#1)
EIP is at list_del+0x18/0x5c
eax:00000048 ebx:f1405c60 ecx:00000086 edx:00000000 esi:f7ffd440 edi:ef893000 ebp:f7fffe80 esp:f7feff0c ds:007b es:007b ss:0068
Proccess events/0(pid:8,ti=f7fef000 task=f7cd6000 task.ti=f7fef000)
stack:
c0638469 f1405c60 c1bd6000 f1405c60 c045d2a7 00000046 00000014 00000008 f7ffa234 f7ffa214 00000014 f7ffa200 f7ffd440 c046d394 00000000 f7fffe80 f7ffd440 f7fffe80 f7cdcdc0 00000286 c046e6aa 00000000 00000000 c1808060


By: heyuqi (heyuqi) 2008-11-11 07:36:07.000-0600

Is that useful??
By: Tzafrir Cohen (tzafrir) 2008-11-11 10:24:36.000-0600

ok, I'm a bit confused as we seem to have some different reports.

When you modprobe, is the system configured to run ztcfg immediately after that? If so: could you please disable that (at least for debugging this)?
By: Digium Subversion (svnbot) 2008-11-20 06:31:55.000-0600

Repository: dahdi
Revision: 5345

U   linux/trunk/drivers/dahdi/tor2.c

------------------------------------------------------------------------
r5345 | tzafrir | 2008-11-20 06:31:55 -0600 (Thu, 20 Nov 2008) | 4 lines

Make tor2 load properly. Seems to fix DAHLIN-38.

Thanks to heyuqi for the testing.

------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=5345
By: Tzafrir Cohen (tzafrir) 2008-11-20 06:33:45.000-0600

The driver should load now. But I'm not yet sure that the driver is fully functional. Maybe there's also an issue with alarms.

So can anybody with a card check this?
By: Roman Yeryomin (leroi05) 2008-11-24 09:07:49.000-0600

I didn't make any calls yet but I have OK on `dahdi show status`.
I will try to make calls tomorrow (nov 25) and post result here
By: Roman Yeryomin (leroi05) 2008-11-28 18:47:58.000-0600

few calls went through fine
will try in production with low traffic

probably it's not related but nevertheless.. I'm getting this disturbing messages when trying to call:

chan_dahdi.c:2712 dahdi_call: Unrecognized prilocaldialplan TON modifier: 0

prilocaldialplan is set to unknown
By: Roman Yeryomin (leroi05) 2008-12-01 10:10:02.000-0600

up to 40 concurrent calls are doing fine
no complains from customers during 20 hour work!
I suppose your fix, tzafrir, is working so far...
By: Tzafrir Cohen (tzafrir) 2008-12-01 10:25:17.000-0600

Looks like issue has been resolved. Thanks to everyobody for testing.