#9895 NORM 1.5-sof: Should we inhibit suspend when we're connected to an ad-hoc network?

[Zarro Boogs per Child]

#9895: Should we inhibit suspend when we're connected to an ad-hoc network?
-------------------------------------------+--------------------------------
           Reporter:  cjb                  |       Owner:  cjb                              
               Type:  defect               |      Status:  new                              
           Priority:  normal               |   Milestone:  1.5-software-update              
          Component:  power manager (OHM)  |     Version:  Development build as of this date
         Resolution:                       |    Keywords:                                   
        Next_action:  communicate          |    Verified:  0                                
Deployment_affected:                       |   Blockedby:                                   
           Blocking:                       |  
-------------------------------------------+--------------------------------

Comment(by Quozl):

 Tested with os62 wireless firmware 9.70.7.p0 on three XO-1.5 units.

 == Test Setup ==

  * disable suspend,
  * on unit GOLF, used ''Create new wireless network'',
  * waited for the network to appear on the other units, then joined the
 network,
  * identified all IP addresses,
  * began a ping from unit HOTEL to unit INDIGO,
  * began a ping from unit GOLF to unit INDIGO,
  * observed normal ping output,

 == Test Loss of Master by Attenuation ==

  * moved unit GOLF into 2GHz faraday cage (inside a microwave oven 6m away
 through a steel wall),
  * observed ping output on unit GOLF had ceased,
  * observed ping output on unit HOTEL had paused very briefly (a 200ms
 instead of 3ms result shown), but continued.

 Conclusion: the network survives the loss of master by attenuation of
 signal.

 == Test of a prior master rejoining network ==
  * moved unit GOLF back to desk,
  * observed ping output on unit GOLF started immediately the faraday cage
 was opened,
  * observed no interruption to the ping on unit HOTEL.

 Conclusion: the network survives joining by a previous master.

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