[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071016180037.GC5670@shadowen.org>
Date: Tue, 16 Oct 2007 19:00:37 +0100
From: Andy Whitcroft <apw@...dowen.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
torvalds@...ux-foundation.org,
Andrew Morton <akpm@...ux-foundation.org>,
Dmitry Adamushko <dmitry.adamushko@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Subject: Re: [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70
On Tue, Oct 16, 2007 at 11:46:31AM +0200, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@...e.hu> wrote:
>
> >
> > * Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com> wrote:
> >
> > > While running kernbench with the 2.6.23-git8 following oops is
> > > produced
> > >
> > > Unable to handle kernel NULL pointer dereference at 0000000000000010 RIP:
> > > [<ffffffff8033f347>] __rb_rotate_left+0x7/0x70
> >
> > that looks nasty ...
> >
> > and -git8 should have the v2.6.23 scheduler code in essence.
>
> ah, this is likely with the recent scheduler commits included as well,
> right?
>
> if it's reproducable, could you try with group scheduling disabled, i.e.
> with:
>
> # CONFIG_FAIR_GROUP_SCHED is not set
>
> as that would be the main suspect for such type of a crash.
Ok, preliminary results with this disabled seem to get us past
kernbench. I am rerunning with it enabled to confirm it blammo's.
-apw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists