Date: Mon, 24 Apr 2017 16:55:41 -0700 From: Navdeep Parhar <np@FreeBSD.org> To: Joe Jones <joe@stream-technologies.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: cxgbe netmap promiscuous mode? Message-ID: <2529e545-fdca-eb51-3290-d5ecbc81ffcb@FreeBSD.org> In-Reply-To: <58F782DA.6060007@stream-technologies.com> References: <58D3C6F4.6010500@stream-technologies.com> <CAPFoGT-F86Y-yxEK03rmmJkr0LbP4ocgq27pqw3g=yqkdud4=Q@mail.gmail.com> <58D521C0.1000804@stream-technologies.com> <CAPFoGT9EFNcjpjszMVyGhB7ktKG2ir-srG5noPziPK=4mbXj_g@mail.gmail.com> <58F0E683.7050806@stream-technologies.com> <20170414163215.GA9358@ox> <58F49246.801@stream-technologies.com> <20170419001836.GA4461@ox> <58F72DE2.40503@stream-technologies.com> <20170419143745.GB4461@ox> <58F782DA.6060007@stream-technologies.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/19/2017 08:31, Joe Jones wrote:
> Hi Navdeep,
>
> I already got rid of the hw.cxgbe.num_vis line in loader.conf when I
> rebooted this morning.
>
> dev.t5nex.0.firmware_version: 1.15.37.0
I tried this exact firmware and was able to reproduce the problem. This
appears to be a firmware bug that has already been fixed in the 1.16.x
firmware available in 10-STABLE.
Regards,
Navdeep
>
>
> On 19/04/17 15:37, Navdeep Parhar wrote:
>> What is the firmware version?
>>
>> # sysctl dev.t5nex.0.firmware_version
>>
>> I'll try to repeat the experiment with a T520-SO with the firmware that
>> you have on your card. Does the card behave this way if the extra VIs
>> are not created? Can you please try without hw.cxgbe.num_vis in
>> loader.conf?
>>
>> Regards,
>> Navdeep
>>
>> On Wed, Apr 19, 2017 at 10:29:06AM +0100, Joe Jones wrote:
>>> uname -a
>>> FreeBSD goose2 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11
>>> 08:48:40 UTC 2017
>>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>>>
>>> The card is a 'T520-SO Unified Wire Ethernet Controller'
>>>
>>> I ran the following with dtrace running in a separate window
>>>
>>> ifconfig cxl1 promisc up ( only see broadcast)
>>> ifconfig cxl1 -promisc
>>> ifconfig cxl1 promisc (now I see traffic)
>>>
>>> dtrace output was
>>>
>>> [root@goose2 /usr/home/joe]# dtrace -n 'fbt::t4_set_rxmode:entry
>>> {trace(arg4)}'
>>> dtrace: description 'fbt::t4_set_rxmode:entry ' matched 1 probe
>>> CPU ID FUNCTION:NAME
>>> 4 61078 t4_set_rxmode:entry 1
>>> 7 61078 t4_set_rxmode:entry 0
>>> 5 61078 t4_set_rxmode:entry 1
>>>
>>>
>>> On 19/04/17 01:18, Navdeep Parhar wrote:
>>>> On Mon, Apr 17, 2017 at 11:00:38AM +0100, Joe Jones wrote:
>>>>> Hi Navdeep
>>>>>
>>>>> running "ifconfig up" and then "ifconfig promisc" works. Running
>>>>> "ifconfig
>>>>> promisc" and then "ifconfig up" does not work. Running "ifconfig up
>>>>> promisc"
>>>>> together does work. Running "ifconfig promisc up" does not work.
>>>> What version of FreeBSD is this? I couldn't reproduce this on head
>>>> with
>>>> a T6 card. Can you please run this in parallel with your ifconfig
>>>> commands, note what dtrace logs in response to what command(s), and
>>>> send
>>>> the output to me?
>>>>
>>>> # dtrace -n 'fbt::t4_set_rxmode:entry {trace(arg4)}'
>>>>
>>>>> The combination that does not work leaves the interface in a state
>>>>> where it
>>>>> reports it's self as being in promiscuous mode.
>>>> In my experiments the interface did function in promiscuous mode
>>>> whether
>>>> I did "ifconfig cc0 promisc up" or "ifconfig cc0 up promisc".
>>>>
>>>> Regards,
>>>> Navdeep
>>> _______________________________________________
>>> freebsd-net@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-net
>>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2529e545-fdca-eb51-3290-d5ecbc81ffcb>