#11400 BLOC 1.75-so: Date resets to 1970 each boot

[Zarro Boogs per Child]

#11400: Date resets to 1970 each boot
---------------------------------+------------------------------------------
           Reporter:  cjb        |       Owner:  dilinger     
               Type:  defect     |      Status:  new          
           Priority:  blocker    |   Milestone:  1.75-software
          Component:  kernel     |     Version:  not specified
         Resolution:             |    Keywords:               
        Next_action:  never set  |    Verified:  0            
Deployment_affected:             |   Blockedby:               
           Blocking:             |  
---------------------------------+------------------------------------------

Comment(by martin.langhoff):

 CONFIG_RTC_HCTOSYS_DEVICE gets compiled into drivers/rtc/hctosys.o , so a
 clean compile makes CONFIG_RTC_HCTOSYS_DEVICE="rtc1" work for me at the
 kernel leve.

 It works in the sense that dmesg shows that the system clock was set right
 at ~4s into the boot process. So that's a step forward.

 By the time I'm logged it, however, we're back to 1970.

 Now we have a mystery

  * Grepping through init scripts, I only see halt and reboot calling it on
 the way down, performing a pointless sync in the wrong direction (system
 clock to the volatile rtc0).
  * Move /sbin/hwclock aside, the problem is gone.
  * Replace /sbin/hwclock with a shellscript that captures the caller, the
 shellscript seems to only log callers on the way down (reboot, halt
 initscripts).

 Perhaps upstart is calling it with / mounted ro, preventing the logging.
 That's my next stop.

 Along the way, I did find that udev cannot change rtc devnode names nor
 attributes. Device name changes are for network devices only.

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