* Greg KH <[email protected]> wrote:
> > 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.
i'd leave it alone - doing that we have in essence the softlockup
detector turned off. Reverting to the older version might trigger false
positives that need the new stuff.
Ingo
-
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/
- Prev by Date:
Re: [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7
- Next by Date:
Re: [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7
- Previous by thread:
Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8
- Next by thread:
Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8
- Index(es):
[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]
