[asterisk-bugs] [Zaptel 0014232]: [patch] Failed to initailize DAA, giving up...

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14232 
====================================================================== 
Reported By:                tallen8840
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   14232
Category:                   wcfxo
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     confirmed
Zaptel Version:              SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 4482 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-13 11:13 CST
Last Modified:              2009-02-24 07:04 CST
====================================================================== 
Summary:                    [patch] Failed to initailize DAA, giving up...
Description: 
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.


====================================================================== 

---------------------------------------------------------------------- 
 (0100610) explidous (reporter) - 2009-02-24 07:04
 http://bugs.digium.com/view.php?id=14232#c100610 
---------------------------------------------------------------------- 
I just tested this patch and it seems to correctly fix the issue on a
production system that had this problem on.
Works for 1.2 as well! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-24 07:04 explidous      Note Added: 0100610                          
======================================================================