From: Sedat Dilek <sedat.dilek@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
Dave Hansen <dave@sr71.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Kristen Carlson Accardi <kristen@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>
Subject: Re: linux-next: Tree for Feb 4
Date: Thu, 5 Feb 2015 23:16:21 +0100 [thread overview]
Message-ID: <CA+icZUX_f_M7EmV3OM_CeosjfqoMSkJrCgUBm0LKFFurFGRvGQ@mail.gmail.com> (raw)
In-Reply-To: <20150205170952.525bdee6@gandalf.local.home>
On Thu, Feb 5, 2015 at 11:09 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 5 Feb 2015 22:45:59 +0100
> Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
>> Steve, this was a typo it's called tlb_flush not tlb_flush*ed*:
>
> Heh, yeah, I typed that entire line in by hand. Just be lucky that was
> the only typo ;-)
>
>>
>> # cat /sys/kernel/debug/tracing/events/tlb/tlb_flush/enable
>> 1
>>
>> [ 391.090381] intel_pstate CPU 1 exiting
>> [ 391.104491] smpboot: CPU 1 is now offline
>>
>
> Now, if you disable that (echo 0 to that file), do you still get the
> rcu lockdep splat if you suspend and resume?
>
YES, I get the call-trace again!
# cat /sys/kernel/debug/tracing/events/tlb/tlb_flush/enable
0
# cat /sys/devices/system/cpu/cpu1/online
0
[ 2470.606222] intel_pstate CPU 1 exiting
[ 2470.628153]
[ 2470.628155] ===============================
[ 2470.628156] [ INFO: suspicious RCU usage. ]
[ 2470.628159] 3.19.0-rc7-next-20150204.9-iniza-small #1 Not tainted
[ 2470.628160] -------------------------------
[ 2470.628162] include/trace/events/tlb.h:37 suspicious
rcu_dereference_check() usage!
[ 2470.628163]
[ 2470.628163] other info that might help us debug this:
[ 2470.628163]
[ 2470.628164]
[ 2470.628164] RCU used illegally from offline CPU!
[ 2470.628164] rcu_scheduler_active = 1, debug_locks = 0
[ 2470.628165] no locks held by swapper/1/0.
[ 2470.628166]
[ 2470.628166] stack backtrace:
[ 2470.628169] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
3.19.0-rc7-next-20150204.9-iniza-small #1
[ 2470.628171] Hardware name: SAMSUNG ELECTRONICS CO., LTD.
530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013
[ 2470.628176] 0000000000000001 ffff88011a44fe18 ffffffff817ecf4d
0000000000000011
[ 2470.628179] ffff88011a448290 ffff88011a44fe48 ffffffff810d6b57
ffff8800cc2660c0
[ 2470.628182] 0000000000000001 ffffffff81d35160 0000000000000002
ffff88011a44fe78
[ 2470.628183] Call Trace:
[ 2470.628192] [<ffffffff817ecf4d>] dump_stack+0x4c/0x65
[ 2470.628198] [<ffffffff810d6b57>] lockdep_rcu_suspicious+0xe7/0x120
[ 2470.628203] [<ffffffff810b7459>] idle_task_exit+0x1c9/0x260
[ 2470.628208] [<ffffffff81054c4e>] play_dead_common+0xe/0x50
[ 2470.628211] [<ffffffff81054ca5>] native_play_dead+0x15/0x140
[ 2470.628216] [<ffffffff8102963f>] arch_cpu_idle_dead+0xf/0x20
[ 2470.628219] [<ffffffff810cdbae>] cpu_startup_entry+0x37e/0x580
[ 2470.628222] smpboot: CPU 1 didn't die...
[ 2470.628224] [<ffffffff81053e20>] start_secondary+0x140/0x150
- Sedat -
next prev parent reply other threads:[~2015-02-05 22:16 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 8:35 linux-next: Tree for Feb 4 Stephen Rothwell
2015-02-04 12:26 ` Sedat Dilek
2015-02-04 15:16 ` Jens Axboe
2015-02-04 15:21 ` Sedat Dilek
2015-02-04 15:31 ` Jens Axboe
2015-02-04 15:36 ` Sedat Dilek
2015-02-04 15:58 ` Martin K. Petersen
2015-02-04 16:06 ` Sedat Dilek
2015-02-05 3:17 ` Martin K. Petersen
2015-02-05 3:41 ` Sedat Dilek
2015-02-05 19:46 ` Sedat Dilek
2015-02-06 15:24 ` Sedat Dilek
2015-02-04 20:18 ` Sedat Dilek
2015-02-04 21:54 ` Rafael J. Wysocki
2015-02-04 21:53 ` Paul E. McKenney
2015-02-04 22:59 ` Rafael J. Wysocki
2015-02-04 23:51 ` Paul E. McKenney
2015-02-04 23:58 ` Sedat Dilek
2015-02-05 0:10 ` Paul E. McKenney
2015-02-05 0:30 ` Sedat Dilek
2015-02-05 0:57 ` Paul E. McKenney
2015-02-05 1:18 ` Sedat Dilek
2015-02-05 1:51 ` Paul E. McKenney
2015-02-05 1:53 ` Sedat Dilek
2015-02-05 2:12 ` Sedat Dilek
2015-02-05 4:13 ` Paul E. McKenney
2015-02-05 7:14 ` Dave Hansen
2015-02-05 14:37 ` Paul E. McKenney
2015-02-05 14:57 ` Sedat Dilek
2015-02-05 16:58 ` Paul E. McKenney
2015-02-05 18:03 ` Steven Rostedt
2015-02-05 18:08 ` Steven Rostedt
2015-02-05 18:11 ` Dave Hansen
2015-02-05 18:34 ` Paul E. McKenney
2015-02-05 18:35 ` Dave Hansen
2015-02-05 18:45 ` Paul E. McKenney
2015-02-05 19:25 ` Sedat Dilek
2015-02-05 19:33 ` Paul E. McKenney
2015-02-05 19:42 ` Sedat Dilek
2015-02-05 19:58 ` Steven Rostedt
2015-02-05 20:07 ` Sedat Dilek
2015-02-05 20:22 ` Steven Rostedt
2015-02-05 20:50 ` Sedat Dilek
2015-02-05 21:45 ` Sedat Dilek
2015-02-05 22:09 ` Steven Rostedt
2015-02-05 22:16 ` Sedat Dilek [this message]
2015-02-05 23:11 ` Steven Rostedt
2015-02-05 23:53 ` Sedat Dilek
2015-02-06 0:03 ` Sedat Dilek
2015-02-06 0:12 ` Steven Rostedt
2015-02-06 0:14 ` Sedat Dilek
2015-02-04 22:38 ` Sedat Dilek
2015-02-04 23:25 ` Rafael J. Wysocki
2015-02-04 23:54 ` Sedat Dilek
2015-02-04 22:46 ` Sedat Dilek
2015-02-04 23:30 ` Rafael J. Wysocki
2015-02-04 23:48 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2022-02-04 4:14 Stephen Rothwell
2021-02-04 9:13 Stephen Rothwell
2020-02-04 4:19 Stephen Rothwell
2019-02-04 5:35 Stephen Rothwell
2016-02-04 3:48 Stephen Rothwell
2014-02-04 5:07 Stephen Rothwell
[not found] ` <CAP=VYLpgLC_4yuPtQH_yAd8S9cqQAVu2uB2=Wf3q_zgY4uzkLw@mail.gmail.com>
2014-02-04 22:23 ` Stephen Rothwell
2014-02-05 0:41 ` Stephen Rothwell
2013-02-04 7:39 Stephen Rothwell
2013-02-04 13:56 ` James Hogan
2013-02-04 20:33 ` Stephen Rothwell
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=CA+icZUX_f_M7EmV3OM_CeosjfqoMSkJrCgUBm0LKFFurFGRvGQ@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=dave@sr71.net \
--cc=hpa@linux.intel.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=riel@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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).