On Jul 17, 2013, at 9:09 AM, Miroslav Lichvar <mlich...@redhat.com> wrote:
> On Wed, Jul 17, 2013 at 08:41:23AM -0600, Chris Murphy wrote: >> >> On Jul 17, 2013, at 8:09 AM, Miroslav Lichvar <mlich...@redhat.com> wrote: >> >>> It was fixed in kernel 3.10, which should be in f19 soon. >> >>> Which functionality exactly? Both ntpd and chronyd (in default >>> configuration) let the kernel sync the RTC. >> >> OK I just set the RTC clock wrong by two months, manually and then I've >> rebooted 3.10.0-1.fc20.x86_64 on Fedora 19. >> >> The system clock is updated by chrony, correctly. >> >> The RTC is not being updated. It still thinks it's May. > > You might need to wait a bit longer. It worked for me the last time I > tried, but it took almost 2 hours for the kernel to sync the RTC. From > the kernel code it seems the RTC update should happen quickly after > the unsynchronized flag in the kernel is cleared and then at most at > 11 minute intervals. Please file a new bug. It's been over 2 hours and the RTC is still wrong. Please let me know if you need additional information from what appears in the bug: https://bugzilla.redhat.com/show_bug.cgi?id=985522 Chris Murphy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
