From: Ingo Molnar <mingo@elte.hu>
To: Greg KH <greg@kroah.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, Greg KH <gregkh@suse.de>,
David <david@unsolicited.net>,
Javier Kohen <jkohen@users.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8
Date: Tue, 20 Nov 2007 21:39:19 +0100 [thread overview]
Message-ID: <20071120203919.GB10008@elte.hu> (raw)
In-Reply-To: <20071120170519.GB15954@kroah.com>
* Greg KH <greg@kroah.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.
Ingo
next prev parent reply other threads:[~2007-11-20 20:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 18:21 Javier Kohen
2007-11-17 19:12 ` [stable] " Greg KH
2007-11-17 20:05 ` David
2007-11-17 20:37 ` Greg KH
2007-11-18 0:34 ` Jeremy Fitzhardinge
2007-11-19 23:22 ` Greg KH
2007-11-20 1:40 ` Jeremy Fitzhardinge
2007-11-20 6:05 ` Ingo Molnar
2007-11-20 17:05 ` Greg KH
2007-11-20 20:39 ` Ingo Molnar [this message]
2007-11-20 21:03 ` Greg KH
2007-11-20 21:49 ` Ingo Molnar
2007-11-20 22:06 ` Greg KH
2007-11-20 23:15 ` David Miller
2007-11-20 23:26 ` Ingo Molnar
2007-11-20 23:52 ` Greg KH
2007-11-18 0:55 ` Ingo Molnar
2007-11-20 0:30 ` Chuck Ebbert
2007-11-20 6:08 ` Ingo Molnar
2007-11-20 17:04 ` Greg KH
2007-11-17 19:40 ` David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071120203919.GB10008@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=david@unsolicited.net \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jeremy@goop.org \
--cc=jkohen@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®