Comment 28 for bug 1333569

Revision history for this message
Colin Ian King (colin-king) wrote :

Just a note:

1. The utopic version of hwclock has a 10 second timeout but does not report a timeout error (which is misleading)
2. The trusty version reports the timeout, but prints the errno from the previous system call, so the error message is misleading
3. When I get hwclock time-out the following kernel message appears:

   hpet1: lost 20 rtc interrupts

4. I've tested this back to 3.12 and we see the same issue there too.