From: Ingo Molnar <mingo@elte.hu>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
torvalds@linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@shadowen.org>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70
Date: Tue, 16 Oct 2007 11:46:31 +0200 [thread overview]
Message-ID: <20071016094631.GA10649@elte.hu> (raw)
In-Reply-To: <20071016091012.GB24341@elte.hu>
* Ingo Molnar <mingo@elte.hu> 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.
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.
Ingo
next prev parent reply other threads:[~2007-10-16 9:46 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 [this message]
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
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=20071016094631.GA10649@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dmitry.adamushko@gmail.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vatsa@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox