From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jkvossen@vossen.org>
Received: from mail.tds.net (smtp-fo.tds.net [64.8.70.105])
 by dpdk.org (Postfix) with ESMTP id B6DE3569C
 for <dev@dpdk.org>; Fri, 20 Mar 2015 18:54:03 +0100 (CET)
X_CMAE_Category: , ,
X-CNFS-Analysis: v=2.1 cv=JbiorC6V c=1 sm=1 tr=0
 a=zDUj20tEDmPq8qaMnVvhOg==:117 a=zDUj20tEDmPq8qaMnVvhOg==:17 a=K-v-2zaBAAAA:8
 a=kj9zAlcOel0A:10 a=txOcFob-AAAA:8 a=I0B4NdSXHbBvPIysUG8A:9 a=CjuIK1q_8ugA:10
X-CM-Score: 0
X-Scanned-by: Cloudmark Authority Engine
X-Authed-Username: amt2b3NzZW5AdGRzLm5ldA==
Authentication-Results: smtp01.tds.cmh.synacor.com smtp.user=jkvossen@tds.net;
 auth=pass (LOGIN)
Received: from [184.60.119.24] ([184.60.119.24:6294] helo=[10.0.1.17])
 by mail.tds.net (envelope-from <jkvossen@vossen.org>)
 (ecelerity 3.6.5.45644 r(Core:3.6.5.0)) with ESMTPSA (cipher=AES128-SHA) 
 id F2/02-21578-ABE5C055; Fri, 20 Mar 2015 13:54:02 -0400
From: Joseph Vossen <jkvossen@vossen.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Mar 2015 13:53:59 -0400
Message-Id: <B6FAFC94-7B71-4433-8595-6E0E601CEB87@vossen.org>
To: dev@dpdk.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Subject: [dpdk-dev] soft lockup calling receive burst
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bford@vossen.org
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2015 17:54:04 -0000

hello,

I am working on a dpdk-based app using version 1.6 under RH7.3.  Under =
varying traffic loads, I will intermittently notice a kernel soft lockup =
and the RIP provided by the kernel always points to the same MOV =
instruction in rte_ethdev.h (line #1982).  The stack trace looks like:


		dev =3D &rte_eth_devices[port_id];
		return =
(*dev->rx_pkt_burst)(dev->data->rx_queues[queue_id], rx_pkts, nb_pkts);


		473176:	0f b7 15 a7 68 38 00		movzwl =
0x3868a7(%rip),%edx	# 7f9a24 <max_rx_burst> rte_eth_rx_burst():
		47317d:	0f b6 31				movzbl =
(%rcx),%esi
		473180:	48 89 f0				mov =
%rsi,%rax
		473183:	0f b6 71 01			movzbl =
0x1(%rcx),%esi
		473187:	48 c1 e0 06			shl $0x6,%rax
		47318b:	48 8b b8 70 ed 83 00		mov =
0x83ed70(%rax),%rdi
	---->	473192:	48 8b 0f				mov =
(%rdi),%rcx
		473195:	48 8b 3c f1				mov =
(%rcx,%rsi,8),%rdi
		473199:	4c 89 ee				mov =
%r13,%rsi
		47319c:	ff 90 60 ed 83 00		callq =
*0x83ed60(%rax)


has any one else seen something like this?

thanks=