From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Ingo Molnar <mingo@elte.hu>,
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>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70
Date: Wed, 17 Oct 2007 00:12:04 +0530 [thread overview]
Message-ID: <20071016184204.GA19219@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071016180037.GC5670@shadowen.org>
On Tue, Oct 16, 2007 at 07:00:37PM +0100, Andy Whitcroft wrote:
> > 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.
Andy,
I have got details from Kamalesh on the machine where this is
recreatable (we couldn't recreate on other machines). Will start looking
at this tomorrow morning first thing ..
--
Regards,
vatsa
next prev parent reply other threads:[~2007-10-16 18:30 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 [this message]
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=20071016184204.GA19219@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--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=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.