From: Dave Jones <davej@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: lockdep splat in CPU hotplug
Date: Tue, 21 Oct 2014 11:10:43 -0400 [thread overview]
Message-ID: <20141021151043.GA11800@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1410211255531.24255@pobox.suse.cz>
On Tue, Oct 21, 2014 at 01:09:04PM +0200, Jiri Kosina wrote:
> Hi,
>
> I am seeing the lockdep report below when resuming from suspend-to-disk
> with current Linus' tree (c2661b80609).
>
> The reason for CCing Ingo and Peter is that I can't make any sense of one
> of the stacktraces lockdep is providing.
>
> Please have a look at the very first stacktrace in the dump, where lockdep
> is trying to explain where cpu_hotplug.lock#2 has been acquired. It seems
> to imply that cpuidle_pause() is taking cpu_hotplug.lock, but that's not
> the case at all.
Could inlining be confusing the trace here ?
You can get from cpuidle_pause to cpuidle_uninstall_idle_handler -> synchronize_rcu
-> synchronize_sched -> synchronize_sched_expedited which
does a try_get_online_cpus which will take the cpu_hotplug.lock
Dave
next prev parent reply other threads:[~2014-10-21 15:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 11:09 lockdep splat in CPU hotplug Jiri Kosina
2014-10-21 14:58 ` Steven Rostedt
2014-10-21 15:04 ` Jiri Kosina
2014-10-22 18:37 ` Steven Rostedt
2014-10-22 18:40 ` Jiri Kosina
2014-10-22 18:46 ` Borislav Petkov
2014-10-21 15:10 ` Dave Jones [this message]
2014-10-21 15:21 ` Jiri Kosina
2014-10-21 16:00 ` Paul E. McKenney
2014-10-21 16:04 ` Jiri Kosina
2014-10-21 16:23 ` Paul E. McKenney
2014-10-22 9:53 ` Jiri Kosina
2014-10-22 11:39 ` Jiri Kosina
2014-10-22 14:28 ` Daniel Lezcano
2014-10-22 14:36 ` Jiri Kosina
2014-10-22 14:45 ` Daniel Lezcano
2014-10-22 14:38 ` Paul E. McKenney
2014-10-22 16:54 ` Paul E. McKenney
2014-10-22 18:57 ` Paul E. McKenney
2014-10-22 20:57 ` Jiri Kosina
2014-10-22 21:09 ` Paul E. McKenney
2014-10-23 8:11 ` Borislav Petkov
2014-10-23 14:56 ` Paul E. McKenney
2014-10-22 16:59 ` Steven Rostedt
2014-10-22 17:26 ` Jiri Kosina
2014-10-24 14:33 ` Peter Zijlstra
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=20141021151043.GA11800@redhat.com \
--to=davej@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
/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).