Messages in this thread | | | Date | Tue, 20 Nov 2007 07:08:08 +0100 | From | Ingo Molnar <> | Subject | Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8 |
| |
* Chuck Ebbert <cebbert@redhat.com> wrote:
> 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 ??
yes:
> > [...] the cpu_clock() and other fixes i did were not picked up.
i just forgot to attach the cpu_clock() changes - they are in a3b13c23.
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |