On Tue, Nov 20, 2007 at 07:05:25AM +0100, Ingo Molnar wrote:
>
> * Jeremy Fitzhardinge <[email protected]> wrote:
>
> > Greg KH wrote:
> > > Can you try applying the patch below to see if that solves the problem
> > > for you?
> > >
> >
> > I don't think this patch will help; it only has cosmetic changes in
> > addition to the original message printing fix. I think it also needs
> > change a3b13c23f186ecb57204580cc1f2dbe9c284953a:
> >
> > diff -r 79f0ea1e0e70 -r 06f060ab58aa kernel/softlockup.c
>
> yes, it does need the cpu_clock() changes as i mentioned.
>
> commit a3b13c23f186ecb57204580cc1f2dbe9c284953a
> Author: Ingo Molnar <[email protected]>
> Date: Tue Oct 16 23:26:06 2007 -0700
>
> softlockup: use cpu_clock() instead of sched_clock()
>
> sched_clock() is not a reliable time-source, use cpu_clock() instead.
>
> but we only have cpu_clock() from v2.6.23 onwards - so we should not
> apply the original patch to v2.6.22. (we should not have applied your
> patch that started the mess to begin with - but that's another matter.)
Well, I can easily back that one out, if that is easier than adding 2
more patches to try to fix up the mess here.
Let me know if you feel that would be best.
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
