From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: BUG: sleeping function called from invalid context at drivers/cpufreq/cpufreq.c:370
Date: Fri, 26 Sep 2014 09:54:00 +0200 [thread overview]
Message-ID: <1411718040.6005.18.camel@marge.simpson.net> (raw)
In-Reply-To: <1411712697.6005.7.camel@marge.simpson.net>
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 ---------------------
index 0e27844e8c2d..e5122f1bfe78 100644
@@ -122,7 +122,7 @@ static int integrator_set_target(struct cpufreq_policy *policy,
return 0;
}
- cpufreq_notify_transition(policy, &freqs, CPUFREQ_PRECHANGE);
+ cpufreq_freq_transition_begin(policy, &freqs);
cm_osc = __raw_readl(cm_base + INTEGRATOR_HDR_OSC_OFFSET);
@@ -143,7 +143,7 @@ static int integrator_set_target(struct cpufreq_policy *policy,
*/
set_cpus_allowed(current, cpus_allowed);
- cpufreq_notify_transition(policy, &freqs, CPUFREQ_POSTCHANGE);
+ cpufreq_freq_transition_end(policy, &freqs, 0);
return 0;
}
> On Thu, 2014-09-25 at 15:59 +0200, Mike Galbraith wrote:
>
> > pcc-cpufreq: spin_lock() -> wait_event() -> gripe() gripe() gripe()...
> >
> > [ 50.756280] BUG: sleeping function called from invalid context at drivers/cpufreq/cpufreq.c:370
> > [ 50.850582] in_atomic(): 1, irqs_disabled(): 0, pid: 2636, name: modprobe
> > [ 50.926744] Preemption disabled at:[<ffffffffa04d74d7>] pcc_cpufreq_target+0x27/0x200 [pcc_cpufreq]
> > [ 51.025044]
> > [ 51.045454] CPU: 57 PID: 2636 Comm: modprobe Tainted: G E 3.17.0-default #7
> > [ 51.136727] Hardware name: Hewlett-Packard ProLiant DL980 G7, BIOS P66 07/07/2010
> > [ 51.218484] 00000000ffffffff ffff88026c46b828 ffffffff81589dbd 0000000000000000
> > [ 51.300293] ffff880037978090 ffff88026c46b848 ffffffff8108e1df ffff880037978090
> > [ 51.382666] 0000000000000000 ffff88026c46b878 ffffffff8108e298 ffff88026d73ec00
> > [ 51.464884] Call Trace:
> > [ 51.495159] [<ffffffff81589dbd>] dump_stack+0x4d/0x90
> > [ 51.555439] [<ffffffff8108e1df>] ___might_sleep+0x10f/0x180
> > [ 51.620610] [<ffffffff8108e298>] __might_sleep+0x48/0xd0
> > [ 51.684774] [<ffffffff8145b905>] cpufreq_freq_transition_begin+0x75/0x140 drivers/cpufreq/cpufreq.c:370 wait_event(policy->transition_wait, !policy->transition_ongoing);
> > [ 51.767992] [<ffffffff8108fc99>] ? preempt_count_add+0xb9/0xc0
> > [ 51.833294] [<ffffffffa04d7513>] pcc_cpufreq_target+0x63/0x200 [pcc_cpufreq] drivers/cpufreq/pcc-cpufreq.c:207 spin_lock(&pcc_lock);
> > [ 51.930204] [<ffffffff810e0d0f>] ? update_ts_time_stats+0x7f/0xb0
> > [ 52.009288] [<ffffffff8145be55>] __cpufreq_driver_target+0x85/0x170
> > [ 52.082479] [<ffffffff8145e4c8>] od_check_cpu+0xa8/0xb0
> > [ 52.143874] [<ffffffff8145ef10>] dbs_check_cpu+0x180/0x1d0
> > [ 52.207329] [<ffffffff8145f310>] cpufreq_governor_dbs+0x3b0/0x720
> > [ 52.276916] [<ffffffff8145ebe3>] od_cpufreq_governor_dbs+0x33/0xe0
> > [ 52.349048] [<ffffffff814593d9>] __cpufreq_governor+0xa9/0x210
> > [ 52.415040] [<ffffffff81459fb2>] cpufreq_set_policy+0x1e2/0x2e0
> > [ 52.480473] [<ffffffff8145a6cc>] cpufreq_init_policy+0x8c/0x110
> > [ 52.545829] [<ffffffff8145c9a0>] ? cpufreq_update_policy+0x1b0/0x1b0
> > [ 52.615796] [<ffffffff8108fb99>] ? preempt_count_sub+0xb9/0x100
> > [ 52.681961] [<ffffffff8145c6c6>] __cpufreq_add_dev+0x596/0x6b0
> > [ 52.746288] [<ffffffffa016c608>] ? pcc_cpufreq_probe+0x4b4/0x4b4 [pcc_cpufreq]
> > [ 52.830472] [<ffffffff8145c7ee>] cpufreq_add_dev+0xe/0x10
> > [ 52.894106] [<ffffffff81408e81>] subsys_interface_register+0xc1/0xf0
> > [ 52.970763] [<ffffffff8108fb99>] ? preempt_count_sub+0xb9/0x100
> > [ 53.038953] [<ffffffff8145b3d7>] cpufreq_register_driver+0x117/0x2a0
> > [ 53.110751] [<ffffffffa016c65d>] pcc_cpufreq_init+0x55/0x9f8 [pcc_cpufreq]
> > [ 53.186920] [<ffffffffa016c608>] ? pcc_cpufreq_probe+0x4b4/0x4b4 [pcc_cpufreq]
> > [ 53.267583] [<ffffffff81000298>] do_one_initcall+0xc8/0x1f0
> > [ 53.330601] [<ffffffff811a731d>] ? __vunmap+0x9d/0x100
> > [ 53.388285] [<ffffffff810eb9a0>] do_init_module+0x30/0x1b0
> > [ 53.451958] [<ffffffff810edfa6>] load_module+0x686/0x710
> > [ 53.514007] [<ffffffff810ebb20>] ? do_init_module+0x1b0/0x1b0
> > [ 53.581246] [<ffffffff810ee1db>] SyS_init_module+0x9b/0xc0
> > [ 53.644024] [<ffffffff8158f7a9>] system_call_fastpath+0x16/0x1b
> >
>
>
next prev parent reply other threads:[~2014-09-26 7:54 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 [this message]
2014-09-26 14:10 ` Rafael J. Wysocki
2014-09-26 22:44 ` Rafael J. Wysocki
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=1411718040.6005.18.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.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 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).