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

[Shaun Ruffell (JIRA)]

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

Shaun Ruffell closed DAHLIN-268.
--------------------------------

    Resolution: Suspended

With the changes in DAHDI-Linux 2.9.2, I would be surprised if this is still an issue. Specifically, the wctc4xxp driver will now reset the firmware either immediately if a critical alert is received, or when all channels are closed if a non-critical alert is received.

> 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, kern.log
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)