[asterisk-bugs] [JIRA] (ASTERISK-28605) chan_dahdi: Deadlock in Hangup Scenarios with concurrent command pri show span X

[Frederic LE FOLL (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249248#comment-249248 ] 

Frederic LE FOLL edited comment on ASTERISK-28605 at 1/7/20 2:20 AM:
---------------------------------------------------------------------

Test with Change Set https://gerrit.asterisk.org/c/asterisk/+/13527, Patch Set 1:

Conditions :
- TE820 with span 4 (euroisdn pri_net) connected to span 8 (euroisdn pri_cpe) with a crossover cable
- call generation with call files towards span 4, approx 10 calls/s
- call answer on span 8 with fast hangup (50ms)
- 'pri show span 4' every 1 s
See attached file 13527-PS1-test.txt for test conditions.

On one of our test servers, deadlock occurs after a variable time (generally 10mn). On another one (different hardware), no deadlock occurs.
Of course, the crossover cable creates a very artificial coincidence between outgoing and incoming calls.
See attached files 13527-PS1-bt.log for a backtrace of all threads after a deadlock, and 13527-PS1-deadlock.odg for a graphical representation of the deadlock.


was (Author: flefoll):
New test with Change Set https://gerrit.asterisk.org/c/asterisk/+/13527, Patch Set 1.

Conditions :
- TE820 with span 4 (euroisdn pri_net) connected to span 8 (euroisdn pri_cpe) with a crossover cable
- call generation with call files towards span 4, approx 10 calls/s
- call answer on span 8 with fast hangup (50ms)
- 'pri show span 4' every 1 s
See attached file 13527-PS1-test.txt for test conditions.

On one of our test servers, deadlock occurs after a variable time (generally 10mn). On another one (different hardware), no deadlock occurs.
Of course, the crossover cable creates a very artificial coincidence between outgoing and incoming calls.
See attached files 13527-PS1-bt.log for a backtrace of all threads after a deadlock, and 13527-PS1-deadlock.odg for a graphical representation of the deadlock.

> chan_dahdi: Deadlock in Hangup Scenarios with concurrent command pri show span X
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28605
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28605
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/General
>    Affects Versions: 16.6.0, 16.6.1
>         Environment: Asterisk 16.6 CentOs 6
>            Reporter: Dirk Wendland
>            Assignee: Unassigned
>         Attachments: 13527-PS1-bt.log, 13527-PS1-deadlock.odg, 13527-PS1-test.txt, core-asterisk-running-2019-11-08T11-08-15+0100-brief.txt, core-asterisk-running-2019-11-08T11-08-15+0100-full.txt, core-asterisk-running-2019-11-08T11-08-15+0100-locks.txt, core-asterisk-running-2019-11-08T11-08-15+0100-thread1.txt, currentLocks.txt
>
>
> We have a Szenario with an high Call Flow ( load tests ).
> Szenario:
> 4 S2M Ports => 60 channels go up in the same second 60 Channels hangs up in the same second
> Every few seconds we check the ISN Lines with the command:
> pri show span X
> After a few iterations asterisk will stop working.
> On the console we can fire up that command only one time then that command line interface hangs.
> localhost*CLI> pri show span 4
> Primary D-channel: 109
> Status: Up, Active
> The next ( Switchtype ) will not be printed
> -----------------------------
> We found the patch/task that created that issue.
> ASTERISK-28525
> If we revert that commit everything works fine.
> Greetings
> Dirk



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