Messages in this thread | | | Subject | Re: [PATCH 0/13] Time: Generic Timeofday Subsystem (v B10) | From | john stultz <> | Date | Mon, 14 Nov 2005 13:38:45 -0800 |
| |
On Mon, 2005-11-14 at 14:22 -0700, Frank Sorenson wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > john stultz wrote: > > All, > > I had hoped to submit this to -mm today, but since Ingo pointed > > out an issue in the __delay code, I'm going to wait a week so the new fix > > can be better tested. > > I replaced the TOD parts of the kthrt patchset with TOD B10. It seems > there is something wrong with 'c3tsc' and 'pit', though. > > c3tsc appears to run fast: > 14 Nov 12:02:13 offset: -0.00247 drift: -2502.0 ppm > 14 Nov 12:03:14 offset: -0.145203 drift: -2342.5 ppm > 14 Nov 12:04:14 offset: -0.329381 drift: -2700.10655738 ppm > 14 Nov 12:05:14 offset: -0.532767 drift: -2927.46703297 ppm > 14 Nov 12:06:15 offset: -0.638096 drift: -2626.04115226 ppm
Hmm... Not sure if this is mis-calibration or just bad-interaction w/ kthrt. Mind sending a dmesg to me?
> and 'pit' seems to produce errors (system will not switch from pit to > another clocksource anymore):
Do the TOD patches have this issue by themselves, or is this only with kthrt? I know I had some issues with non-continuous clocksources (pit, jiffies) with the kthrt patch, where it wouldn't fall back to non-high-res when the clocksource stopped supporting it.
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/
| |