Re: 2.6.28-rc2: REGRESSION in early boot

["Yinghai Lu" <yinghai@kernel.org>]

On Tue, Nov 4, 2008 at 2:45 PM, Theodore Tso <tytso@mit.edu> wrote:
> I've opened a Kernel Bug to track this regression:
>
>     http://bugzilla.kernel.org/show_bug.cgi?id=11951
>
> My fileserver boots under 2.6.27, but it is failing to boot on
> 2.6.28-rc2.  It took me a while to bisect, so after I finished the
> bisection, I retested with the latest mainline
> (v2.6.28-rc3-54-g75fa677), and the problem still shows up.
>
> Essentially, the system panics in early boot, resulting in multiple
> oops.  I finally was able get the very first oops, and the image of
> that oops can be found here:
>
> http://thunk.org/tytso/2.6.27-regress/92b29b8/IMG_0331.JPG
>
> From the console snapshot, it looks like two CPU simultaneously
> OOPS'ed with a:
>
> BUG: unable to handle kernel NULL dereference at 00000000
> BUG: unable to handle kernel NULL dereference at 00000038
>
> On the stack is "scheduler_tick+0x83/0x15f"
>
> When doing a bisection, the last good commit (i.e., the last one which
> I can boot on my system) is git id: d6c88a50 (which preceeds 2.6.28-rc1).
>
> The first bad git ID is:
>
> commit d6c88a507ef0b6afdb013cba4e7804ba7324d99a
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date:   Wed Oct 15 15:27:23 2008 +0200
>
>    genirq: revert dynarray
>
>    Revert the dynarray changes. They need more thought and polishing.
>
>    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> ... but in fact, the failure is different from the above messages.
> The failure is also in early boot, but the oops message is quite
> different:

please check http://lkml.org/lkml/2008/11/4/431

YH