[asterisk-bugs] [Asterisk 0018811]: [patch] Seems Like ast_read / timerfd_timer_ack Causes lockups and resource drain
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed May 11 08:52:44 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18811
======================================================================
Reported By: irroot
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18811
Category: Resources/res_timing_timerfd
Reproducibility: random
Severity: major
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.2.17-rc2
JIRA: SWP-3126
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-02-15 02:31 CST
Last Modified: 2011-05-11 08:52 CDT
======================================================================
Summary: [patch] Seems Like ast_read / timerfd_timer_ack
Causes lockups and resource drain
Description:
The system locks up eventually and as it is holding a channel lock things
like pickup and walking channels locked will cause a deadlock ...
i have reverted to dahdi timer that is not prone to this problem.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0018791 [patch] Deadlock sip_read check_rtp_tim...
======================================================================
----------------------------------------------------------------------
(0134785) zvision (reporter) - 2011-05-11 08:52
https://issues.asterisk.org/view.php?id=18811#c134785
----------------------------------------------------------------------
I have the same issue with the current Asterisk 1.6.2 SVN version.
Launching MeetMe with a few hundreds users at a single conference almost
always leaves a few deadlocked MeetMe users (usually 1-4). Attaching GDB to
a running Asterisk show deadlocked MeetMe threads waiting in the
timerfd_timer_ack read call. The dealock occurs when these users are about
to hang up (VoIP channels are hung up correctly, only MeetMe users in a
conference are left deadlocked).
Issue History
Date Modified Username Field Change
======================================================================
2011-05-11 08:52 zvision Note Added: 0134785
======================================================================
More information about the asterisk-bugs
mailing list