From owner-freebsd-net@FreeBSD.ORG Thu Mar 20 20:05:23 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D42D87EA for ; Thu, 20 Mar 2014 20:05:23 +0000 (UTC) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 93E75B25 for ; Thu, 20 Mar 2014 20:05:23 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id w7so1664998qcr.22 for ; Thu, 20 Mar 2014 13:05:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9tYhD43R7RKD6VljbOAp9fsTegFok4nYMyFAiw8CFfM=; b=g86OFqqb1b5f79vFYVVMxSIEaowcvmV4zFhPlZ8HEcsWTJ3llR6CLrGDJjqInpim5D gipuLdM8K9tTcUmYeAeiqdMbYmQaRe+p0p3mqBccjQgBD8BlUzX4TBrYDi0Z4mvpICGf +qwLGLolp28vNaeQSkG/DDkB2T9IA8vdPTERvUjpnuGFLObYf4/3cCOpuGDIdXokZLeD oUfbmOMim5IrHgZsg6r2tEZEfQ4oO32N2zIBXnkPqFPjCn2ISuWETOWBCHPgttMsHWoI sPh1Sb/cRgutRLH/hWWCWmbhGB8NY/RYlUcgrh+zCY5zoKY1RmObeuj8fLDxSj89J2Va fCOQ== MIME-Version: 1.0 X-Received: by 10.224.123.7 with SMTP id n7mr571055qar.18.1395345922844; Thu, 20 Mar 2014 13:05:22 -0700 (PDT) Received: by 10.96.79.97 with HTTP; Thu, 20 Mar 2014 13:05:22 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Mar 2014 17:05:22 -0300 Message-ID: Subject: Re: 9.2 ixgbe tx queue hang From: Christopher Forgeron To: Markus Gebert Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-net@freebsd.org, Rick Macklem , Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Mar 2014 20:05:24 -0000 Re: cpuset ping I can report that I do not get any fails with this ping - I have screens of failed flood pings on the ix0 nic, but these always pass (i have that cpuset ping looping constantly). I can't report about the dtrace yet, as I'm running Rick's ixgbe patch, and there seems to be a .ko conflict someplace that keeps dtrace from running. I'm going to try locking my flood pings down to specific CPU's to see if there is any pattern there. After that I'll restore GENERIC and try the dtrace line. On Thu, Mar 20, 2014 at 7:40 AM, Markus Gebert wrote: > > > Can you try this when the problem occurs? > > for CPU in {0..7}; do echo "CPU${CPU}"; cpuset -l ${CPU} ping -i 0.2 -c 2 > -W 1 10.0.0.1 | grep sendto; done > > It will tie ping to certain cpus to test the different tx queues of your > ix interface. If the pings reliably fail only on some queues, then your > problem is more likely to be the same as ours. > > Also, if you have dtrace available: > > kldload dtraceall > dtrace -n 'fbt:::return / arg1 == EFBIG && execname == "ping" / { stack(); > }' > > while you run pings over the interface affected. This will give you hints > about where the EFBIG error comes from. > > > [...] > > > Markus > > >