Prev: [PATCH 3/3] [2.6.26] ehea: Add DLPAR memory remove support
Next: Scalability requirements for sysv ipc - v3
From: Henrique de Moraes Holschuh on 7 May 2008 09:00
On Wed, 07 May 2008, Martin Knoblauch wrote:
> any news on the one below? I upgraded to 2.6.25.2 and the problem still persists. Would adding a bugzilla actually help ? :-)

Well, at least a bugzilla entry makes it impossible for the information
to be lost, so IMHO unless you get a patch right away, it is a good idea
to open one.

As for it helping someone to actually go and FIX the bug, no :-)

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: John Stultz on 7 May 2008 15:10
On Wed, 2008-05-07 at 11:14 -0700, Martin Knoblauch wrote:
> > 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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 3/3] [2.6.26] ehea: Add DLPAR memory remove support
Next: Scalability requirements for sysv ipc - v3