|Summary:||ASTERISK-01872: Asterisk deadlocks - gdb output attached|
|Date Opened:||2004-06-23 09:28:32||Date Closed:||2004-09-25 02:40:24|
|Environment:||Attachments:||( 0) mastdead230604.txt|
Asterisk CVS head 22/06/04
|Comments:||By: Mark Spencer (markster) 2004-06-23 13:59:12|
I found one minor issue in which lock was not held during answer, although I doubt this is relevant to your deadlock (although it may relate to a different bug in the tracker). As usual, the trace is insufficient. I've have provided Tan with the instructions for contacting me so that I can perform a meaningful analysis of the deadlock, and continuing to place these deadlocks with (in this case) generally useless backtraces is simply a waste of both your time and mine.
In order to provide a timely response and fix, please follow up *directly* and provide me with access to the machine when it is in the deadlocked situation. Again, to reitterate an additional time, I will need root access to the machine *when it is stuck in that state* and absolutely nothing short of that will do. It may be useful to setup a "hot spare" that you can put into service so that the state of the stuck machine is not lost.