From: Chuck Ebbert <cebbert@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Greg KH <greg@kroah.com>, David <david@unsolicited.net>,
Jeremy Fitzhardinge <jeremy@goop.org>,
gregkh@suse.de, 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: Mon, 19 Nov 2007 19:30:27 -0500 [thread overview]
Message-ID: <47422AA3.7060507@redhat.com> (raw)
In-Reply-To: <20071118005538.GD26865@elte.hu>
On 11/17/2007 07:55 PM, Ingo Molnar wrote:
> * Greg KH <greg@kroah.com> wrote:
>
>> Great, thanks for tracking this down.
>>
>> Ingo, this corrisponds to changeset
>> a115d5caca1a2905ba7a32b408a6042b20179aaa in mainline. Is that patch
>> incorrect? Should this patch in the -stable tree be reverted?
>
> hm, there are no such problems in .24 and the cpu_clock() and other
> fixes i did were not picked up. Find the missing fixes below. They
> should work just fine in .23 as it has the cpu_clock() functionality
> too.
>
> [ NOTE: the most robust thing is to make the .23 version match the .24
> version of kernel/softlockup.c, so i included two other harmless
> changes in this diff as well. ]
>
> Ingo
>
> ----------->
> commit a5f2ce3c6024a5bb895647b6bd88ecae5001020a
> Author: Ingo Molnar <mingo@elte.hu>
> Date: Tue Oct 16 23:26:08 2007 -0700
>
> commit 43581a10075492445f65234384210492ff333eba
> Author: Ingo Molnar <mingo@elte.hu>
> Date: Tue Oct 16 23:26:08 2007 -0700
Those are just cosmetic / cleanup changes.
Don't you need commit a3b13c23f186ecb57204580cc1f2dbe9c284953a ??
next prev parent reply other threads:[~2007-11-20 0:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 18:21 Soft lockups since stable kernel upgrade to 2.6.23.8 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
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 [this message]
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=47422AA3.7060507@redhat.com \
--to=cebbert@redhat.com \
--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=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.