#11600 BLOC 1.75-so: Hang w. OS26

[Zarro Boogs per Child]

#11600: Hang w. OS26
--------------------------------+-------------------------------------------
           Reporter:  wad       |       Owner:                                   
               Type:  defect    |      Status:  new                              
           Priority:  blocker   |   Milestone:  1.75-software                    
          Component:  kernel    |     Version:  Development build as of this date
         Resolution:            |    Keywords:  XO-1.75, suspend                 
        Next_action:  diagnose  |    Verified:  0                                
Deployment_affected:            |   Blockedby:                                   
           Blocking:            |  
--------------------------------+-------------------------------------------

Comment(by greenfeld):

 I agree it doesn't seem necessary to use the camera to cause a hang, but
 it might be an aggravating factor.

  * Using a script to running a 5 second on/off dortc loop after launching
 an X Window for "gst-launch v4l2src ! xvimagesink &" in the foreground
 hung both times I ran it within the first hour after starting the test.
 The hang occurred with the power LED on but the camera LED off.  I did not
 enable serial, watchdog, or blacklisting any modules while doing this.
 The configuration should have been like os28 freshly imaged.

  * Running the camera for a few hours with the above command without a
 dortc loop did not cause a hang, or visibly cause the XO to suspend.

  * Running the gst-launch command for 5 seconds and then killing it off
 for 5 seconds did not cause a hang when I tested it for an hour, but
 powerd didn't see this as enough activity and put the XO to sleep.  Given
 we watch camera activity now this might be a bug on its own, but I used
 olpc-nosleep to workaround it.

  * Running the same dortc loop without the camera running hung once so
 far, but took a few hours to reach that point.    The dortc-loop test hung
 shortly after printing for a few cycles that the rtc device was already in
 use.  I am now using olpc-nosleep to verify that powerd doesn't kick in
 and conflict with the script, but what else uses the rtc device?

 All scripts were run from the Terminal activity in Sugar as the root user
 on a B1 HS unit.  The XO was then left untouched since switching views in
 Sugar risked putting sugar-session into a CPU loop until the gst-launch
 window was closed (which probably should be a ticket on its own).

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