From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: 3.0.0-rc5-mmotm0630 - rcu_update whinge in cpu_idle
Date: Tue, 05 Jul 2011 18:18:02 -0400 [thread overview]
Message-ID: <61640.1309904282@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2392 bytes --]
(Sorry if this is already reported, I'm back from 10 days off and am about 8,423 mails
behind on lkml ;)
Seen at boot of 3.0.0-rc5-mmotm0630:
[ 0.411716] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[ 0.411716] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 0.411716] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 0.417076] Switching to clocksource hpet
[ 0.417601] Warning: could not register annotated branches stats
[ 0.417925] Switched to NOHz mode on CPU #1
[ 0.417966] ------------[ cut here ]------------
[ 0.417973] WARNING: at include/linux/rcupdate.h:256 rcu_lock_acquire+0x6a/0xc5()
[ 0.417976] Hardware name: Latitude E6500
[ 0.417978] Modules linked in:
[ 0.417983] Pid: 0, comm: kworker/0:0 Not tainted 3.0.0-rc5-mmotm0630 #1
[ 0.417985] Call Trace:
[ 0.417991] [<ffffffff810383f6>] warn_slowpath_common+0x7e/0x96
[ 0.417995] [<ffffffff81038423>] warn_slowpath_null+0x15/0x17
[ 0.417999] [<ffffffff8105c062>] rcu_lock_acquire+0x6a/0xc5
[ 0.418005] [<ffffffff8158e6c4>] __atomic_notifier_call_chain+0x2c/0x62
[ 0.418009] [<ffffffff8158e709>] atomic_notifier_call_chain+0xf/0x11
[ 0.418014] [<ffffffff81000771>] enter_idle+0x20/0x22
[ 0.418018] [<ffffffff81000821>] cpu_idle+0x73/0xf9
[ 0.418024] [<ffffffff81b6b7ca>] start_secondary+0x9a/0x9c
[ 0.418068] ---[ end trace 4eaa2a86a8e2da22 ]---
[ 0.418070] ------------[ cut here ]------------
[ 0.418074] WARNING: at include/linux/rcupdate.h:262 rcu_lock_release+0x66/0xb1()
[ 0.418077] Hardware name: Latitude E6500
[ 0.418079] Modules linked in:
[ 0.418083] Pid: 0, comm: kworker/0:0 Tainted: G W 3.0.0-rc5-mmotm0630 #1
[ 0.418085] Call Trace:
[ 0.418089] [<ffffffff810383f6>] warn_slowpath_common+0x7e/0x96
[ 0.418093] [<ffffffff81038423>] warn_slowpath_null+0x15/0x17
[ 0.418097] [<ffffffff8105c123>] rcu_lock_release+0x66/0xb1
[ 0.418102] [<ffffffff8158e6eb>] __atomic_notifier_call_chain+0x53/0x62
[ 0.418106] [<ffffffff8158e709>] atomic_notifier_call_chain+0xf/0x11
[ 0.418110] [<ffffffff81000771>] enter_idle+0x20/0x22
[ 0.418114] [<ffffffff81000821>] cpu_idle+0x73/0xf9
[ 0.418119] [<ffffffff81b6b7ca>] start_secondary+0x9a/0x9c
[ 0.418122] ---[ end trace 4eaa2a86a8e2da23 ]---
[ 0.424803] Switched to NOHz mode on CPU #0
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
reply other threads:[~2011-07-05 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=61640.1309904282@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®