From: Stephen Boyd <sboyd@codeaurora.org>
To: Dave Jones <davej@codemonkey.org.uk>,
Viresh Kumar <viresh.kumar@linaro.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: cpufreq/ondemand: unpinning an unpinned lock.
Date: Tue, 21 Jul 2015 17:46:16 -0700 [thread overview]
Message-ID: <55AEE7D8.3000507@codeaurora.org> (raw)
In-Reply-To: <20150716124241.GA20320@codemonkey.org.uk>
On 07/16/2015 05:42 AM, Dave Jones wrote:
> On Thu, Jul 16, 2015 at 10:41:50AM +0530, Viresh Kumar wrote:
>
> > > > WARNING: CPU: 1 PID: 29529 at kernel/locking/lockdep.c:3497 lock_unpin_lock+0x109/0x110()
> > > > unpinning an unpinned lock
> > > > CPU: 1 PID: 29529 Comm: kworker/1:1 Not tainted 4.2.0-rc2-think+ #3
> > > > Workqueue: events od_dbs_timer
> > > > 0000000000000009 ffff880094d5baa8 ffffffffae7f5e6f 0000000000000007
> > > > ffff880094d5baf8 ffff880094d5bae8 ffffffffae07b91a 0000000000000118
> > > > 00000000000000e0 ffff880507bd5c58 0000000000000092 0000000000000004
> > > > Call Trace:
> > > > [<ffffffffae7f5e6f>] dump_stack+0x4f/0x7b
> > > > [<ffffffffae07b91a>] warn_slowpath_common+0x8a/0xc0
> > > > [<ffffffffae07b996>] warn_slowpath_fmt+0x46/0x50
> > > > [<ffffffffae0d0ec9>] lock_unpin_lock+0x109/0x110
> > > > [<ffffffffae7f93cc>] __schedule+0x3ac/0xb60
> > > > [<ffffffffae7f9c41>] schedule+0x41/0x90
> > > > [<ffffffffae7f9ff8>] schedule_preempt_disabled+0x18/0x30
> > > > [<ffffffffae7fbcef>] mutex_lock_nested+0x16f/0x3e0
> > > > [<ffffffffae69207f>] ? gov_queue_work+0x2f/0xf0
> > > > [<ffffffffae690ec7>] ? od_check_cpu+0x57/0xd0
> > > > [<ffffffffae69207f>] ? gov_queue_work+0x2f/0xf0
> > > > [<ffffffffae69207f>] gov_queue_work+0x2f/0xf0
> > > > [<ffffffffae6918dd>] od_dbs_timer+0xbd/0x150
> >
> > I don't know why this will happen. Just to confirm, you are getting
> > this over 4.2-rc(1 or 2)? And you weren't getting these on 4.1 at all?
> > And its always reproducible? How ?
>
> I've hit it once, on rc2. I didn't have a lot of time for testing rc1.
Lock pinning is new in v4.2-rc1. Adding Peter just in case there's some
insight.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-07-22 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 22:04 cpufreq/ondemand: unpinning an unpinned lock Dave Jones
2015-07-16 0:13 ` Rafael J. Wysocki
2015-07-16 5:11 ` Viresh Kumar
2015-07-16 12:42 ` Dave Jones
2015-07-22 0:46 ` Stephen Boyd [this message]
2015-07-22 9:02 ` 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=55AEE7D8.3000507@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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 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.