[asterisk-bugs] [JIRA] (ZAP-354) [patch] Failed to initailize DAA, giving up...

Jonah (JIRA) noreply at issues.asterisk.org
Thu Apr 14 08:48:56 CDT 2016


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

Jonah commented on ZAP-354:
---------------------------

Hi can we please re-open this ticket as the card seems to be no longer supported with the latest version of Dahdi:

[761493.393658] FXO PCI Master abort
[761493.393667] FXO PCI Master abort
[761493.393673] NOTICE-wcfxo: WCFXO/0: Unknown DAA chip revision: REVB=0
[761493.393675] Failed to initailize DAA, giving up...
[761493.393676] FXO PCI Master abort
[761493.393686] FXO PCI Master abort
[761493.393861] wcfxo: probe of 0000:04:00.0 failed with error -5
[761493.401507] dahdi_dummy: Trying to load High Resolution Timer
[761493.401509] dahdi_dummy: Initialized High Resolution Timer
[761493.401510] dahdi_dummy: Starting High Resolution Timer
[761493.401511] dahdi_dummy: High Resolution Timer started, good to go
root at svr:/home/jonah# 

> [patch] Failed to initailize DAA, giving up...
> ----------------------------------------------
>
>                 Key: ZAP-354
>                 URL: https://issues.asterisk.org/jira/browse/ZAP-354
>             Project: Zaptel
>          Issue Type: Bug
>          Components: wcfxo
>            Reporter: tim allen
>         Attachments: wcfxo.diff
>
>
> NOTICE-wcfxo: WCFXO/0: Unknown DAA chip revision: REVB=0
> Failed to initailize DAA, giving up...
> wcfxo: probe of xxxx:xx:xx.x failed with error -5
> The X100p and clones will sometimes work and sometimes not depending on weather the DAA powers up in running state- this seems to be related to the power supply. This problem is caused by the driver not reseting the DAA and may be the source of a great many intermittent problems with this card.
> ****** ADDITIONAL INFORMATION ******
> I initially thought this was a hardware bug (eg crappy card); however, I reverse engineered the card and found that the DAA's reset pin is connected to the PCI chip's AUX5 pin not, as one might expect the RESET# pin.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list