From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: paulmck@linux.vnet.ibm.com, dave@sr71.net
Subject: suspicious RCU usage. (TLB flush tracepoints)
Date: Wed, 6 Aug 2014 14:18:01 -0400 [thread overview]
Message-ID: <20140806181801.GA4605@redhat.com> (raw)
===============================
[ INFO: suspicious RCU usage. ]
3.16.0+ #34 Not tainted
-------------------------------
include/trace/events/tlb.h:35 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
RCU used illegally from idle CPU!
rcu_scheduler_active = 1, debug_locks = 1
RCU used illegally from extended quiescent state!
no locks held by swapper/1/0.
stack backtrace:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.16.0+ #34
0000000000000001 e7d0f46a57e60fc7 ffff880243357db0 ffffffff8a7f1e37
ffff880243360000 ffff880243357de0 ffffffff8a0cc6c5 ffff8801753693f8
ffff88023e2e2a40 0000000000000001 ffff88023e2e2a40 ffff880243357e10
Call Trace:
[<ffffffff8a7f1e37>] dump_stack+0x4e/0x7a
[<ffffffff8a0cc6c5>] lockdep_rcu_suspicious+0xd5/0x110
[<ffffffff8a049f05>] leave_mm+0x1a5/0x200
[<ffffffff8a3ec8df>] intel_idle+0x16f/0x190
[<ffffffff8a6623da>] cpuidle_enter_state+0x3a/0xd0
[<ffffffff8a662557>] cpuidle_enter+0x17/0x20
[<ffffffff8a0c719c>] cpu_startup_entry+0x43c/0x800
[<ffffffff8a03232d>] start_secondary+0x29d/0x3b0
Looks like this came from the addition of trace points in d17d8f9de
Dave
next reply other threads:[~2014-08-06 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 18:18 Dave Jones [this message]
2014-08-06 20:58 ` suspicious RCU usage. (TLB flush tracepoints) Dave Hansen
2014-08-07 6:50 ` 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=20140806181801.GA4605@redhat.com \
--to=davej@redhat.com \
--cc=dave@sr71.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.