[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071120210315.GC13160@kroah.com>
Date: Tue, 20 Nov 2007 13:03:15 -0800
From: Greg KH <greg@...ah.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>, Greg KH <gregkh@...e.de>,
linux-kernel@...r.kernel.org, stable@...nel.org,
Javier Kohen <jkohen@...rs.sourceforge.net>,
Andrew Morton <akpm@...ux-foundation.org>,
David <david@...olicited.net>
Subject: Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8
On Tue, Nov 20, 2007 at 09:39:19PM +0100, Ingo Molnar wrote:
>
> * Greg KH <greg@...ah.com> 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.
Ok, I'll see if the current round of patches fix up everyone complaints
:)
thanks for sending these,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists