|Summary:||ASTERISK-17968: chan_dahdi - core dump at Asterisk startup if red alarm on PRI (1.8 SVN)|
|Reporter:||Douglas Jensen (djensen99)||Labels:|
|Date Opened:||2011-06-06 12:07:49||Date Closed:||2011-06-13 12:30:49|
|Versions:||220.127.116.11 Potential Blocker||Frequency of|
|Environment:||Centos 5.6, kernel 2.6.18-164.15.1-el5, DAHDI 18.104.22.168+2.4.1, LibPRI 22.214.171.124||Attachments:||( 0) gdb.txt|
|Description:||I checked out 1.8 r312575 from SVN in order to test the fixes for PRI channel switching causing lockups on two systems which use DAHDI. Both systems utilize TE412p and TC400b cards and have all four PRI spans configured as 5ess/pri_net. The only difference is that one system has all four spans in use and one system currently only has two spans in use. On the system with all four PRI spans in use, there were no issues. On the system with only two PRI spans in use, asterisk core dumped immediately after initializing the two connected spans. Changing /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf to comment out the two unused spans on the second system caused asterisk to start up normally.|
I also reproduced this on the first system by unplugging a PRI and restarting asterisk - same behavior.
|Comments:||By: Douglas Jensen (djensen99) 2011-06-09 22:32:10.137-0500|
Unoptimized backtrace from crash.
By: Richard Mudgett (rmudgett) 2011-06-10 18:14:42.972-0500
This is already fixed:
r312949 | rmudgett | 2011-04-05 13:45:24 -0500 (Tue, 05 Apr 2011) | 6 lines
Crash if ISDN span layer 1 is down on initial load.
Regression from -r312575 B channel shifting during negotiation.
* Also combine updating the alarm flag with clearing the resetting flag.
By: Douglas Jensen (djensen99) 2011-06-10 21:02:52.841-0500
Thanks! Will check out the newer subversion.