#11544 HIGH Not Tri: Completed runin logs not reliably compiled/synced prior to reboot

[Zarro Boogs per Child]

#11544: Completed runin logs not reliably compiled/synced prior to reboot
-----------------------------------+----------------------------------------
 Reporter:  greenfeld              |                 Owner:                                   
     Type:  defect                 |                Status:  new                              
 Priority:  high                   |             Milestone:  Not Triaged                      
Component:  manufacturing process  |               Version:  Development build as of this date
 Keywords:                         |           Next_action:  diagnose                         
 Verified:  0                      |   Deployment_affected:                                   
Blockedby:                         |              Blocking:                                   
-----------------------------------+----------------------------------------
 Four C1's here successfully seemed to complete the 24-hour runin on their
 first try using all default settings (with TS=RUNIN).  All of them were
 seen by /runin/log directory timestamps to reboot and restart runin a
 minute after

 But of these, only two had created a .tar.gz file rolling up their log
 data, and had data at the end of run.log implying the test was complete.
 The other two failed to create .tar.gz files with a message at the end of
 kern.log implying the file system was about to be synced.

 Since then, a fifth C1 has finished 24-hour runin on its second try, and
 successfully complied its logs.

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