From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: BUG: sleeping function called from invalid context at drivers/cpufreq/cpufreq.c:370
Date: Sat, 27 Sep 2014 00:44:23 +0200 [thread overview]
Message-ID: <2457441.tHFXzSCneW@vostro.rjw.lan> (raw)
In-Reply-To: <1411718040.6005.18.camel@marge.simpson.net>
On Friday, September 26, 2014 09:54:00 AM Mike Galbraith wrote:
> On Fri, 2014-09-26 at 08:24 +0200, Mike Galbraith wrote:
> > (the hazards of multitasking.. post escaped early, and went to mostly
> > the wrong folks)
> >
> >
> > While testing some scheduler patches, the below pcc-cpufreq
> > might_sleep() gripe fell out.
>
> Because the bits below from 8fec051e didn't make the lock go away first.
> Reverting only pcc-cpufreq back to notifier.. works.
>
> --------------------- drivers/cpufreq/integrator-cpufreq.c ---------------------
Are you sure this is the right file?
Shouldn't that be pcc-cpufreq.c rather?
Also moving the spin_lock(&pcc_lock) after the cpufreq_freq_transition_begin()
should fix the problem too (like the below). Have you tried that?
---
drivers/cpufreq/pcc-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-pm/drivers/cpufreq/pcc-cpufreq.c
===================================================================
--- linux-pm.orig/drivers/cpufreq/pcc-cpufreq.c
+++ linux-pm/drivers/cpufreq/pcc-cpufreq.c
@@ -204,7 +204,6 @@ static int pcc_cpufreq_target(struct cpu
u32 input_buffer;
int cpu;
- spin_lock(&pcc_lock);
cpu = policy->cpu;
pcc_cpu_data = per_cpu_ptr(pcc_cpu_info, cpu);
@@ -216,6 +215,7 @@ static int pcc_cpufreq_target(struct cpu
freqs.old = policy->cur;
freqs.new = target_freq;
cpufreq_freq_transition_begin(policy, &freqs);
+ spin_lock(&pcc_lock);
input_buffer = 0x1 | (((target_freq * 100)
/ (ioread32(&pcch_hdr->nominal) * 1000)) << 8);
next prev parent reply other threads:[~2014-09-26 22:24 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 8:18 [PATCH 00/11] nested sleeps, fixes and debug infrastructure Peter Zijlstra
2014-09-24 8:18 ` [PATCH 01/11] locking/mutex: Dont assume TASK_RUNNING Peter Zijlstra
2014-10-28 11:09 ` [tip:sched/core] locking/mutex: Don't " tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 02/11] wait: Provide infrastructure to deal with nested blocking Peter Zijlstra
2014-09-29 21:02 ` Oleg Nesterov
2014-10-02 7:37 ` Peter Zijlstra
2014-10-02 21:21 ` Oleg Nesterov
2014-10-28 11:09 ` [tip:sched/core] sched/wait: " tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 03/11] wait: Add might_sleep() Peter Zijlstra
2014-10-28 11:09 ` [tip:sched/core] sched/wait: Add might_sleep() checks tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 04/11] exit: Deal with nested sleeps Peter Zijlstra
2014-10-28 11:10 ` [tip:sched/core] sched, " tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 05/11] inotify: " Peter Zijlstra
2014-10-28 11:10 ` [tip:sched/core] sched, " tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 06/11] tty: " Peter Zijlstra
2014-10-28 11:10 ` [tip:sched/core] sched, " tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 07/11] smp: Correctly deal " Peter Zijlstra
2014-10-28 11:11 ` [tip:sched/core] sched, " tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 08/11] module: Fix nested sleep Peter Zijlstra
2014-09-29 22:18 ` Oleg Nesterov
2014-09-30 13:43 ` Peter Zijlstra
2014-10-28 11:11 ` [tip:sched/core] sched, modules: Fix nested sleep in add_unformed_module() tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 09/11] net: Clean up sk_wait_event() vs might_sleep() Peter Zijlstra
2014-09-24 8:36 ` Peter Zijlstra
2014-10-28 11:11 ` [tip:sched/core] sched, net: Clean up sk_wait_event() vs. might_sleep() tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 10/11] sched: Debug nested sleeps Peter Zijlstra
2014-09-29 22:13 ` Oleg Nesterov
2014-09-30 13:49 ` Peter Zijlstra
2014-09-30 21:47 ` Oleg Nesterov
2014-10-01 16:10 ` Peter Zijlstra
2014-10-01 18:35 ` Oleg Nesterov
2014-10-02 9:07 ` Peter Zijlstra
2014-10-02 21:34 ` Oleg Nesterov
2014-10-28 11:11 ` [tip:sched/core] " tip-bot for Peter Zijlstra
2014-09-24 8:18 ` [PATCH 11/11] sched: Exclude cond_resched() from nested sleep test Peter Zijlstra
2014-10-28 11:12 ` [tip:sched/core] " tip-bot for Peter Zijlstra
2014-09-25 8:30 ` [PATCH 00/11] nested sleeps, fixes and debug infrastructure Mike Galbraith
2014-09-25 9:06 ` Peter Zijlstra
2014-09-25 9:10 ` Mike Galbraith
2014-09-25 9:15 ` Peter Zijlstra
2014-09-25 9:56 ` Mike Galbraith
2014-09-25 13:59 ` BUG: sleeping function called from invalid context at drivers/cpufreq/cpufreq.c:370 Mike Galbraith
2014-09-26 6:24 ` Mike Galbraith
2014-09-26 7:54 ` Mike Galbraith
2014-09-26 14:10 ` Rafael J. Wysocki
2014-09-26 22:44 ` Rafael J. Wysocki [this message]
2014-09-27 6:14 ` Mike Galbraith
2014-09-27 19:57 ` Rafael J. Wysocki
2014-10-02 10:22 ` [PATCH 00/11] nested sleeps, fixes and debug infrastructure Peter Zijlstra
2014-10-02 12:15 ` Peter Zijlstra
2014-10-27 13:41 ` Peter Zijlstra
2014-10-28 0:07 ` Oleg Nesterov
2014-10-28 8:23 ` Peter Zijlstra
2014-10-29 0:00 ` Oleg Nesterov
2014-10-29 9:35 ` Peter Zijlstra
2014-10-29 11:31 ` Peter Zijlstra
2014-10-29 11:36 ` Peter Zijlstra
2014-10-29 14:26 ` Peter Zijlstra
2014-11-04 16:08 ` [tip:sched/core] audit, sched/wait: Fixup kauditd_thread() wait loop tip-bot for 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=2457441.tHFXzSCneW@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=umgwanakikbuti@gmail.com \
--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 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®