From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, baryluk@smp.if.uj.edu.pl,
bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 42754] New: BUG: sleeping function called from invalid context at mm/memory.c:3924
Date: Fri, 10 Feb 2012 16:38:02 +0100 [thread overview]
Message-ID: <1328888282.25989.5.camel@laptop> (raw)
In-Reply-To: <20120209191317.2fbad57b.akpm@linux-foundation.org>
On Thu, 2012-02-09 at 19:13 -0800, Andrew Morton wrote:
> > [ 1203.050623] BUG: sleeping function called from invalid context at
> > mm/memory.c:3924
> > [ 1203.054259] in_atomic(): 1, irqs_disabled(): 0, pid: 4446, name:
> > NetworkManager
> > [ 1203.057932] INFO: lockdep is turned off.
This here should have been a listing of all held locks when this
happened, however due to an earlier error lockdep has already been
disabled (means it stops tracking state and printing anything would be
printing nonsense).
This suggests this isn't the first error hit.
> > [ 1203.061685] Pid: 4446, comm: NetworkManager Tainted: G W O
> > 3.3.0-rc2-t43-devel-smp-00172-g23783f8 #13
> > [ 1203.065606] Call Trace:
> > [ 1203.069502] [<c107e182>] __might_sleep+0x122/0x1d0
> > [ 1203.073506] [<c1140b4e>] might_fault+0x2e/0xb0
> > [ 1203.077501] [<c131c67b>] copy_to_user+0x3b/0x60
> > [ 1203.081561] [<c158a102>] put_cmsg+0x52/0xd0
> > [ 1203.085624] [<c15bc7d7>] netlink_recvmsg+0x287/0x340
> > [ 1203.089740] [<c1579b43>] sock_recvmsg+0xd3/0x110
> > [ 1203.093902] [<c1140b74>] ? might_fault+0x54/0xb0
> > [ 1203.098093] [<c158834c>] ? verify_iovec+0x4c/0xc0
> > [ 1203.102336] [<c1579a70>] ? sock_sendmsg_nosec+0x100/0x100
> > [ 1203.106611] [<c157a994>] __sys_recvmsg+0x114/0x1e0
> > [ 1203.110942] [<c1081dc7>] ? finish_task_switch+0x77/0x200
> > [ 1203.115315] [<c11784b5>] ? fget_light+0xc5/0x410
> > [ 1203.119722] [<c1081dc7>] ? finish_task_switch+0x77/0x200
> > [ 1203.124167] [<c11784c9>] ? fget_light+0xd9/0x410
> > [ 1203.128618] [<c1178435>] ? fget_light+0x45/0x410
> > [ 1203.133102] [<c157c659>] sys_recvmsg+0x39/0x60
> > [ 1203.137590] [<c157cbb3>] sys_socketcall+0x2e3/0x330
> > [ 1203.142147] [<c17cf58d>] ? sysenter_exit+0xf/0x1a
> > [ 1203.146707] [<c131be78>] ? trace_hardirqs_on_thunk+0xc/0x10
> > [ 1203.151358] [<c17cf558>] sysenter_do_call+0x12/0x38
> Peter, is there any way in which lockdep can help us find the culprit
> in the second case?
prev parent reply other threads:[~2012-02-10 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42754-27@https.bugzilla.kernel.org/>
2012-02-10 3:13 ` [Bug 42754] New: BUG: sleeping function called from invalid context at mm/memory.c:3924 Andrew Morton
2012-02-10 12:26 ` Witold Baryluk
2012-02-10 15:39 ` Peter Zijlstra
2012-02-10 16:30 ` Francois Romieu
2012-02-12 17:50 ` Paul E. McKenney
2012-02-15 13:02 ` Peter Zijlstra
2012-02-16 15:10 ` Witold Baryluk
2012-02-16 15:24 ` Eric Dumazet
2012-02-10 15:38 ` Peter Zijlstra [this message]
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=1328888282.25989.5.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=baryluk@smp.if.uj.edu.pl \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox