[asterisk-bugs] [JIRA] (ASTERISK-29429) asterisk deadlock issue

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-29429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp closed ASTERISK-29429.
-------------------------------------

    Resolution: Suspended

You can try finding help elsewhere, but this is an ancient version of Asterisk 13 and is not supported. It's entirely possible it's been fixed, and it is unlikely anyone will spend the time investigating it.

> asterisk deadlock issue
> -----------------------
>
>                 Key: ASTERISK-29429
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29429
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 13.18.2
>         Environment: openwrt
>            Reporter: priya
>            Severity: Major
>
> + We are facing asterisk deadlock issue everyday with call load of 32 channel at a time.
> + Can Dial plan handling also create deadlock issue.
> +  We need some guidance only which part of code or Dial Plan we can check,
>  i am going to attach "core show lock" output. 
> =======================================================================
> === 13.18.2
> === Currently Held Locks
> =======================================================================
> ===
> === <pending> <lock#> (<file>): <lock type> <line num> <function> <lock name> <lock addr> (times locked)
> ===
> === Thread ID: 0x76524d2c LWP:350 (do_devstate_changes  started at [  646] devicestate.c ast_device_state_engine_init())
> === ---> Lock #0 (main.c): RDLOCK 1113 find_device_ex &(&state->devices)->lock 0x5d20f8 (1)
> === ---> Waiting for Lock #1 (main.c): MUTEX 1116 find_device_ex &pvt->lock 0x659104 (1)
> === --- ---> Locked Here: main.c line 514 (call_monitor)
> === -------------------------------------------------------------------
> ===
> === Thread ID: 0x768a6d2c LWP:1427 (thread_discovery started at [  913] chan_dongle.c discovery_restart())
> === ---> Lock #0 (main.c): MUTEX 514 call_monitor &pvt->lock 0x659104 (1)
> === ---> Waiting for Lock #1 (channel.c): MUTEX 1080 __ast_queue_frame chan 0x712fa0 (1)
> === --- ---> Locked Here: channel.c line 2718 (ast_hangup)
> === -------------------------------------------------------------------
> === -------------------------------------------------------------------
> ===
> === Thread ID: 0x76790d2c LWP:19943 (pbx_thread           started at [ 4634] pbx.c ast_pbx_start())
> === ---> Lock #0 (channel.c): MUTEX 2718 ast_hangup chan 0x712fa0 (1)
> === ---> Waiting for Lock #1 (channel.c): MUTEX 408 channel_hangup &pvt->lock 0x659104 (1)
> === --- ---> Locked Here: main.c line 514 (call_monitor)
> === -------------------------------------------------------------------
> ===
> === Thread ID: 0x744a7d2c LWP:28095 (netconsole           started at [ 1739] asterisk.c listener())
> === ---> Lock #0 (cli.c): RDLOCK 76 cli_show_devices &(&gpublic->devices)->lock 0x5d20f8 (1)
> === ---> Waiting for Lock #1 (cli.c): MUTEX 79 cli_show_devices &pvt->lock 0x659104 (1)
> === --- ---> Locked Here: main.c line 514 (call_monitor)
> === -------------------------------------------------------------------
> ===
> === Thread ID: 0x744e5d2c LWP:28218 (pbx_thread           started at [ 4634] pbx.c ast_pbx_start())
> === ---> Lock #0 (main.c): RDLOCK 1164 find_device_by_resource_ex &(&state->devices)->lock 0x5d20f8 (1)
> === ---> Waiting for Lock #1 (main.c): MUTEX 1201 find_device_by_resource_ex &pvt->lock 0x659104 (1)
> === --- ---> Locked Here: main.c line 514 (call_monitor)
> === -------------------------------------------------------------------
> ===
> === Thread ID: 0x7442bd2c LWP:28406 (pbx_thread           started at [ 4634] pbx.c ast_pbx_start())
> === ---> Lock #0 (main.c): RDLOCK 1164 find_device_by_resource_ex &(&state->devices)->lock 0x5d20f8 (1)
> === ---> Waiting for Lock #1 (main.c): MUTEX 1201 find_device_by_resource_ex &pvt->lock 0x659104 (1)



--
This message was sent by Atlassian JIRA
(v6.2#6252)