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

[Shaun Ruffell]

Ex Vito,

[comments inline]

Ex Vito wrote:
>   Hi list,
> 
>   After a lot of testing + troubleshooting, I guess I'm observing
>   what I am now calling a regression with zaptel 1.4.10 (is it?)
>   As such I call for peer feedback, before either asking Digium
>   install support or filing a bug.
> 
> 
>   Under zaptel 1.4.10, when ztcfg runs this gets logged in the kernel
>   buffer:
> 
> About to enter spanconfig!
> Done with spanconfig!
> About to enter spanconfig!
> Done with spanconfig!
> 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 1: Primary Sync Source
> VPM400: Not Present
> VPM450: echo cancellation for 64 channels
> BUG: soft lockup detected on CPU#0!
>  [<c044d448>] softlockup_tick+0x96/0xa4
>  [<c042ddc8>] update_process_times+0x39/0x5c
>  [<c04196f7>] smp_apic_timer_interrupt+0x5b/0x6c
>  [<c04059bf>] apic_timer_interrupt+0x1f/0x24
>  [<f89bc1e7>] init_vpm450m+0x32d/0x34a [wct4xxp]
>  [<f89a3b11>] t4_vpm450_init+0x18ce/0x198c [wct4xxp]
>  [<f89a7ee4>] t4_startup+0x4315/0x43c7 [wct4xxp]
>  [<c042621c>] release_console_sem+0x17e/0x1b8
>  [<c0407406>] do_IRQ+0xa5/0xae
>  [<f8994311>] t4_dacs+0x211/0x24b [wct4xxp]
>  [<f8a01f6a>] zt_ioctl+0x273/0x144f [zaptel]
>  [<c0457600>] mempool_alloc+0x28/0xc9
>  [<c04ddd33>] cfq_resort_rr_list+0x23/0x8b
>  [<c04deb6c>] cfq_add_crq_rb+0xba/0xc3
>  [<c04dec72>] cfq_insert_request+0x42/0x498
>  [<c04d5175>] elv_insert+0x10a/0x1ad
>  [<c04d908b>] __make_request+0x31d/0x366
>  [<c04de8b1>] cfq_dispatch_requests+0x26a/0x46b
>  [<c04dde27>] __cfq_slice_expired+0x8c/0xa5
>  [<c04de8b1>] cfq_dispatch_requests+0x26a/0x46b
>  [<c04d505d>] elv_next_request+0x15c/0x16a
>  [<f88bc101>] start_io+0x77/0xdc [cciss]
>  [<f88bf63e>] do_cciss_request+0x32c/0x337 [cciss]
>  [<f88ccff0>] __split_bio+0x408/0x418 [dm_mod]
>  [<f88cd6a6>] dm_request+0xce/0xd4 [dm_mod]
>  [<c04d6a81>] generic_make_request+0x248/0x258
>  [<c04d8734>] submit_bio+0xbf/0xc5
>  [<c04548e2>] find_get_page+0x18/0x38
>  [<c04719ad>] __find_get_block_slow+0xfb/0x105
>  [<c0471cea>] __find_get_block+0x15c/0x166
>  [<c0471cea>] __find_get_block+0x15c/0x166
>  [<c0471d24>] __getblk+0x30/0x270
>  [<f885a485>] journal_cancel_revoke+0x8a/0x96 [jbd]
>  [<f885a472>] journal_cancel_revoke+0x77/0x96 [jbd]
>  [<f885626f>] __journal_file_buffer+0x10e/0x1e3 [jbd]
>  [<c041f871>] __wake_up+0x2a/0x3d
>  [<f8856679>] journal_stop+0x1b0/0x1ba [jbd]
>  [<c042a209>] current_fs_time+0x4a/0x55
>  [<c048626d>] touch_atime+0x60/0x8f
>  [<c04552ee>] do_generic_mapping_read+0x421/0x468
>  [<c045478b>] file_read_actor+0x0/0xd1
>  [<c04548e2>] find_get_page+0x18/0x38
>  [<c0457319>] filemap_nopage+0x192/0x315
>  [<c046048f>] __handle_mm_fault+0x85e/0x87b
>  [<c047f46b>] do_ioctl+0x47/0x5d
>  [<c047f6cb>] vfs_ioctl+0x24a/0x25c
>  [<c047f725>] 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 2: Secondary Sync Source
> Completed startup!


Your stack trace appears to possibly be stack corruption. 

Could you try either this branch:
http://svn.digium.com/view/zaptel/team/mattf/zaptel-1.4-stackcleanup/

Or with a kernel that does not have 4K stacks enabled?  You can check if your installed kernel does with the following command.

$ cat /boot/config-`uname -r` | grep 4K
# CONFIG_4KSTACKS is not set

Cheers,
Shaun