#8592 HIGH 8.2.1: bug or feature? XO hogs CPU trying to find Mesh while already connected to Access Point

[Zarro Boogs per Child]

#8592: bug or feature?  XO hogs CPU trying to find Mesh while already connected to
Access Point
--------------------------+-------------------------------------------------
   Reporter:  thomaswamm  |       Owner:  marco                            
       Type:  defect      |      Status:  new                              
   Priority:  high        |   Milestone:  8.2.1                            
  Component:  sugar       |     Version:  Development build as of this date
 Resolution:              |    Keywords:  relnote                          
Next_action:  diagnose    |    Verified:  0                                
  Blockedby:  4074, 6944  |    Blocking:  8098                             
--------------------------+-------------------------------------------------

Comment(by mtd):

 Replying to [comment:12 gregorio]:
 > Hi Guys,
 >
 > Is this closed in 765[?]

 It's not closed in 765.

 > ...does it need to go in the release notes?

 Yes.  But as the patch suggester and general person-without-
 responsibility, can we just fix it?  The patch addresses one of the most
 common symptoms of the problem (as the full problem is certainly beyond
 the scope of 8.2.0).

 > If we need a release note, please me write a short user friendly blurb
 (e.g. when the XO wakes from being suspended it will search for a Mesh
 connection (e.g. another XO) if that is not found it will try to connect
 to the last AP that was in use. Please wait until it tries to connect to
 that AP manually connecting to an AP in the Neighborhood view). Sorry for
 the nested "e.g."s, hopefully you get the idea.

 I get the idea, but who gets to write the blurb?

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