On Jan 6, 2008 2:11 PM, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > On Sunday, 6 of January 2008, Parag Warudkar wrote: > > On Jan 6, 2008 7:57 AM, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > On Sunday, 6 of January 2008, Ingo Molnar wrote: > > > > > > > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > > > > > > > Subject : soft lockup - CPU#1 stuck for 15s! [swapper:0] > > > > > Submitter : "Parag Warudkar" <[EMAIL PROTECTED]> > > > > > Date : 2007-12-07 18:14 > > > > > References : http://lkml.org/lkml/2007/12/7/299 > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=9525 > > > > > Handled-By : "Pallipadi, Venkatesh" <[EMAIL PROTECTED]> > > > > > Thomas Gleixner <[EMAIL PROTECTED]> > > > > > Ingo Molnar <[EMAIL PROTECTED]> > > > > > > > > i think this only occurs with cpuidle, right? drivers/cpuidle/ and > > > > CPU_IDLE is new in 2.6.24 so this appears to be a bug in that code (or a > > > > bug elsewhere triggered by that code), not a regression from v2.6.23. > > > > > > OK, removed from the regressions list. > > > > Nope - actually it did happen without CPU_IDLE so it is definitely a > > regression. > > (See http://lkml.org/lkml/2007/12/17/93 ) > > > > And it does happen with latest git which I believe has your patch Ingo. > > > > So I would suggest to keep it on the list of regressions. > > OK > > Thanks for the clarification. >
BTW, I have so far tested 2.6.24-rc4/5/6/7 and 2.6.23.12 - all of which have this problem. Yesterday I went back to using 2.6.22.15 and after a day's uptime it has not reproduced with the same config. Time for git-bisect I suppose? (the only problem is that this takes anywhere between 20 minutes to 8 hrs to confirm reliably.) Parag -- 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/
