Comment 1 for bug 43661

I can confirm this on an Intel dual core Pentium. I synchronized my clock with an NTP server on Friday, and started up NTP, which should have kept it in sync. I rebooted today (Sunday) to install a video card, and my clock is several hours wrong again - I suspect because it got set from the hwclock, and NTP won't correct it by such a big jump. I can't query the hwclock, though, with the same error as above:

$ sudo hwclock
select() to /dev/rtc to wait for clock tick timed out