#12622 NORM Not Tri: hwclock fails in select

[Zarro Boogs per Child]

#12622: hwclock fails in select
------------------------------------+---------------------------------------
           Reporter:  Quozl         |       Owner:  rsmith       
               Type:  defect        |      Status:  closed       
           Priority:  normal        |   Milestone:  Not Triaged  
          Component:  not assigned  |     Version:  not specified
         Resolution:  fixed         |    Keywords:               
        Next_action:  no action     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by dsd):

 This is not an error, it is just a warning. The RTC does get set as
 requested immediately after that warning is printed. Admittedly it is
 confusing, I will ask upstream what can be done.

 What happens here is that it first tries to wait for a RTC clock tick,
 before reading the time, and that time is used to calculate/maintain the
 "adjtime" time drift stuff (see hwclock man page).

 In this case we do not care about adjtime so you could just run: hwclock
 --systohc --noadjfile --utc

 That avoids the confusing error (since it causes hwclock just to go
 straight and write the new time), and is the kind of invocation we would
 put in a script.

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