[asterisk-users] zaptel 1.4.10 regression with TE220B on Proliant DL380 G5 ?

Ex Vito ex.vitorino at gmail.com
Wed Apr 16 11:50:33 CDT 2008


  update with no 4K stack kernel:

  - The kernel was build from stock centos 5 kernel 2.6.18-53.1.14.el5
  - The only .config change was to disable the CONFIG_4KSTACKS

  Tested zaptel-1.4.10, 1.4.9.2 and the stackcleanup svn branch as
  suggested by Shaun and Mathew.

  Short: Results are about the same (stack traces are different).
             1.4.10 and the stackcleanup lead to soft hangups, 1.4.9.2
             does not.

  1.4.10 dmesg snippet:

Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.10
Zaptel Echo Canceller: MG2
ACPI: PCI Interrupt 0000:12:01.0[A] -> GSI 25 (level, low) -> IRQ 154
wcte12xp: Setting up global serial parameters for T1
wcte12xp: Found a Wildcard TE122
ACPI: PCI Interrupt 0000:18:08.0[A] -> GSI 19 (level, low) -> IRQ 162
Found TE2XXP at base address fdff0000, remapped to f893e000
TE2XXP version c01a016a, burst ON
Octasic optimized!
FALC version: 00000005, Board ID: 00
Reg 0: 0x3613a400
Reg 1: 0x3613a000
Reg 2: 0xffffffff
Reg 3: 0x00000000
Reg 4: 0x00003101
Reg 5: 0x00000000
Reg 6: 0xc01a016a
Reg 7: 0x00001300
Reg 8: 0x00000000
Reg 9: 0x00ff0031
Reg 10: 0x0000004a
TE2XXP: Launching card: 0
TE2XXP: Setting up global serial parameters
Found a Wildcard: Wildcard TE220 (4th Gen)
About to enter spanconfig!
Done with spanconfig!
About to enter spanconfig!
Done with spanconfig!
Registered tone zone 25 (Portugal)
wcte12xp: Span configured for ESF/B8ZS
About to enter startup!
TE2XXP: Span 1 configured for CCS/HDB3/CRC4
timing source auto card 0!
wct2xxp: Setting yellow alarm on span 1
timing source auto card 0!
SPAN 2: Primary Sync Source
VPM400: Not Present
wcte12xp: Setting yellow alarm
VPM450: echo cancellation for 64 channels
wcte12xp: Clearing yellow alarm
BUG: soft lockup detected on CPU#1!
 [<c044d480>] softlockup_tick+0x96/0xa4
 [<c042de00>] update_process_times+0x39/0x5c
 [<c04196ef>] smp_apic_timer_interrupt+0x5b/0x6c
 [<c04059bf>] apic_timer_interrupt+0x1f/0x24
 [<c0605c30>] _spin_unlock_irqrestore+0x8/0x9
 [<f8e82d57>] Oct6100UserDriverWriteBurstApi+0x1d/0x27 [wct4xxp]
 [<f8e95de0>] Oct6100ApiLoadImage+0x1b5/0x289 [wct4xxp]
 [<f8e9afc4>] Oct6100ChipOpen+0x166/0x25e [wct4xxp]
 [<f8e83050>] init_vpm450m+0x196/0x306 [wct4xxp]
 [<f8e6ab11>] t4_vpm450_init+0x18ce/0x198c [wct4xxp]
 [<f8e6eee4>] t4_startup+0x4315/0x43c7 [wct4xxp]
 [<c042624e>] release_console_sem+0x1b0/0x1b8
 [<c042680e>] printk+0x18/0x8e
 [<f8af6fe4>] t1_configure_t1+0xc10/0xc18 [wcte12xp]
 [<f8ac65ef>] zt_rbs_sethook+0x102/0x13b [zaptel]
 [<f8acdf6a>] zt_ioctl+0x273/0x144f [zaptel]
 [<f885626f>] __journal_file_buffer+0x10e/0x1e3 [jbd]
 [<f885626f>] __journal_file_buffer+0x10e/0x1e3 [jbd]
 [<c0483cb3>] __d_lookup+0x98/0xdb
 [<c047b32c>] do_lookup+0x53/0x166
 [<c047d9ec>] do_path_lookup+0x20e/0x25e
 [<c0471053>] get_empty_filp+0x99/0x15e
 [<c047b5a5>] permission+0xa2/0xb5
 [<c04e1a36>] kobject_get+0xf/0x13
 [<c046ea1e>] __dentry_open+0xea/0x1ab
 [<c046eb43>] nameidata_to_filp+0x19/0x28
 [<c046eb7d>] do_filp_open+0x2b/0x31
 [<c047f4a7>] do_ioctl+0x47/0x5d
 [<c047f707>] vfs_ioctl+0x24a/0x25c
 [<c0470de6>] __fput+0x13f/0x167
 [<c047f761>] sys_ioctl+0x48/0x5f
 [<c0404eff>] syscall_call+0x7/0xb
 =======================
VPM450: hardware DTMF disabled.
VPM450: Present and operational servicing 2 span(s)
Completed startup!
About to enter startup!
TE2XXP: Span 2 configured for CCS/HDB3/CRC4
wct2xxp: Setting yellow alarm on span 2
timing source auto card 0!
SPAN 3: Secondary Sync Source
Completed startup!

  1.4.9.2 dmesg snippet:

Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.9.2
Zaptel Echo Canceller: MG2
PCI: Enabling device 0000:12:01.0 (0150 -> 0153)
ACPI: PCI Interrupt 0000:12:01.0[A] -> GSI 25 (level, low) -> IRQ 154
wcte12x[p]: Setting up global serial parameters for T1
wcte12x[p]: Found a Wildcard TE122
Found TE2XXP at base address fdff0000, remapped to f893e000
TE2XXP version c01a016a, burst ON
Octasic optimized!
FALC version: 00000005, Board ID: 00
Reg 0: 0x3571b400
Reg 1: 0x3571b000
Reg 2: 0xffffffff
Reg 3: 0x00000000
Reg 4: 0x00000101
Reg 5: 0x00000000
Reg 6: 0xc01a016a
Reg 7: 0x00001300
Reg 8: 0x010200ff
Reg 9: 0x00fd0001
Reg 10: 0x0000004a
TE2XXP: Launching card: 0
TE2XXP: Setting up global serial parameters
Found a Wildcard: Wildcard TE220 (4th Gen)
About to enter spanconfig!
Done with spanconfig!
About to enter spanconfig!
Done with spanconfig!
Registered tone zone 25 (Portugal)
wcte12x[p]: Span configured for ESF/B8ZS
About to enter startup!
TE2XXP: Span 1 configured for CCS/HDB3/CRC4
timing source auto card 0!
wct2xxp: Setting yellow alarm on span 1
SPAN 2: Primary Sync Source
timing source auto card 0!
VPM400: Not Present
VPM450: echo cancellation for 64 channels
VPM450: hardware DTMF disabled.
VPM450: Present and operational servicing 2 span(s)
Completed startup!
About to enter startup!
TE2XXP: Span 2 configured for CCS/HDB3/CRC4
wct2xxp: Setting yellow alarm on span 2
SPAN 3: Secondary Sync Source
Completed startup!
timing source auto card 0!


  1.4-stackcleanup-r4163 dmesg snippet:

Zapata Telephony Interface Registered on major 196
Zaptel Version: SVN-mattf-zaptel-1.4-stackcleanup-r4163
Zaptel Echo Canceller: MG2
wcte12xp: Setting up global serial parameters for T1
wcte12xp: Found a Wildcard TE122
Found TE2XXP at base address fdff0000, remapped to f893e000
TE2XXP version c01a016a, burst ON
Octasic optimized!
FALC version: 00000005, Board ID: 00
Reg 0: 0x3491a400
Reg 1: 0x3491a000
Reg 2: 0xffffffff
Reg 3: 0x00000000
Reg 4: 0x00000101
Reg 5: 0x00000000
Reg 6: 0xc01a016a
Reg 7: 0x00001300
Reg 8: 0x010200ff
Reg 9: 0x00fd0001
Reg 10: 0x0000004a
TE2XXP: Launching card: 0
TE2XXP: Setting up global serial parameters
Found a Wildcard: Wildcard TE220 (4th Gen)
About to enter spanconfig!
Done with spanconfig!
About to enter spanconfig!
Done with spanconfig!
Registered tone zone 25 (Portugal)
wcte12xp: Span configured for ESF/B8ZS
About to enter startup!
TE2XXP: Span 1 configured for CCS/HDB3/CRC4
timing source auto card 0!
wct2xxp: Setting yellow alarm on span 1
SPAN 2: Primary Sync Source
timing source auto card 0!
VPM400: Not Present
VPM450: echo cancellation for 64 channels
BUG: soft lockup detected on CPU#1!
 [<c044d480>] softlockup_tick+0x96/0xa4
 [<c042de00>] update_process_times+0x39/0x5c
 [<c04196ef>] smp_apic_timer_interrupt+0x5b/0x6c
 [<c04059bf>] apic_timer_interrupt+0x1f/0x24
 [<c0605c30>] _spin_unlock_irqrestore+0x8/0x9
 [<f8e82d57>] Oct6100UserDriverWriteBurstApi+0x1d/0x27 [wct4xxp]
 [<f8e95de0>] Oct6100ApiLoadImage+0x1b5/0x289 [wct4xxp]
 [<f8e9afc4>] Oct6100ChipOpen+0x166/0x25e [wct4xxp]
 [<f8e83050>] init_vpm450m+0x196/0x306 [wct4xxp]
 [<f8e6ab11>] t4_vpm450_init+0x18ce/0x198c [wct4xxp]
 [<f8e6eee4>] t4_startup+0x4315/0x43c7 [wct4xxp]
 [<c042624e>] release_console_sem+0x1b0/0x1b8
 [<c042680e>] printk+0x18/0x8e
 [<f8af6fe4>] t1_configure_t1+0xc10/0xc18 [wcte12xp]
 [<f8ac65ef>] zt_rbs_sethook+0x102/0x13b [zaptel]
 [<f8acdf39>] zt_ioctl+0x273/0x14be [zaptel]
 [<c04777b1>] chrdev_open+0x11e/0x132
 [<c0477693>] chrdev_open+0x0/0x132
 [<c046ea1e>] __dentry_open+0xea/0x1ab
 [<c047f4a7>] do_ioctl+0x47/0x5d
 [<c047f707>] vfs_ioctl+0x24a/0x25c
 [<c0470de6>] __fput+0x13f/0x167
 [<c047f761>] sys_ioctl+0x48/0x5f
 [<c0404eff>] syscall_call+0x7/0xb
 =======================
wcte12xp0: Missed interrupt. Increasing latency to 4 ms in order to compensate.
VPM450: hardware DTMF disabled.
VPM450: Present and operational servicing 2 span(s)
Completed startup!
About to enter startup!
TE2XXP: Span 2 configured for CCS/HDB3/CRC4
wct2xxp: Setting yellow alarm on span 2
timing source auto card 0!
SPAN 3: Secondary Sync Source
Completed startup!


  More context info regarding this system:

  - The objective was to go live in about a week
  - Since we are RMAing a TC400B which we had trouble
    getting to work (according to Digium install support, it is
    probably faulty), we will probably have to delay the
    go live date -- our supplier won't be as fast as we wished

  Question:

  - If we were to go live now, should we go with 1.4.9.2 or
    1.4.10 and disregard the soft hangup since it is related
    to FW update ?...

  - Could this prevent future FW upgrades on the card ?

  Regards,
--
  exvito



More information about the asterisk-users mailing list