[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:                     needs license
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-01-13 17:20 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.


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

---------------------------------------------------------------------- 
 (0097679) tallen8840 (reporter) - 2009-01-13 17:20
 http://bugs.digium.com/view.php?id=14232#c97679 
---------------------------------------------------------------------- 
...
kernel: [   62.333336] Uhhuh. NMI received for unknown reason 21 on CPU
0.
kernel: [   62.333336] Do you have a strange power saving mode enabled?
kernel: [   62.333336] Dazed and confused, but trying to continue
...

I think I did the right thing (reseting the DAA) but in the wrong place.
The module now generates an NMI (but no crash) the first time it loads. I
think I'm causing DMA to start too soon. Can anyone confirm seeing an NMI
the the first time (after a reboot) they load the patched module? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-13 17:20 tallen8840     Note Added: 0097679                          
======================================================================