From: Dipankar Sarma <dipankar@in.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.17-rt1 : fix x86_64 oops
Date: Tue, 4 Jul 2006 09:45:19 +0530 [thread overview]
Message-ID: <20060704041519.GC16074@in.ibm.com> (raw)
In-Reply-To: <20060703165750.GB3899@in.ibm.com>
On Mon, Jul 03, 2006 at 10:27:50PM +0530, Dipankar Sarma wrote:
> On Thu, Jun 29, 2006 at 10:11:45PM +0200, Ingo Molnar wrote:
> >
> > * Paul E. McKenney <paulmck@us.ibm.com> wrote:
> > > OK, I ran this with both torture types (rcu and rcu_bh) on i386 with
> > > CONFIG_PREEMPT=y on 2.6.17-mm4 and didn't see any "scheduling while
> > > atomic" oopses -- or any other oopses, for that matter.
> > >
> > > Here is the .config file I used. What am I missing here?
> >
> > hm, i'm seeing some other types of crashes too - so rcutorture could
> > just have been collateral damage. It was on i386, an allyesconfig
> > bzImage kernel.
>
> With 2.6.17-rt5 I see this -
>
> Starting pass 0
> Unable to handle kernel paging request at ffffffff88006bd0 RIP:
> <ffffffff802597d5>{rcu_process_callbacks+107}
> rcutorture: --- End of test: SUCCESS: nreaders=8 stat_interval=1PGD 203027 PUD 205027 PMD 21eb18067 PTE 21829f163
> Oops: 0000 [1] PREEMPT SMP
> CPU 1
>
> I have been able to reproduce a similar looking oopse with 2.6.16-rt29.
> 2.6.16-rt20 works fine. I will try to track it down to the exact
> release as far as I can.
OK, it looks as if rt20 is fine but rt21 is broken. So something
that got in rt21 is causing this oops.
Ingo, do you have a suspect ?
Thanks
Dipankar
next prev parent reply other threads:[~2006-07-04 4:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 20:01 2.6.17-rt1 : x86_64 oops Dipankar Sarma
2006-06-28 18:21 ` [PATCH] 2.6.17-rt1 : fix " Dipankar Sarma
2006-06-28 19:32 ` Ingo Molnar
2006-06-28 20:02 ` Dipankar Sarma
2006-06-29 14:24 ` Ingo Molnar
2006-06-29 16:32 ` Paul E. McKenney
2006-06-29 19:41 ` Paul E. McKenney
2006-06-29 20:11 ` Ingo Molnar
2006-06-29 21:35 ` Paul E. McKenney
2006-07-03 16:57 ` Dipankar Sarma
2006-07-04 4:15 ` Dipankar Sarma [this message]
2006-07-04 6:43 ` Ingo Molnar
2006-07-04 6:50 ` Ingo Molnar
2006-07-05 9:11 ` Dipankar Sarma
2006-07-26 7:36 ` Dipankar Sarma
2006-07-06 20:06 ` Paul E. McKenney
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=20060704041519.GC16074@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.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