Re: PROBLEM: 3.0-rc kernels unbootable since -rc3

["Paul E. McKenney" <paulmck@linux.vnet.ibm.com>]

On Sun, Jul 10, 2011 at 10:16:26AM -0700, Paul E. McKenney wrote:
> On Sun, Jul 10, 2011 at 05:38:25PM +0100, julie Sullivan wrote:
> > > I added another patch onto the jms.2011.07.07a in the -rcu git tree.
> > > If you get a chance to test it, please let me know how it goes.
> > >
> > >                                                        Thanx, Paul
> > 
> > 
> > Right, adding this commit to the other six:
> > 
> > commit 8a153670878242b8a95213d986f4922111321743
> > 
> >  makes us freeze on boot again.
> 
> Thank you again for the testing!  This one will take some thought...

But maybe not that much thought.  My current guess is that your
configuration is somehow causing some RCU callbacks to be executed
during early boot, and that these callbacks are attempting to use kernel
features that are not yet initialized.  If my guess is correct, then
the reason that enabling RCU_BOOST makes things work is that it prevents
RCU callbacks from executing until after the scheduler is up and running.

So I added another commit to the jms.2011.07.07a branch in the -rcu
git tree.  If my guesses are correct, this will allow your system to
boot, possibly emitting a warning on the way up.  When you get a chance
to try this out, please let me know how it goes.

							Thanx, Paul