From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, oleg@redhat.com, torvalds@linux-foundation.org,
tglx@linutronix.de, ilya.dryomov@inktank.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] nested sleeps, fixes and debug infrastructure
Date: Thu, 25 Sep 2014 11:56:59 +0200 [thread overview]
Message-ID: <1411639019.15810.31.camel@marge.simpson.net> (raw)
In-Reply-To: <20140925091556.GB5430@worktop>
On Thu, 2014-09-25 at 11:15 +0200, Peter Zijlstra wrote:
> I suppose just flipping the scheudle() and try_to_freeze() should do the
> trick. Ugly code that, but then again, I think audit is known for that.
>
> Can you give that a go?
Yeah, seems that fixed that one.
And thanks to my clever ratelimiting, printk() no longer goes gaga as it
emits this one.. forever. This boot is gonna take a while too :)
[ 53.951297] BUG: sleeping function called from invalid context at drivers/cpufreq/cpufreq.c:370
[ 54.044733] in_atomic(): 1, irqs_disabled(): 0, pid: 2676, name: modprobe
[ 54.120213] CPU: 42 PID: 2676 Comm: modprobe Tainted: G E 3.17.0-default #5
[ 54.212540] Hardware name: Hewlett-Packard ProLiant DL980 G7, BIOS P66 07/07/2010
[ 54.294917] 0000000000000000 ffff880273f83838 ffffffff815b2ff2 ffff880273f83848
[ 54.377182] ffffffff8108d156 ffff880273f83878 ffffffff8108d1d8 ffff88026e71e600
[ 54.459679] ffff880273f83898 ffff88026e71e748 ffff88026e71e744 ffff880273f838f8
[ 54.542107] Call Trace:
[ 54.573965] [<ffffffff815b2ff2>] dump_stack+0x72/0x88
[ 54.635104] [<ffffffff8108d156>] ___might_sleep+0xd6/0x110
[ 54.700956] [<ffffffff8108d1d8>] __might_sleep+0x48/0xd0
[ 54.765821] [<ffffffff8146c1d5>] cpufreq_freq_transition_begin+0x75/0x140
[ 54.842571] [<ffffffffa0548523>] pcc_cpufreq_target+0x63/0x208 [pcc_cpufreq]
[ 54.923403] [<ffffffff810dec5f>] ? update_ts_time_stats+0x7f/0xb0
[ 54.996678] [<ffffffff8146c725>] __cpufreq_driver_target+0x85/0x170
[ 55.067871] [<ffffffff8146ed98>] od_check_cpu+0xa8/0xb0
[ 55.126035] [<ffffffff8146f7c0>] dbs_check_cpu+0x180/0x1d0
[ 55.191425] [<ffffffff8146fbc0>] cpufreq_governor_dbs+0x3b0/0x720
[ 55.259809] [<ffffffff8146f493>] od_cpufreq_governor_dbs+0x33/0xe0
[ 55.329556] [<ffffffff81469cb9>] __cpufreq_governor+0xa9/0x210
[ 55.396925] [<ffffffff8146a892>] cpufreq_set_policy+0x1e2/0x2e0
[ 55.462852] [<ffffffff8146afac>] cpufreq_init_policy+0x8c/0x110
[ 55.462854] [<ffffffff8146d270>] ? cpufreq_update_policy+0x1b0/0x1b0
[ 55.462857] [<ffffffff8146cf96>] __cpufreq_add_dev+0x596/0x6b0
[ 55.462859] [<ffffffffa054d608>] ? pcc_cpufreq_probe+0x4b4/0x4b4 [pcc_cpufreq]
[ 55.462861] [<ffffffff8146d0be>] cpufreq_add_dev+0xe/0x10
[ 55.462863] [<ffffffff8140eef1>] subsys_interface_register+0xc1/0xf0
[ 55.462865] [<ffffffff8146bcb7>] cpufreq_register_driver+0x117/0x2a0
[ 55.462868] [<ffffffffa054d65d>] pcc_cpufreq_init+0x55/0x9f8 [pcc_cpufreq]
[ 55.462870] [<ffffffffa054d608>] ? pcc_cpufreq_probe+0x4b4/0x4b4 [pcc_cpufreq]
[ 55.462873] [<ffffffff81000298>] do_one_initcall+0xc8/0x1f0
[ 55.462875] [<ffffffff811a581d>] ? __vunmap+0x9d/0x100
[ 55.462877] [<ffffffff810e9680>] do_init_module+0x30/0x1b0
[ 55.462878] [<ffffffff810ebaaa>] load_module+0x67a/0x700
[ 55.462879] [<ffffffff810e9800>] ? do_init_module+0x1b0/0x1b0
[ 55.462881] [<ffffffff810ebcdb>] SyS_init_module+0x9b/0xc0
[ 55.462883] [<ffffffff815b86a9>] system_call_fastpath+0x16/0x1b
[ 55.463467] BUG: sleeping function called from invalid context at drivers/cpufreq/cpufreq.c:370
[ 55.463468] in_atomic(): 1, irqs_disabled(): 0, pid: 2676, name: modprobe
[ 55.463469] CPU: 42 PID: 2676 Comm: modprobe Tainted: G
next prev parent reply other threads:[~2014-09-25 9:57 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 [this message]
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
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=1411639019.15810.31.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=ilya.dryomov@inktank.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).