On Thu, Aug 06, 2009 at 02:29:35PM +0200, Ingo Molnar wrote: > > * Gautham R Shenoy <ego@xxxxxxxxxx> wrote: > > > On Wed, Aug 05, 2009 at 06:26:45PM -0700, Paul E. McKenney wrote: > > > On Mon, Aug 03, 2009 at 05:56:18AM -0700, Paul E. McKenney wrote: > > > > On Mon, Aug 03, 2009 at 09:04:58AM +0200, Ingo Molnar wrote: > > > > > > > > > > i've attached the full serial bootlog with the warning in it. This > > > > > should address your question about what the order of initialization > > > > > is, right? > > > > > > > > It does, thank you! This problem really is happening during boot. > > > > > > > > > Let me know if you still would like me to run your diagnostic patch > > > > > too. > > > > > > > > Now that you mention it, you should probably let me test it a bit first. > > > > > > And here is a tested and debugged version. Diagnostic only, not for > > > inclusion, based on tip/core/rcu as of today (August 5th). > > > > > > Gautham, have you been able to reproduce on your machines? > > > Still cannot here. > > > > I tried on a couple of machines yesterday, but I still couldn't > > reproduce it with Ingo's config. > > Paul, should i try your latest diagnostic patch in -tip testing, to > see whether it triggers any new warning? Could you please? Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|