From: "Bjørn Mork" <bjorn@mork.no>
To: paulmck@linux.vnet.ibm.com
Cc: Dipankar Sarma <dipankar@in.ibm.com>,
linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [v3.10-rc1] WARNING: at kernel/rcutree.c:502
Date: Sun, 12 May 2013 20:19:34 +0200 [thread overview]
Message-ID: <87a9o0ukll.fsf@nemi.mork.no> (raw)
In-Reply-To: <20130512172135.GJ3648@linux.vnet.ibm.com> (Paul E. McKenney's message of "Sun, 12 May 2013 10:21:35 -0700")
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> writes:
> On Sun, May 12, 2013 at 05:55:00PM +0200, Bjørn Mork wrote:
>> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> writes:
>> > On Sun, May 12, 2013 at 11:08:50AM +0200, Bjørn Mork wrote:
>> >> Hello,
>> >>
>> >> got the splat below when running powertop on plain v3.10-rc1
>> >> (i.e. without my previously mentioned revert patch or any other extra
>> >> patches). Config attached.
>> >
>> > OK, it looks like you have context-tracking enabled, so you might be
>> > hitting a bug that Steven Rostedt found a few days ago. Could you
>> > please try out his fix below?
>>
>> Thanks for the quick reply, but I'm afraid that patch had no effect on
>> the warning I got. It's still there.
>
> Other than wondering whether powertop has issues similar to the bug
> Steven Rostedt located, I must confess myself clueless. Here are some
> diagnostics I can suggest:
>
> 1. Run in 32-bit mode. This disables some of the new adaptive-ticks
> functionality, so might give a probabilistic indication of where
> the bug lies.
>
> 2. The standard fallback of bisection.
>
> Would you be willing to do either of these?
Willing, yes. But it will take some time before I am able to do either
unless I can recreate the problem in a virtual machine. I assume that
you by " 32-bit mode" mean a 32bit kernel? I'm not exactly set up to
run that on my laptop. Bisection will be less work.
To be honest, I don't even know how old this thing is. It could be
totally unrelated to your recent changes for all I know. Running
powertop is something I do once every 6 kernel releases or something
like that...
I'll see what I can come up with. Thanks for your attention.
Bjørn
next prev parent reply other threads:[~2013-05-12 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 9:08 [v3.10-rc1] WARNING: at kernel/rcutree.c:502 Bjørn Mork
2013-05-12 11:39 ` Paul E. McKenney
2013-05-12 15:55 ` Bjørn Mork
2013-05-12 17:21 ` Paul E. McKenney
2013-05-12 18:19 ` Bjørn Mork [this message]
2013-05-12 20:58 ` Paul E. McKenney
2013-05-12 23:35 ` Bjørn Mork
2013-05-13 14:39 ` Bjørn Mork
2013-05-13 22:31 ` Srivatsa S. Bhat
2013-05-14 7:38 ` Bjørn Mork
2013-05-14 7:46 ` Srivatsa S. Bhat
2013-05-14 7:51 ` Srivatsa S. Bhat
2013-05-14 8:20 ` Bjørn Mork
2013-05-14 8:21 ` Srivatsa S. Bhat
2013-05-14 10:24 ` Paul E. McKenney
2013-05-14 15:50 ` [tip:core/urgent] rcu/idle: Wrap cpu-idle poll mode within rcu_idle_enter/exit tip-bot for Srivatsa S. Bhat
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=87a9o0ukll.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
/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