> the right thing to do is to fix timesync to notice
> such jumps and write them off as suspend/resume
> instead of assuming that the cpu has gotten *very* slow.

timesync still needs to set the correct time (a system which was
suspended for, say, 10 hours will live 10 hours in the past). perhaps
devcons.c:^writebintime should be the one to skip updating the clock
frequency?

Reply via email to