#11738 HIGH 1.75-fi: Runin discharge battery stat not cleared when XO-1.75s are powered off

Zarro Boogs per Child bugtracker at laptop.org
Wed Mar 28 17:22:14 EDT 2012


#11738: Runin discharge battery stat not cleared when XO-1.75s are powered off
-------------------------------------------+--------------------------------
           Reporter:  greenfeld            |       Owner:  rsmith                           
               Type:  defect               |      Status:  assigned                         
           Priority:  high                 |   Milestone:  1.75-firmware                    
          Component:  embedded controller  |     Version:  Development build as of this date
         Resolution:                       |    Keywords:                                   
        Next_action:  code                 |    Verified:  0                                
Deployment_affected:                       |   Blockedby:                                   
           Blocking:                       |  
-------------------------------------------+--------------------------------

Comment(by rsmith):

 Replying to [comment:3 greenfeld]:
 > I am slightly confused, as I have not run any of the affected XO-1.75's
 in RUNIN for the past few weeks.

 Exactly. And unless you have removed the battery without external power
 connected the EC has been sitting there drawing 6.5mA. It will take 20+
 days for the battery to completely run down enough to reset the EC.

 > Are you modifying the EC to disable battery debug output when powered
 off, disable the RUNIN discharge test (which does not seem to be the issue
 as I would have noticed XO's not charging), or both?

 I'm changing the EC to make sure the runin discharge flag is cleared if
 you power the laptop off.  Its not possible to be in RUNIN when the laptop
 is powered off so having it set is invalid.  If the EC thinks runin
 discharge is active then it won't sleep.

 > I thought those were two separate commands to the EC.

 Debug output is orthogonal to going into stop mode.  It looks similar
 because when you turn on the same debugging with 'b3' that command also
 sets a "no stop mode" flag but that is not the same as the runin discharge
 flag. There are multiple flags the EC looks at to decide if it can go into
 stop mode.

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


More information about the Bugs mailing list