From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: BUG: sleeping function called from invalid context at kernel/mutex.c:271
Date: Mon, 16 Apr 2012 13:27:24 +0600 [thread overview]
Message-ID: <1334561244.3339.7.camel@aep-desktop> (raw)
Hello.
With linux-3.3.0, my computer at work is rather unstable. The kernel
seems to leak memory, however, kmemleak finds nothing significant.
Finally, the computer started swapping heavily and responded only via
ssh. In dmesg, I found this (repeated every two seconds):
[ 6709.483956] BUG: sleeping function called from invalid context at
kernel/mutex.c:271
[ 6709.483968] in_atomic(): 0, irqs_disabled(): 0, pid: 1210, name:
NetworkManager
[ 6709.483974] INFO: lockdep is turned off.
[ 6709.483981] Pid: 1210, comm: NetworkManager Tainted: G I
3.3.0-gentoo #4
[ 6709.483987] Call Trace:
[ 6709.484006] [<ffffffff810683fc>] __might_sleep+0xff/0x103
[ 6709.484019] [<ffffffff81548783>] mutex_lock_nested+0x2a/0x2ff
[ 6709.484031] [<ffffffff811261b5>] ? fget_light+0x6a/0x118
[ 6709.484043] [<ffffffff8115a738>] inotify_poll+0x35/0x53
[ 6709.484052] [<ffffffff81135eb1>] do_sys_poll+0x266/0x3f2
[ 6709.484060] [<ffffffff81134e33>] ? poll_freewait+0x8f/0x8f
[ 6709.484069] [<ffffffff81134efa>] ? __pollwait+0xc7/0xc7
[ 6709.484076] [<ffffffff81134efa>] ? __pollwait+0xc7/0xc7
[ 6709.484084] [<ffffffff81134efa>] ? __pollwait+0xc7/0xc7
[ 6709.484092] [<ffffffff81134efa>] ? __pollwait+0xc7/0xc7
[ 6709.484099] [<ffffffff81134efa>] ? __pollwait+0xc7/0xc7
[ 6709.484107] [<ffffffff81134efa>] ? __pollwait+0xc7/0xc7
[ 6709.484118] [<ffffffff8112fde0>] ? putname+0x2d/0x36
[ 6709.484127] [<ffffffff8112fde0>] ? putname+0x2d/0x36
[ 6709.484138] [<ffffffff81045cb7>] ? timespec_add_safe+0x32/0x5f
[ 6709.484146] [<ffffffff81018078>] ? read_tsc+0x9/0x1b
[ 6709.484155] [<ffffffff8113509a>] ? poll_select_set_timeout+0x61/0x75
[ 6709.484163] [<ffffffff811360d8>] sys_poll+0x4e/0xb7
[ 6709.484173] [<ffffffff81552896>] sysenter_dispatch+0x7/0x21
The taint is due to nouveau. I am sure that this
"sleeping-in-invalid-context" report is a consequence of the memory leak
that I could not convert into something reportable. But still, it is
something that the kernel wants me to report, that's why this e-mail.
The kernel is configured as CONFIG_PREEMPT=y, if this is relevant.
--
Alexander E. Patrakov
next reply other threads:[~2012-04-16 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 7:27 Alexander E. Patrakov [this message]
2012-04-18 2:56 ` BUG: sleeping function called from invalid context at kernel/mutex.c:271 Steven Rostedt
2012-04-18 4:06 ` Paul E. McKenney
2012-04-18 4:51 ` Alexander E. Patrakov
2012-04-18 12:08 ` Steven Rostedt
2012-04-18 13:45 ` Alexander E. Patrakov
2012-04-18 13:48 ` Steven Rostedt
2012-04-18 15:21 ` Alexander E. Patrakov
2012-04-18 16:19 ` Alexander E. Patrakov
2012-04-18 13:51 ` Paul E. McKenney
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=1334561244.3339.7.camel@aep-desktop \
--to=patrakov@gmail.com \
--cc=linux-kernel@vger.kernel.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.