9.2 ixgbe tx queue hang

[Markus Gebert]

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

> Markus,
> 
> 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:
> 
> 

This is expected. This dtrace probe will fire if any kernel function that is run in the context of a process named “ping” 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’s 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 at hostpoint.ch>wrote:
> 
>> 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.
>> 
>> 
>> 
>> 
>> 
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>