Skip site navigation (1)Skip section navigation (2) 
Date:      Thu, 20 Mar 2014 12:52:15 -0300
From:      Christopher Forgeron <csforgeron@gmail.com>
To:        Markus Gebert <markus.gebert@hostpoint.ch>
Cc:        freebsd-net@freebsd.org, Rick Macklem <rmacklem@uoguelph.ca>, Jack Vogel <jfvogel@gmail.com>
Subject:   Re: 9.2 ixgbe tx queue hang
Message-ID:  <CAB2_NwBA07jtFiFAxXRtMJ8s6-TC%2BAy0UEPpYFc-OLRfsx0b1A@mail.gmail.com>
In-Reply-To: <CAB2_NwDMbJP7ph786s=aJoo8Pfy7pz5mivt7HYzA12KZSZLZUg@mail.gmail.com>
References:  <CAB2_NwDG=gB1WCJ7JKTHpkJCrvPuAhipkn%2BvPyT%2BxXzOBrTGkg@mail.gmail.com> <FA262955-B3A9-48EC-828B-FF0D4D5D0498@hostpoint.ch> <CAB2_NwDMbJP7ph786s=aJoo8Pfy7pz5mivt7HYzA12KZSZLZUg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help 

(Struggling with this mail client for some reason, sorry, here's the paste)

# dtrace -n 'fbt:::return / arg1 == EFBIG && execname == "ping" / {
stack(); }'
dtrace: description 'fbt:::return ' matched 24892 probes
CPU     ID                    FUNCTION:NAME
 19  29656               maybe_yield:return
              kernel`uiomove_faultflag+0xab
              kernel`m_uiotombuf+0xfd
              kernel`sosend_generic+0x367
              kernel`kern_sendit+0x224
              kernel`sendit+0x116
              kernel`sys_sendto+0x4d
              kernel`amd64_syscall+0x357
              kernel`0xffffffff80c7567b

 19  29656               maybe_yield:return
              kernel`uiomove_faultflag+0xab
              kernel`ttydisc_write+0xde
              kernel`ttydev_write+0x143
              kernel`devfs_write_f+0xef
              kernel`dofilewrite+0x8a
              kernel`kern_writev+0x65
              kernel`sys_write+0x63
              kernel`amd64_syscall+0x357
              kernel`0xffffffff80c7567b

 11  29656               maybe_yield:return
              kernel`uiomove_faultflag+0xab
              kernel`m_uiotombuf+0xfd
              kernel`sosend_generic+0x367
              kernel`kern_sendit+0x224
              kernel`sendit+0x116
              kernel`sys_sendto+0x4d
              kernel`amd64_syscall+0x357
              kernel`0xffffffff80c7567b

 11  29656               maybe_yield:return
              kernel`uiomove_faultflag+0xab
              kernel`ttydisc_write+0xde
              kernel`ttydev_write+0x143
              kernel`devfs_write_f+0xef
              kernel`dofilewrite+0x8a
              kernel`kern_writev+0x65
              kernel`sys_write+0x63
              kernel`amd64_syscall+0x357
              kernel`0xffffffff80c7567b


On Thu, Mar 20, 2014 at 12:50 PM, Christopher Forgeron <csforgeron@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:
>
>
>
>
>
> On Thu, Mar 20, 2014 at 7:40 AM, Markus Gebert <markus.gebert@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.
>>
>>
>>
>>
>>
>

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB2_NwBA07jtFiFAxXRtMJ8s6-TC%2BAy0UEPpYFc-OLRfsx0b1A>