From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Gautham R Shenoy <ego@in.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: preempt rcu bug on s390
Date: Sat, 9 Feb 2008 06:07:11 -0800 [thread overview]
Message-ID: <20080209140711.GA16205@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080209113435.GA6915@osiris.boeblingen.de.ibm.com>
On Sat, Feb 09, 2008 at 12:34:35PM +0100, Heiko Carstens wrote:
> Using CONFIG_PREEMPT_RCU and CONFIG_NO_IDLE_HZ on s390 my system always
> gets stuck when running with more than one cpu.
> When booting with four cpus I get all four cpus caught withing cpu_idle
> and not advancing anymore. However there is the init process which is
> waitung for synchronize_rcu() to complete (lcrash output):
>
> STACK TRACE FOR TASK: 0xf84d968 (swapper)
>
> STACK:
> 0 schedule+842 [0x36c956]
> 1 schedule_timeout+172 [0x36d0e4]
> 2 wait_for_common+204 [0x36c398]
> 3 synchronize_rcu+76 [0x567bc]
> 4 netlink_change_ngroups+150 [0x2b4302]
> 5 genl_register_mc_group+256 [0x2b6174]
> 6 genl_init+188 [0x534e44]
> 7 kernel_init+444 [0x518334]
> 8 kernel_thread_starter+6 [0x192a6]
>
> If I change the code so that timer ticks won't be disabled everything
> runs fine. So my guess is that rcu_needs_cpu() doesn't do the right
> thing for the rcu preemptible case.
>
> Kernel version is git head of today.
>
> Any ideas?
Does this tree have http://lkml.org/lkml/2008/1/29/208 applied?
If not, could you please check it out?
Thanx, Paul
next prev parent reply other threads:[~2008-02-09 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 11:34 preempt rcu bug on s390 Heiko Carstens
2008-02-09 14:07 ` Paul E. McKenney [this message]
2008-02-09 17:14 ` Heiko Carstens
2008-02-09 22:02 ` Paul E. McKenney
2008-02-10 13:01 ` Heiko Carstens
2008-02-10 17:43 ` Paul E. McKenney
2008-02-11 15:37 ` Steven Rostedt
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=20080209140711.GA16205@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
--cc=srostedt@redhat.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