#10366 NORM Not Tri: Possible Networkmanager/S3 sleep race condition and/or other issue(s)

[Zarro Boogs per Child]

#10366: Possible Networkmanager/S3 sleep race condition and/or other issue(s)
-----------------------------+----------------------------------------------
 Reporter:  greenfeld        |                 Owner:  dsd          
     Type:  defect           |                Status:  new          
 Priority:  normal           |             Milestone:  Not Triaged  
Component:  network manager  |               Version:  not specified
 Keywords:                   |           Next_action:  never set    
 Verified:  0                |   Deployment_affected:               
Blockedby:                   |              Blocking:               
-----------------------------+----------------------------------------------
 This likely needs to be triaged, as I probably keep guessing wrong as to
 why eth0 loses track of its ESSID/IP Address information.   Again this is
 with the RPMs from #9845 installed, but at first glance the problem
 appears to be below the Sugar layer.

 My production XO-1.5 laptops occasionally lose track of what to connect
 to, even when they are supposed to default to an Adhoc network with the
 #9845 changes.  So one time when I cleared the Network History from Sugar,
 clicked the checkmark to close the Network control panel, and pressed
 Ctrl-Alt-Esc to restart X & Sugar, I noticed that the #9845 change did not
 reconnect to the Adhoc #1 network by default like it should.  So I enabled
 sugar & presence server debugging, and kept clearing the
 history/restarting X a few times on the laptop showing the issue (as well
 as one which wasn't showing it) trying to get the problem to reproduce
 and/or go away.  {It happened twice on the broken one and persisted for a
 while each time; never on the non-broken XO 1.5, although the latter has
 shown this behavior before.}

 Martin took an initial look, and although it may not relate to the above,
 the area around "Sep 15 17:14:52" in var/log/messages looked interesting.
 There, the laptop decided to sleep in the middle of NetworkManager setting
 up a connection.  This resulted in NetworkManager deciding that the
 connection was invalid, and not trying to restore it.

 Attached please find the system/sugar/powersave log files from the system
 which lost track of connections.  I turned on verbose sugar debugging
 after the first time the issue was spotted.

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