#10757 NORM Not Tri: XO-1.5 system time failed to adjust forward by rtcwake period

[Zarro Boogs per Child]

#10757: XO-1.5 system time failed to adjust forward by rtcwake period
------------------------------------+---------------------------------------
           Reporter:  Quozl         |       Owner:               
               Type:  defect        |      Status:  new          
           Priority:  normal        |   Milestone:  Not Triaged  
          Component:  not assigned  |     Version:  not specified
         Resolution:                |    Keywords:               
        Next_action:  never set     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by Quozl):

 Reproduced on unit ''quozl-i'', SHC937010AA, an XO-1.5 B2, which had been
 synchronised using ''ntpdate'', then ''hwclock --systohc --utc'', then
 ''poweroff''.  Roughly 12 hours without main battery or external DC
 elapsed.  After reboot the following output was captured:

 {{{
 # A=$(date +%s)
 # echo A=${A}
 A=1300228749
 # rtcwake -m mem -s 20 -u
 rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Mar 15 22:39:30 2011
 # B=$(date +%s)
 # echo B=${B}
 B=1300228753
 # echo C=$(($B-$A))
 C=4
 # sleep 30
 # hwclock --utc
 Tue Mar 15 22:40:01 2011  -0.427068 seconds
 # ntpdate -d pool.ntp.org
 15 Mar 22:39:44 ntpdate[2897]: ntpdate 4.2.4p7 at 1.1607-o Wed Dec  9
 11:54:06 UTC 2009 (1)
 ...
 15 Mar 22:39:48 ntpdate[2897]: step time server 121.0.0.42 offset
 16.045683 sec
 }}}

 After a ''poweroff'' and reboot the same symptom persists.

 10.1.3 os860 2.6.31_xo1.5-20101216.1243.1.olpc.741a3e67d9e7bb8

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