From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: linux-next RCU complaint during boot
Date: Fri, 2 Sep 2011 03:53:32 +0200 [thread overview]
Message-ID: <20110902015330.GA28121@somewhere.redhat.com> (raw)
In-Reply-To: <20110902014424.GB2405@linux.vnet.ibm.com>
On Thu, Sep 01, 2011 at 06:44:24PM -0700, Paul E. McKenney wrote:
> On Thu, Sep 01, 2011 at 12:33:37PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > Seen during boot of linux-next 20110831:
> >
> > [ 8.823047] ------------[ cut here ]------------
> > [ 8.823177] WARNING: at kernel/rcutree.c:1821 rcu_needs_cpu_quick_check+0x6e/0x204()
> > [ 8.823314] Hardware name: Latitude E6500
> > [ 8.823418] Modules linked in:
> > [ 8.823601] Pid: 0, comm: swapper Not tainted 3.1.0-rc4-next-20110831-dirty #11
> > [ 8.823724] Call Trace:
> > [ 8.823824] <IRQ> [<ffffffff81039682>] warn_slowpath_common+0x7e/0x96
> > [ 8.824015] [<ffffffff81092467>] ? note_new_gpnum+0x32/0x96
> > [ 8.824034] [<ffffffff810396af>] warn_slowpath_null+0x15/0x17
> > [ 8.824034] [<ffffffff810917de>] rcu_needs_cpu_quick_check+0x6e/0x204
> > [ 8.824034] [<ffffffff81093df8>] rcu_needs_cpu+0x9/0xd
> > [ 8.824034] [<ffffffff81065933>] tick_nohz_stop_sched_tick+0x20a/0x420
> > [ 8.824034] [<ffffffff8103fd77>] irq_exit+0xd2/0xe0
> > [ 8.824034] [<ffffffff81018f91>] smp_apic_timer_interrupt+0x8b/0x99
> > [ 8.824034] [<ffffffff815a1b30>] apic_timer_interrupt+0x70/0x80
> > [ 8.824034] <EOI> [<ffffffff8159dbbf>] ? notifier_call_chain+0x20/0x81
> > [ 8.824034] [<ffffffff8159dc7e>] __atomic_notifier_call_chain+0x5e/0x90
> > [ 8.824034] [<ffffffff8159dc20>] ? notifier_call_chain+0x81/0x81
> > [ 8.824034] [<ffffffff8159dcbf>] atomic_notifier_call_chain+0xf/0x11
> > [ 8.824034] [<ffffffff8100092d>] cpu_idle+0xaf/0x102
> > [ 8.824034] [<ffffffff81569ddc>] rest_init+0xd0/0xd7
> > [ 8.824034] [<ffffffff81569d0c>] ? csum_partial_copy_generic+0x16c/0x16c
> > [ 8.824034] [<ffffffff81b31b09>] start_kernel+0x375/0x380
> > [ 8.824034] [<ffffffff81b3129f>] x86_64_start_reservations+0xaf/0xb3
> > [ 8.824034] [<ffffffff81b31393>] x86_64_start_kernel+0xf0/0xf7
> > [ 8.824034] ---[ end trace f6289633ba846f8f ]---
> >
> > Any ideas?
>
> This is a bug where someone uses RCU at a time when RCU has been told
> that the CPU is in dyntick-idle mode. Frederic Weisbecker has some
> patches that should address this.
Yep, see there: https://lkml.org/lkml/2011/8/20/81
next prev parent reply other threads:[~2011-09-02 1:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 16:33 linux-next RCU complaint during boot Valdis.Kletnieks
2011-09-02 1:44 ` Paul E. McKenney
2011-09-02 1:53 ` Frederic Weisbecker [this message]
2011-09-02 16:06 ` Valdis.Kletnieks
2011-09-02 16:37 ` 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=20110902015330.GA28121@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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