From: Viresh Kumar <viresh.kumar@linaro.org>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: rjw@rjwysocki.net, benh@kernel.crashing.org,
linux-pm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [lockdep] cpufreq/ppc: possible circular locking dependency detected
Date: Mon, 8 Jun 2015 22:02:28 +0530 [thread overview]
Message-ID: <20150608163228.GD4198@linux> (raw)
In-Reply-To: <CAOJe8K3Mtj9UMOYwjAuh7DYQxHR-ZLbEBAQJ+t3oSDphwu5+Hg@mail.gmail.com>
On 08-06-15, 18:45, Denis Kirjanov wrote:
> Hi,
>
> I see the following lockdep splat on my RackMac machine on boot:
What kernel version is it ?
--
viresh
next prev parent reply other threads:[~2015-06-08 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 15:45 [lockdep] cpufreq/ppc: possible circular locking dependency detected Denis Kirjanov
2015-06-08 16:32 ` Viresh Kumar [this message]
2015-06-08 16:37 ` Denis Kirjanov
2015-06-08 16:40 ` Viresh Kumar
2015-06-08 16:43 ` Denis Kirjanov
2015-06-08 21:10 ` Benjamin Herrenschmidt
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=20150608163228.GD4198@linux \
--to=viresh.kumar@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=kda@linux-powerpc.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).