#472: Device Driver Crashes, Kernel Panics and Locking Problems
-----------------------------------+----------------------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:  mrenzmann                   
        
          Type:  defect            |      Status:  assigned                     
       
      Priority:  major             |   Milestone:  version 0.9.0 - move to new 
codebase
     Component:  madwifi: driver   |     Version:  trunk                        
       
    Resolution:                    |    Keywords:                               
       
Patch_attached:  1                 |  
-----------------------------------+----------------------------------------
Changes (by [EMAIL PROTECTED]):

  * cc:  [EMAIL PROTECTED] => [EMAIL PROTECTED],[EMAIL PROTECTED]

Comment:

 I'm running an IA32 system with 2.6.16 and desktop (ie voluntary)
 preemption.

 I have found the changes in spin_locks-20050331.diff to eliminate the oops
 I was seeing when the interface is up - I have seen the AR5212 chip lockup
 and reset (below) a number of times, but the host system is rock-solid:

 {{{
 wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
 wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
 wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
 24Mbps 36Mbps 48Mbps 54Mbps
 wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
 wifi0: H/W encryption support: WEP AES AES_CCM TKIP
 wifi0: mac 10.5 phy 6.1 radio 6.3
 wifi0: Use hw queue 1 for WME_AC_BE traffic
 wifi0: Use hw queue 0 for WME_AC_BK traffic
 wifi0: Use hw queue 2 for WME_AC_VI traffic
 wifi0: Use hw queue 3 for WME_AC_VO traffic
 wifi0: Use hw queue 8 for CAB traffic
 wifi0: Use hw queue 9 for beacons
 wifi0: Atheros 5212: mem=0xdfae0000, irq=201
 wlan: mac acl policy registered
 wifi0: hardware error; reseting
 wifi0: hardware error; reseting
 wifi0: hardware error; reseting
 wifi0: hardware error; reseting
 wifi0: hardware error; reseting
 }}}

 My kernel has debug features enabled and I have a serial connection for
 harvesting a clean backtrace - I'll test for the bringup/teardown oops I
 was seeing in the unpatched code and post my results in the next day. Oh,
 I'll jackup the SSID broadcast rate to check for another race in the
 unpatched code too.

-- 
Ticket URL: <http://madwifi.org/ticket/472>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity

Reply via email to