#2253: AR5213 & AR5413/AR5414: 5GHz AP mode unusable/broken
---------------------------------------+------------------------------------
      Reporter:  [email protected]  |       Owner:                          
          Type:  defect                |      Status:  new                     
      Priority:  critical              |   Milestone:                          
     Component:  madwifi: driver       |     Version:  trunk                   
    Resolution:                        |    Keywords:  master mode 5ghz madwifi
Patch_attached:  0                     |     Pending:  0                       
---------------------------------------+------------------------------------
Comment (by [email protected]):

 I saw the same issue on my embedded target with AP mode in 5GHz, but not
 for station mode or in 2.4GHz.
   > HARWARE:
       Target CPU: AMCC PowerPC PPC405EP 333MHz[[BR]]

       Radio: miniPCI ZCOM AG-623C
   > SOFTWARE:
       Openwrt trunk rev.17239[[BR]]

       Madwifi trunk rev.4075[[BR]]

       Linux 2.6.26.8[[BR]]

   > CONFIGURE:
       AP mode, Channel 149, No security

 [[BR]]

 Two approaches I worked around the issue:
   > disable beacon calibration using parameter 'beacon_cal=0' to start
 ath_pci
 or
   > when madwifi is running,[[BR]]

     input 'echo 1 > /proc/sys/dev/wifi0/intmit',[[BR]]

     then  'echo 0 > /proc/sys/dev/wifi0/intmit'[[BR]]

     (it may needs to do several times)[[BR]]
 [[BR]]

 Suspect causing:
   With some investigation of source code, I suspect calling ath_reset in
 interrupt handler (ath_intr) causes the issue.
     1. ath_intr calls ath_beacon_send when receiving SWBA interrupt
     2. ath_beacon_send calls ath_calibration when beacon calibration is
 enabled and calibration timer is expired
     3. ath_calibration calls ath_reset
     4. ath_reset calls ath_startrecv
   I noticed that no SWBA interrupt comes again when the issue happened. An
 interesting thing is that the issue would not happen if I printk a long
 string (len>32) in ath_startrecv (between ath_hal_startpcurecv and
 ath_override_intmit_if_disabled). I have not got time to dig deeply.
 Hopefully, this would help others to continue to investigate.

-- 
Ticket URL: <http://madwifi-project.org/ticket/2253#comment:2>
madwifi-project.org <http://madwifi-project.org/>
Multiband Atheros Driver for Wireless Fidelity
------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to