From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/rcu] rcu: Fix holdoff for accelerated GPs for last non-dynticked CPU
Date: Wed, 17 Mar 2010 12:22:41 -0700 [thread overview]
Message-ID: <20100317192241.GB6806@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100317175311.GA5187@elte.hu>
On Wed, Mar 17, 2010 at 06:53:11PM +0100, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > incidentally i have a RCU badness crash log from another box:
> >
> > [ 4.573332] initcall ipmi_init_msghandler_mod+0x0/0xd returned 0 after 0 usecs
> > [ 4.573332] calling init_ipmi_si+0x0/0x435 @ 1
> > [ 4.573332] IPMI System Interface driver.
> > [ 4.573340] [<ffffffff81022cdc>] no_context+0x1fc/0x20b
> > [ 4.576672] [<ffffffff81002a16>] ? ftrace_call+0x5/0x2b
> > [ 4.580021] [<ffffffff81022e77>] __bad_area_nosemaphore+0x18c/0x1af
> > [ 4.583338] [<ffffffff81002a16>] ? ftrace_call+0x5/0x2b
> > [ 4.586672] [<ffffffff81022ead>] bad_area_nosemaphore+0x13/0x15
> > [ 4.590005] [<ffffffff81023159>] do_page_fault+0x138/0x284
> > [ 4.593354] [<ffffffff81a632bf>] page_fault+0x1f/0x30
>
> I spent a few hours yesterday and today trying to track this down, but failed
> to bisect it. The crash is sporadic on many configs - which confused my
> bisection attempts. Sometimes it crashes only after 10 reboots. Was able to
> crash v2.6.30 as well, so it's an older bug. v2.6.29 was not testable on that
> box due to network driver problems so i stopped there.
OK, I give up...
What did you change about your testing? ;-)
Thanx, Paul
next prev parent reply other threads:[~2010-03-17 19:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 22:52 [PATCH tip/core/rcu 0/2] more lockdep-RCU and RCU_FAST_NO_HZ fixes Paul E. McKenney
2010-02-27 22:53 ` [PATCH tip/core/rcu 1/2] rcu: fix holdoff for accelerated GPs for last non-dynticked CPU Paul E. McKenney
2010-02-28 8:59 ` [tip:core/rcu] rcu: Fix " tip-bot for Paul E. McKenney
2010-03-16 11:00 ` Ingo Molnar
2010-03-16 11:03 ` Ingo Molnar
2010-03-16 11:51 ` Ingo Molnar
2010-03-16 12:15 ` Ingo Molnar
2010-03-16 13:30 ` Paul E. McKenney
2010-03-17 17:53 ` Ingo Molnar
2010-03-17 19:22 ` Paul E. McKenney [this message]
2010-03-17 19:35 ` Ingo Molnar
2010-02-27 22:53 ` [PATCH tip/core/rcu 2/2] rcu: make task_subsys_state() RCU-lockdep checks handle boot-time use Paul E. McKenney
2010-02-28 8:59 ` [tip:core/rcu] rcu: Make " tip-bot for Paul E. McKenney
2010-03-01 19:47 ` Paul Menage
2010-02-28 8:55 ` [PATCH tip/core/rcu 0/2] more lockdep-RCU and RCU_FAST_NO_HZ fixes Ingo Molnar
2010-02-28 16:32 ` Paul E. McKenney
2010-03-01 8:33 ` [tip:core/rcu] sched, rcu: Fix rcu_dereference() for RCU-lockdep tip-bot for Paul E. McKenney
2010-03-01 12:10 ` [PATCH tip/core/rcu 0/2] more lockdep-RCU and RCU_FAST_NO_HZ fixes Ingo Molnar
2010-03-01 16:08 ` Paul E. McKenney
2010-03-01 17:58 ` Peter Zijlstra
2010-03-01 18:50 ` 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=20100317192241.GB6806@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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