From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.14.2] Debug: sleeping function called from invalid context at mm/slab.c:2459
Date: Mon, 14 Nov 2005 20:30:21 +0100 [thread overview]
Message-ID: <20051114193021.GA15010@janus> (raw)
2.6.14.2 on a AMD Athlon X2 3800
Nov 14 20:17:30 iapetus kernel: in_atomic():1, irqs_disabled():0
Nov 14 20:17:30 iapetus kernel: [<c010410e>] dump_stack+0x1e/0x20
Nov 14 20:17:30 iapetus kernel: [<c01211c5>] __might_sleep+0xa5/0xb0
Nov 14 20:17:30 iapetus kernel: [<c01512cd>] __kmalloc+0xdd/0x100
Nov 14 20:17:30 iapetus kernel: [<c041d8bd>] pskb_expand_head+0x4d/0x150
Nov 14 20:17:30 iapetus kernel: [<c043bbc7>] netlink_broadcast+0x387/0x3c0
Nov 14 20:17:30 iapetus kernel: [<c04a4673>] nfnetlink_send+0x63/0xa0
Nov 14 20:17:30 iapetus kernel: [<c0484d20>] ctnetlink_conntrack_event+0x3a0/0xac0
Nov 14 20:17:30 iapetus kernel: [<c013239d>] notifier_call_chain+0x2d/0x50
Nov 14 20:17:30 iapetus kernel: [<c047fadb>] destroy_conntrack+0x12b/0x190
Nov 14 20:17:30 iapetus kernel: [<c0480b35>] ip_conntrack_in+0x1a5/0x360
Nov 14 20:17:30 iapetus kernel: [<c047eda6>] ip_conntrack_local+0x66/0x70
Nov 14 20:17:30 iapetus kernel: [<c04a2fd8>] nf_iterate+0x68/0xb0
Nov 14 20:17:30 iapetus kernel: [<c04a308d>] nf_hook_slow+0x6d/0x140
Nov 14 20:17:30 iapetus kernel: [<c04460ab>] ip_queue_xmit+0x47b/0x5f0
Nov 14 20:17:30 iapetus kernel: [<c0457402>] tcp_transmit_skb+0x442/0x6e0
Nov 14 20:17:30 iapetus kernel: [<c0459fb7>] tcp_connect+0x2f7/0x380
Nov 14 20:17:30 iapetus kernel: [<c045c0c7>] tcp_v4_connect+0x627/0xb70
Nov 14 20:17:30 iapetus kernel: [<c046bddd>] inet_stream_connect+0x7d/0x1a0
Nov 14 20:17:30 iapetus kernel: [<c0419328>] sys_connect+0x78/0xa0
Nov 14 20:17:30 iapetus kernel: [<c0419db3>] sys_socketcall+0xa3/0x240
Nov 14 20:17:30 iapetus kernel: [<c01031fb>] sysenter_past_esp+0x54/0x75
--
Frank
reply other threads:[~2005-11-14 19:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051114193021.GA15010@janus \
--to=frankvm@frankvm.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.