#9565 BLOC 1.5-F11: system freeze under os33

[Zarro Boogs per Child]

#9565: system freeze under os33
------------------------------------+---------------------------------------
           Reporter:  pgf           |       Owner:               
               Type:  defect        |      Status:  new          
           Priority:  blocker       |   Milestone:  1.5-F11      
          Component:  not assigned  |     Version:  not specified
         Resolution:                |    Keywords:               
        Next_action:  never set     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by dsaxena):

 Replying to [comment:7 pgf]:
 >
 >
 > if i revert 3517a0561e15c68734bb9dc59405030f66450a23, i can no longer
 lock the system (either with or without X) with simple suspend/resume
 cycles.  (the two 'count' args to memcpy_fromio() seem odd.)

 Yep, looks like a buglet, I'm copying 0xff fromio but writing back 0x100
 toio.

 > i _can_ still lock the system as in #9581.

 > i _can_ still lock the system as in #9420.  the difference in that case
 (in my testing -- i can't really speak for cjb) is that the i reproduce
 #9420 with a loop:
 > {{{
 >     while :
 >     do
 >        echo mem > /sys/power/state
 >     done
 > }}}
 >
 > whereas this bug i reproduce by hand.   my suspicion lies in the fact
 that the console session is terminated and restarted across the
 suspend/resume.  the loop which reproduces #9420 attempts to keep running
 across the s/r cycles.  do we understand why the console session restarts?

 I've opened a separate bug for that issue, #9584

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