[asterisk-bugs] [JIRA] (DAHLIN-268) Flag "stuck" channels as in-use and optionally reset firmware.

[Russ Meyerriecks (JIRA)]

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

Russ Meyerriecks commented on DAHLIN-268:
-----------------------------------------

So the 0003 patch I just attached attempts to flag the "wedged" echo can timeslots so dahdi will no longer attempt to use them. This is sort of a workaround instead of a permanent fix, since the wedged timeslot will not longer be useful until the driver is reloaded, but it should theoretically keep dahdi from becoming hung up.
                
> Flag "stuck" channels as in-use and optionally reset firmware.
> --------------------------------------------------------------
>
>                 Key: DAHLIN-268
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-268
>             Project: DAHDI-Linux
>          Issue Type: New Feature
>      Security Level: None
>          Components: wctc4xxp
>    Affects Versions: 2.5.0.2
>            Reporter: Shaun Ruffell
>            Assignee: Russ Meyerriecks
>         Attachments: 0001-wctc4xxp-Fail-gracefully-on-Failed-to-create-channel.patch, 0003-wctc4xxp-Fail-gracefully-on-Failed-to-create-channel.patch
>
>
> seanbright reported on IRC that the wctc4xxp driver can sometimes report:
> {noformat}
> [3133994.496258] wctc4xxp 0000:07:08.0: Failed to create channel in timeslot 52.  Response from DTE was (ffbd).
> {noformat}
> When this happens, the card typically has that channel stuck and will return an error message on any new channel creation until the driver is reloaded. While unclear how the firmware gets into this state the driver could be more proactive about minimizing the impact of this on a running system by marking channels as in use and not trying them until after a reload, and optionally reloading after the channel use count is at 0 for some specific amount of time.

--
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