venom@sns.it wrote:
> I just upgraded on a test pc to kernel 2.5.70.
> with this kernel the system clock has become e lot faster (the
> same happens with 2.5.69 too), so what the system thinks to be a second,
> is more or le 0,6 real seconds.
>
> setting HZ to 100 slows down a little, so a system second is almost 0,8
> real seconds.
>
> going back to 2.5.66 or 2.4.20 solves the problem.
Sorry for missing this earlier. This issue is being tracked in bug 827.
http://bugme.osdl.org/show_bug.cgi?id=827
The current workaround is booting w/ "clock=pit" but I just sent a patch to
Andrew requesting we disable the lost-ticks code until this is properly
fixed.
thanks
-john
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 23 2003 - 22:00:33 EST