From: Dhaval Giani <dhaval.giani@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>, Nick Piggin <npiggin@suse.de>
Subject: Re: [ANNOUNCE] 2.6.33.6-rt26
Date: Tue, 13 Jul 2010 18:52:18 +0200 [thread overview]
Message-ID: <AANLkTin5dJXFZyfKxuM6p2aR30U1P5m0v2mDHGwygOR8@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1007131745230.3321@localhost.localdomain>
Hi,
> Enjoy !
>
I hit this with rt26. (Quite possible is on vanilla as well, will
build a kernel soemtime soon and try)
=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.33.6-rt26 #36
-------------------------------------------------------
iperf/1629 is trying to acquire lock:
(slock-AF_INET){+.+...}, at: [<ffffffff8135a4fa>] release_sock+0x30/0x108
but task is already holding lock:
(&lock->lock){+.+...}, at: [<ffffffff813cd6cc>] ipt_do_table+0x118/0x650
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&lock->lock){+.+...}:
[<ffffffff810697e7>] lock_acquire+0xd6/0xfa
[<ffffffff813fcfaa>] rt_spin_lock+0x31/0x38
[<ffffffffa00ba8ef>] nf_nat_get_offset+0x42/0x6b [nf_nat]
[<ffffffff8138b2ba>] tcp_packet+0x659/0xd5b
[<ffffffff81387eb9>] nf_conntrack_in+0x445/0x4fc
[<ffffffff813ca933>] ipv4_conntrack_local+0x3b/0x44
[<ffffffff81384c22>] nf_iterate+0x41/0x84
[<ffffffff81384cd8>] nf_hook_slow+0x73/0xdb
[<ffffffff813970b4>] nf_hook_thresh.clone.0+0x3c/0x45
[<ffffffff81397136>] __ip_local_out+0x79/0x7b
[<ffffffff81397149>] ip_local_out+0x11/0x22
[<ffffffff81397407>] ip_push_pending_frames+0x2ad/0x30b
[<ffffffff81398a41>] ip_send_reply+0x21a/0x259
[<ffffffff813acdf1>] tcp_v4_send_reset+0x1c8/0x1eb
[<ffffffff813b0367>] tcp_v4_rcv+0x500/0x661
[<ffffffff8139400a>] ip_local_deliver_finish+0x14d/0x1c3
[<ffffffff813940f2>] ip_local_deliver+0x72/0x7c
[<ffffffff81393ac3>] ip_rcv_finish+0x31a/0x346
[<ffffffff81393d29>] ip_rcv+0x23a/0x268
[<ffffffff81366862>] netif_receive_skb+0x3fa/0x424
[<ffffffffa023fb41>] br_handle_frame_finish+0x105/0x13d [bridge]
[<ffffffffa023fd08>] br_handle_frame+0x18f/0x1a7 [bridge]
[<ffffffff81366792>] netif_receive_skb+0x32a/0x424
[<ffffffff813669d4>] napi_skb_finish+0x24/0x3b
[<ffffffff81366e83>] napi_gro_receive+0x2a/0x2f
[<ffffffff812d03b9>] sky2_poll+0x86e/0xaef
[<ffffffff81366fcc>] net_rx_action+0xa3/0x1f1
[<ffffffff81044a02>] run_ksoftirqd+0x14e/0x254
[<ffffffff8105975f>] kthread+0x88/0x90
[<ffffffff81009844>] kernel_thread_helper+0x4/0x10
-> #0 (slock-AF_INET){+.+...}:
[<ffffffff8106941a>] __lock_acquire+0x9f1/0xce8
[<ffffffff810697e7>] lock_acquire+0xd6/0xfa
[<ffffffff813fcfaa>] rt_spin_lock+0x31/0x38
[<ffffffff8135a4fa>] release_sock+0x30/0x108
[<ffffffff813a012a>] tcp_recvmsg+0x8b8/0x9a3
[<ffffffff81359864>] sock_common_recvmsg+0x37/0x48
[<ffffffff81357178>] __sock_recvmsg+0x6d/0x78
(Just run iperf as server and test it from another system)
thanks,
Dhaval
next prev parent reply other threads:[~2010-07-13 16:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner
2010-02-24 22:38 ` Peter Zijlstra
2010-02-25 22:56 ` Peter Zijlstra
2010-02-26 19:44 ` Dan Carpenter
2010-02-27 8:10 ` Thomas Gleixner
2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner
2010-02-27 9:25 ` Xavier Miller
2010-02-27 10:10 ` GeunSik Lim
2010-02-27 11:53 ` Thomas Gleixner
2010-03-02 21:25 ` Fernando Lopez-Lezcano
2010-03-02 21:53 ` Thomas Gleixner
2010-02-27 9:50 ` GeunSik Lim
2010-03-12 10:44 ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner
2010-03-12 12:17 ` 2.6.33-rt6 on Beagle Chatterjee, Amit
2010-03-15 9:20 ` Uwe Kleine-König
2010-03-15 11:23 ` What's the best way to create an embedded version of PREEMPT_RT Linux ? Armin Steinhoff
2010-03-21 11:06 ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner
2010-04-07 14:24 ` [ANNOUNCE] 2.6.33.2-rt13 Thomas Gleixner
2010-04-27 15:52 ` [ANNOUNCE] 2.6.33.3-rt16 Thomas Gleixner
2010-04-30 10:00 ` [ANNOUNCE] 2.6.33.3-rt17 Thomas Gleixner
2010-05-02 19:18 ` [ANNOUNCE] 2.6.33.3-rt19 Thomas Gleixner
2010-06-09 16:44 ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner
2010-06-09 21:31 ` Will Schmidt
2010-06-10 6:07 ` Thomas Gleixner
2010-06-10 15:56 ` Will Schmidt
2010-06-10 16:05 ` Darcy L. Watkins
2010-06-14 13:33 ` Thomas Gleixner
2010-06-14 13:34 ` Thomas Gleixner
2010-06-14 15:35 ` Will Schmidt
2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner
2010-07-13 16:52 ` Dhaval Giani [this message]
2010-07-13 18:04 ` Philipp Überbacher
2010-07-13 19:13 ` Darcy L. Watkins
2010-07-13 19:23 ` Philipp Überbacher
2010-07-14 13:47 ` Thomas Gleixner
2010-07-14 13:57 ` Ng Oon-Ee
2010-07-14 14:27 ` John Kacur
[not found] ` <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com>
2010-07-15 5:25 ` Yang Jian
2010-07-15 11:45 ` Philipp Überbacher
2010-07-19 6:37 ` Barry Song
2010-07-31 13:33 ` [ANNOUNCE] 2.6.33.6-rt27 Thomas Gleixner
2010-08-03 9:23 ` [ANNOUNCE] 2.6.33.7-rt29 Thomas Gleixner
2010-12-21 13:52 ` Thomas Gleixner
2010-12-21 15:01 ` Mark Knecht
2010-12-21 15:48 ` Madovsky
2010-12-21 16:39 ` Dennis Borgmann
2010-12-22 16:38 ` Madovsky
2010-12-22 20:20 ` Remy Bohmer
2010-12-24 22:36 ` Fernando Lopez-Lezcano
2010-12-31 19:56 ` Fernando Lopez-Lezcano
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=AANLkTin5dJXFZyfKxuM6p2aR30U1P5m0v2mDHGwygOR8@mail.gmail.com \
--to=dhaval.giani@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.de \
/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).