lkml.org 
[lkml]   [2005]   [Nov]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 0/13] Time: Generic Timeofday Subsystem (v B10)
From
Date
On Mon, 2005-11-14 at 14:53 -0700, Frank Sorenson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> john stultz wrote:
> > Hmm... Not sure if this is mis-calibration or just bad-interaction w/
> > kthrt. Mind sending a dmesg to me?
>
> dmesg attached

Thanks, I'll start looking into it.

> >>and 'pit' seems to produce errors (system will not switch from pit to
> >>another clocksource anymore):
>
> Odd. This time, I got the errors when I switched from acpi_pm (which it
> had defaulted to at bootup) to jiffies. System has not locked at one
> clocksource yet, though.

Yea, jiffies and pit are similarly non-continuous clocksources.

> > 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.
>
> I only tried with kthrt because I ran into lots of conflicts when
> applying the patches to more recent kernels otherwise. I can try again
> with 2.6.14-mm2 in order to test it out.

You can alternatively drop the patches in the kthrt set that are after
the timeofday patches in Thomas' series file. Or even just disable the
high-res config option and see if that changes anything.

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/

\
 
 \ /
  Last update: 2005-11-14 23:05    [W:0.556 / U:0.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site