On Wed, 2008-05-07 at 11:14 -0700, Martin Knoblauch wrote:
quoted text
> > The printk timestamps may jump around a bit at bootup,  especially if
> > you have unsynced TSCs, so that is a known issue. However its not
> > known to have any actual negative effect other then maybe causing the
> > dmesg log to be a bit confusing.
> > 
> 
>  the problem, is not just at bootup and the jumping. During the
> *complete* lifetime of the kernel I see:
> 
> a) the dmesg timestamps jumping back and forth
> b) the values are much to small and have absolutely no relation to
> "seconds after bootup", as they have with 2.6.24 and before.
> 
>  But you are right, it might not be a jiffie problem, but a "dmesg
> timestamp" thing.

Hrmm.. So the issue persisting over the lifetime of the kernel is a new
one by me. This may also have some effect in scheduling decisions (not
necessarily causing a correctness issue, but a performance one). Also it
may have some effect on thread cputime values.

Please do open a bug and provide example dmesg output. I'll try to tag
some folks who have access to the same system type. 

thanks
-john


--
unsubscribe notice
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/