[asterisk-bugs] [JIRA] (ASTERISK-20625) asterisk crashed after warning Can't fix up channel

Matt Jordan (JIRA) noreply at issues.asterisk.org
Tue Oct 30 06:27:18 CDT 2012


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

Matt Jordan closed ASTERISK-20625.
----------------------------------

    Resolution: Suspended

Additionally, questions asking for information are best asked on either the asterisk-users mailing list or the #asterisk IRC channel.
                
> asterisk crashed after warning Can't fix up channel 
> ----------------------------------------------------
>
>                 Key: ASTERISK-20625
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20625
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: SVN
>         Environment: Asterisk 1.6.2.12
> libpri 1.4.11.4-1_centos5
> dahdi linux-2.4.0-1_centos5
> We are using two Digium, Inc. Wildcard TE420P quad-span T1/E1/J1 card 3.3V (PCI-Express) (rev 02)
>            Reporter: arjan kroon
>
> Hello,
> I have a problem.
> One every couple of months my asterisk system crashes with a segmentation fault.
> kernel: asterisk[20527]: segfault at 0000080000000008 rip 00002aaac952d8f2 rsp 0000000040edb910 error 4
> (This is in /var/log/messages)
> If I look at the same timestamp in the warning log file of asterisk (/var/log/asterisk/warning),
> I see that the are warning about fix up channel:
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 1 to 2 because 2 is already in use
> WARNING[24000] chan_dahdi.c: Ringing requested on channel 0/2 not in use on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 5 to 6 because 6 is already in use
> WARNING[24000] chan_dahdi.c: Ringing requested on channel 0/6 not in use on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 6 to 8 because 8 is already in use
> WARNING[24000] chan_dahdi.c: Ringing requested on channel 0/8 not in use on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 3 to 4 because 4 is already in use
> WARNING[24000] chan_dahdi.c: Hangup REQ on bad channel 0/4 on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 2 to 3 because 3 is already in use
> WARNING[24000] chan_dahdi.c: Hangup REQ on bad channel 0/3 on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 4 to 5 because 5 is already in use
> WARNING[24000] chan_dahdi.c: Hangup REQ on bad channel 0/5 on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 1 to 2 because 2 is already in use
> WARNING[24000] chan_dahdi.c: Answer requested on channel 0/2 not in use on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 5 to 6 because 6 is already in use
> WARNING[24000] chan_dahdi.c: Answer requested on channel 0/6 not in use on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 1 to 2 because 2 is already in use
> WARNING[24000] chan_dahdi.c: Hangup on bad channel 0/2 on span 1
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 2 to 3 because 3 is already in use
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 3 to 4 because 4 is already in use
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 4 to 5 because 5 is already in use
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 5 to 6 because 6 is already in use
> WARNING[24000] chan_dahdi.c: Hangup on bad channel 0/6 on span 1
> WARNING[24000] chan_dahdi.c: Whoa, there's no owner, and we're having to fix up channel 6 to channel 8
> WARNING[24000] chan_dahdi.c: Whoa, there's no owner, and we're having to fix up channel 1 to channel 2
> WARNING[24000] chan_dahdi.c: Can't fix up channel from 5 to 6 because 6 is already in use
> Does anybody know what these messages mean?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list