#4927 NORM Future : NetworkManager overrides iwpriv command

[Zarro Boogs per Child]

#4927: NetworkManager overrides iwpriv command
-----------------------+----------------------------------------------------
  Reporter:  carrano   |       Owner:  mbletsas      
      Type:  defect    |      Status:  new           
  Priority:  normal    |   Milestone:  Future Release
 Component:  wireless  |     Version:                
Resolution:            |    Keywords:  beacon        
  Verified:  0         |  
-----------------------+----------------------------------------------------
Changes (by dcbw):

  * owner:  dcbw => mbletsas
  * component:  network manager => wireless


Comment:

 I'd suggest putting some debugging info into the driver to report back
 what values are actually returned from the firmware.  The driver does
 _not_ store the requested beacon interval internally for long, any time
 you execute a get-beacon it overwrites the internal value with the value
 the firmware returns.  So it may be that the firmware isn't keeping the
 right value around either.

 Furthermore, the value is sent to the firmware during adhoc association,
 so any time the association happens the value may change.  You should put
 a debug print in the driver where the driver sends the beacon_period to
 the firmware and see what that value is, and also a debug print when the
 value gets read from the firmware.

 Basically, NM never touches this value.  It doesn't matter what results
 happen when NM is running and when it's not, because NM isn't the problem.
 It only makes the problem happen more often.

 Whatever the driver or firmware is doing is somehow overwriting the beacon
 period value as a result of other operations in the driver or firmware.
 The value returned from iwpriv _always_ is what the firmware reports, and
 the firmware is only ever told what the beacon period is through (a) the
 iwpriv command, and (b) when starting an adhoc network.  Somebody needs to
 put more debugging info into the driver to trace down the driver/firmware
 interaction here.

-- 
Ticket URL: <http://dev.laptop.org/ticket/4927#comment:5>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system