From: Andy Whitcroft <apw@shadowen.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
torvalds@linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70
Date: Tue, 16 Oct 2007 11:03:11 +0100 [thread overview]
Message-ID: <20071016100311.GD17517@shadowen.org> (raw)
In-Reply-To: <20071016091012.GB24341@elte.hu>
On Tue, Oct 16, 2007 at 11:10:12AM +0200, Ingo Molnar wrote:
>
> * Kamalesh Babulal <kamalesh@linux.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
next prev parent reply other threads:[~2007-10-16 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 5:25 [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70 Kamalesh Babulal
2007-10-16 9:10 ` Ingo Molnar
2007-10-16 9:46 ` Ingo Molnar
2007-10-16 18:00 ` Andy Whitcroft
2007-10-16 18:42 ` Srivatsa Vaddagiri
2007-10-17 9:07 ` Andy Whitcroft
2007-10-16 10:03 ` Andy Whitcroft [this message]
2007-10-17 14:21 ` Ingo Molnar
2007-10-17 14:43 ` Andy Whitcroft
2007-10-17 15:00 ` Srivatsa Vaddagiri
2007-10-17 14:52 ` Ingo Molnar
2007-10-17 15:29 ` Andy Whitcroft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071016100311.GD17517@shadowen.org \
--to=apw@shadowen.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dmitry.adamushko@gmail.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.