On 10/09/2014 11:05 AM, Noé RUBINSTEIN wrote: >> Are you sure that drift factor (re)calculation does not happen if >> writing the Hardware Clock fails? I just had a quick look at the >> code and it seem that we do not test to see if write fails. So >> (re)calculation might work as is? > > It does not seem to work the obvious way: > > [root@localhost ~]# date > Thu Oct 9 14:56:30 UTC 2014 > [root@localhost ~]# hwclock --systohc --update > hwclock: ioctl(RTC_SET_TIME) to /dev/rtc to set the time failed.: Invalid argument > [root@localhost ~]# hwclock --get > Thu Jan 8 05:12:51 1970 .543449 seconds You cannot initialize the Hardware Clock at all? Not even through the BIOS? If the Hardware Clock cannot be set at all, then my patch will not help you. Sorry if I misunderstood. What machine are you using? -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
