On Wed, Jan 24, 2007 at 03:23:47PM +0100, Segher Boessenkool wrote:

quoted

I believed that the patch also worked on desktops. Of course, one
solution is to try to reset time from an NTP server on resume if you
are connected (if you are not, then an error of a fraction of a second
is less serious).

A fraction of a second is *never* serious, except with
broken apps ;-)

You've obviously never met people doing VLBI (Very Long Baseline 
Interferometry) ;-) 

Seriously, here we have a bunch of machines doing data acquisition
which are synchronized through timestamps taken at interrupt time.
They need an accuracy ot 5-10ms, which NTP easily provides (we have
our own redundant NTP servers connected to reference clocks: GPS
receivers and high precision clocks including an hydrogen maser).
Fortunately they never perform a suspend/resume cycle, because this
precision is not achievable even when trying to synchronize with the
second transition from the RTC.

If we did suspend the machines to save power, the only solution 
would be to tell NTP to synchronize with the master clock by 
stepping the time (not slewing) at resume time.

	Gabriel