From owner-freebsd-net@FreeBSD.ORG  Thu Mar 20 17:02:13 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 653FA67F
 for <freebsd-net@freebsd.org>; Thu, 20 Mar 2014 17:02:13 +0000 (UTC)
Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch
 [IPv6:2a00:d70:0:a::e0])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 21C92FA
 for <freebsd-net@freebsd.org>; Thu, 20 Mar 2014 17:02:13 +0000 (UTC)
Received: from [2001:1620:2013:1:4535:ed23:3991:6e11] (port=57438)
 by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128)
 (Exim 4.80.1 (FreeBSD)) (envelope-from <markus.gebert@hostpoint.ch>)
 id 1WQgM6-0001Hj-He; Thu, 20 Mar 2014 18:02:10 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: 9.2 ixgbe tx queue hang
From: Markus Gebert <markus.gebert@hostpoint.ch>
In-Reply-To: <CAB2_NwDMbJP7ph786s=aJoo8Pfy7pz5mivt7HYzA12KZSZLZUg@mail.gmail.com>
Date: Thu, 20 Mar 2014 18:01:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5D34624-EE94-417C-84DD-93207CDEF8DC@hostpoint.ch>
References: <CAB2_NwDG=gB1WCJ7JKTHpkJCrvPuAhipkn+vPyT+xXzOBrTGkg@mail.gmail.com>
 <FA262955-B3A9-48EC-828B-FF0D4D5D0498@hostpoint.ch>
 <CAB2_NwDMbJP7ph786s=aJoo8Pfy7pz5mivt7HYzA12KZSZLZUg@mail.gmail.com>
To: Christopher Forgeron <csforgeron@gmail.com>
X-Mailer: Apple Mail (2.1874)
Cc: freebsd-net@freebsd.org, Rick Macklem <rmacklem@uoguelph.ca>,
 Jack Vogel <jfvogel@gmail.com>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Mar 2014 17:02:13 -0000


On 20.03.2014, at 16:50, Christopher Forgeron <csforgeron@gmail.com> =
wrote:

> Markus,
>=20
> I just wanted to clarify what dtrace will output in a 'no-error'
> situation. I'm seeing the following during a normal ping (no errors) =
on
> ix0, or even on a non-problematic bge NIC:
>=20
>=20

This is expected. This dtrace probe will fire if any kernel function =
that is run in the context of a process named =93ping=94 returns 27, =
which is what EFBIG stands for. Kernel functions can return 27 for many =
reasons, not just an error, or they can return void (not sure how dtrace =
handles this case). Anyway, this dtrace one-liner is only meant to be =
used in the error case. Otherwise it=92s probably useless. And even when =
the problem occurs, you need to pick the right stack trace, and dig =
around kernel sources to verify that the functions indeed return EFBIG =
and not any integer that happens to be 27 by accident.


Markus


> On Thu, Mar 20, 2014 at 7:40 AM, Markus Gebert
> <markus.gebert@hostpoint.ch>wrote:
>=20
>> Also, if you have dtrace available:
>>=20
>> kldload dtraceall
>> dtrace -n 'fbt:::return / arg1 =3D=3D EFBIG && execname =3D=3D "ping" =
/ { stack();
>> }'
>>=20
>> while you run pings over the interface affected. This will give you =
hints
>> about where the EFBIG error comes from.
>>=20
>>=20
>>=20
>>=20
>>=20
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>=20