From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
paulmck@linux.vnet.ibm.com, jack@suse.cz,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
Tejun Heo <tj@kernel.org>,
Michael Wang <wangyun@linux.vnet.ibm.com>
Subject: Re: WARNING: at kernel/rcutree.c:1558 rcu_do_batch+0x386/0x3a0(), during CPU hotplug
Date: Fri, 14 Sep 2012 18:04:44 +0530 [thread overview]
Message-ID: <50532464.5050904@linux.vnet.ibm.com> (raw)
In-Reply-To: <1347625519.7172.31.camel@twins>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
On 09/14/2012 05:55 PM, Peter Zijlstra wrote:
> On Fri, 2012-09-14 at 17:48 +0530, Srivatsa S. Bhat wrote:
>> #! /bin/bash
>
> CPUPATH="/sys/devices/system/cpu"
>
>> NUMBER_OF_CPUS=`ls -d /sys/devices/system/cpu/cpu[0-9]* | wc -l`
>
> apply the above
>
>> cd /sys/devices/system/cpu
>
> skip this, so running the script doesn't change PWD
>
>> while [ 1 ]
>
> while :;
>
>> do
>> for ((i=1; i < NUMBER_OF_CPUS; i++))
>> do
>> sleep 1;
>
> Also play with shorter sleeps like: sleep .1, I've found that higher
> hotplug rate triggers some races faster.
>
>> state=`cat cpu$i/online`
>> if [ $state -eq 0 ]
>> then
>> echo 1 > cpu$i/online
>> else
>> echo 0 > cpu$i/online
>
> echo $((state^1)) > $CPUPATH/cpu$i/online
>
>> fi
>> done
>> done
>
>
Thanks a lot Peter for your suggestions!
Fengguang, like I had mentioned some time before, somebody had pointed
me to a hotplug test-suite that I believe is being used in LTP.
I have a copy of that suite, which I have attached with this mail.
I have never actually used it seriously before (because I could trigger
bugs with my simple script!), so I don't exactly know what state it is
in ;-)
Regards,
Srivatsa S. Bhat
[-- Attachment #2: lhcs_regression-1.6.tgz --]
[-- Type: application/x-compressed-tar, Size: 17854 bytes --]
next prev parent reply other threads:[~2012-09-14 12:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 12:09 WARNING: at kernel/rcutree.c:1550 __rcu_process_callbacks+0x46f/0x4b0() Srivatsa S. Bhat
2012-07-19 17:15 ` Paul E. McKenney
2012-07-20 10:41 ` Srivatsa S. Bhat
2012-07-20 14:36 ` Paul E. McKenney
2012-07-20 14:57 ` Srivatsa S. Bhat
2012-09-12 12:36 ` WARNING: at kernel/rcutree.c:1558 rcu_do_batch+0x386/0x3a0(), during CPU hotplug Srivatsa S. Bhat
2012-09-12 15:31 ` Paul E. McKenney
2012-09-13 6:30 ` Michael Wang
2012-09-13 12:47 ` Srivatsa S. Bhat
2012-09-14 4:33 ` Michael Wang
2012-09-26 9:35 ` Srivatsa S. Bhat
2012-09-27 2:59 ` Michael Wang
2012-09-27 19:06 ` Srivatsa S. Bhat
2012-09-13 8:35 ` Srivatsa S. Bhat
2012-09-14 11:47 ` Fengguang Wu
2012-09-14 12:18 ` Srivatsa S. Bhat
2012-09-14 12:25 ` Peter Zijlstra
2012-09-14 12:32 ` Fengguang Wu
2012-09-14 12:34 ` Srivatsa S. Bhat [this message]
2012-09-14 12:28 ` Fengguang Wu
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=50532464.5050904@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=wangyun@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;
as well as URLs for NNTP newsgroup(s).