[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071016100311.GD17517@shadowen.org>
Date: Tue, 16 Oct 2007 11:03:11 +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>
Subject: Re: [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70
On Tue, Oct 16, 2007 at 11:10:12AM +0200, Ingo Molnar 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.
To fill in a few details. This was triggered in the middle of a
kernbench run on the machine. A job with just dbench runs in it ran to
completion. The machine is a 4 node numa x86_64 system.
Seems that most schedular options are on:
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_FAIR_USER_SCHED=y
At the moment we don't have any historical jobs back from 2.6.23 so I
cannot be more specific as to when it arrived in mainline. The x86/x86_64
merge broke our build process; a bad assumption here, not a problem with
the merge.
-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