public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 3.19 scheduler might_sleep triggered from module loading during boot.
Date: Tue, 10 Feb 2015 11:42:17 -0500	[thread overview]
Message-ID: <20150210164217.GA5547@codemonkey.org.uk> (raw)

I don't recall seeing this one until now..

	Dave

[    3.559609] WARNING: CPU: 0 PID: 181 at kernel/sched/core.c:7326 __might_sleep+0xd0/0xf0()
[    3.559701] do not call blocking ops when !TASK_RUNNING; state=1 set at [<ffffffff950e1db3>] prepare_to_wait_event+0x93/0x1f0
[    3.559800] CPU: 0 PID: 181 Comm: modprobe Not tainted 3.19.0+ #5
[    3.559932]  ffffffff950b75b0 ffff88020da3fba8 ffffffff9573726a ffffffff95101ec3
[    3.560174]  ffff88020da3fbf8 ffff88020da3fbe8 ffffffff950742f2 ffffffff964c1fa0
[    3.561927]  ffffffff95ad86e8 000000000000026d 0000000000000000 ffff88020da9aac0
[    3.562159] Call Trace:
[    3.562218]  [<ffffffff950b75b0>] ? __might_sleep+0xd0/0xf0
[    3.562288]  [<ffffffff9573726a>] dump_stack+0x84/0xb9
[    3.562359]  [<ffffffff95101ec3>] ? console_unlock+0x373/0x690
[    3.562431]  [<ffffffff950742f2>] warn_slowpath_common+0xd2/0x140
[    3.562495]  [<ffffffff95074457>] warn_slowpath_fmt+0x57/0x70
[    3.562569]  [<ffffffff950e1db3>] ? prepare_to_wait_event+0x93/0x1f0
[    3.562641]  [<ffffffff950e1db3>] ? prepare_to_wait_event+0x93/0x1f0
[    3.562728]  [<ffffffff950b75b0>] __might_sleep+0xd0/0xf0
[    3.562799]  [<ffffffff9573b9c1>] mutex_lock_nested+0x41/0x760
[    3.562870]  [<ffffffff950cb16d>] ? local_clock+0x4d/0x60
[    3.562933]  [<ffffffff957439ef>] ? _raw_spin_unlock_irqrestore+0x5f/0xc0
[    3.563009]  [<ffffffff9514e888>] resolve_symbol.isra.35+0x48/0x150
[    3.563081]  [<ffffffff951521b4>] load_module+0x1134/0x20b0
[    3.563149]  [<ffffffff953ed85e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[    3.563221]  [<ffffffff950e1570>] ? wait_woken+0x110/0x110
[    3.563290]  [<ffffffff95744ba0>] ? retint_restore_args+0xe/0xe
[    3.563359]  [<ffffffff95153262>] SyS_init_module+0x132/0x190
[    3.563433]  [<ffffffff95743f52>] system_call_fastpath+0x12/0x17


             reply	other threads:[~2015-02-10 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 16:42 Dave Jones [this message]
2015-02-10 17:06 ` [PATCH] module: Annotate nested sleep in resolve_symbol() Peter Zijlstra
2015-02-10 17:12   ` Peter Zijlstra
2015-02-10 17:50     ` Dave Jones
2015-02-10 23:48       ` Rusty Russell

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=20150210164217.GA5547@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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