Intel 82567V-2 using em driver, no carrier or constant link-state changes with 1000BaseT

2016-11-27 Thread Michael Knap 
Preface: I've been a long-time linux user, and I am enjoying the BSD
experience. For the following scenario, I have reproduced these results
with 3 or more cables which are known to be good.

Using FreeBSD 10.3 Stable :
FreeBSD 10.3-STABLE #0 r295946+07c41cd(9.10-STABLE): Wed Nov  9 00:19:25
UTC 2016 root@gauntlet
:/freenas-9.10-releng/_BE/objs/freenas-9.10-releng/_BE/os/sys/FreeNAS.amd64

Also, this isn't a NIC, per se, as it is onboard, but I will call it a NIC
or card or whatever.

Using em driver, though I don't know how to determine a driver version (if
there is such a thing).

Basically, the card will not push gigabit, though it will work with
100BaseTX. However, there seems to be more than just that as the chip-set
is advertised as a gigabit Ethernet controller.

When connected to a 100BaseTX switch, everything is good. Leaving it in
autodetect mode, and connecting to a 1000baseTX switch (with good CAT6
cable), the card's link state oscillates from link up and link down:

Nov 27 13:07:38 freenas kernel: em0: link state changed to DOWN
Nov 27 13:07:38 freenas kernel: em0: link state changed to DOWN
Nov 27 13:07:41 freenas kernel: em0: link state changed to UP
Nov 27 13:07:41 freenas kernel: em0: link state changed to UP
Nov 27 13:07:41 freenas kernel: em0: link state changed to DOWN
Nov 27 13:07:41 freenas kernel: em0: link state changed to DOWN
Nov 27 13:07:55 freenas kernel: em0: link state changed to UP
Nov 27 13:07:55 freenas kernel: em0: link state changed to UP
Nov 27 13:07:56 freenas kernel: em0: link state changed to DOWN
Nov 27 13:07:56 freenas kernel: em0: link state changed to DOWN
Nov 27 13:07:58 freenas kernel: em0: link state changed to UP
Nov 27 13:07:58 freenas kernel: em0: link state changed to UP
Nov 27 13:07:59 freenas kernel: em0: link state changed to DOWN
Nov 27 13:07:59 freenas kernel: em0: link state changed to DOWN
Nov 27 13:08:01 freenas kernel: em0: link state changed to UP
Nov 27 13:08:01 freenas kernel: em0: link state changed to UP
Nov 27 13:08:02 freenas kernel: em0: link state changed to DOWN
Nov 27 13:08:02 freenas kernel: em0: link state changed to DOWN

If I issue  ifconfig em0 media 100baseTX mediaopt full-duplex, then I have
no carrier.
Also, ifconfig em0 media 1000baseT gives no carrier.
However, if I ifconfig em0 media 10baseT, then I can get an active link.

Interestingly, man em(4) does not claim to support this chipset, though it
seems that this chipset was once supported in either e1000 or igb for older
freeBSD versions?

Now, at least from the driver's POV, I should be able to handle gigabit, as

ifconfig -m em0
em0: flags=8c02 metric 0 mtu 1500
options=4219b
capabilities=5399b
ether 00:25:11:59:d4:be
inet 10.42.0.111 netmask 0xff00 broadcast 10.42.0.255
nd6 options=9
media: Ethernet 10baseT/UTP (10baseT/UTP )
status: active
supported media:
media autoselect
media 1000baseT
media 1000baseT mediaopt full-duplex
media 100baseTX mediaopt full-duplex
media 100baseTX
media 10baseT/UTP mediaopt full-duplex
media 10baseT/UTP

However when connected to gigabit switch, any explicit declaration of media
fails except for 10baseT, even the autoselect declaration fails with no
carrier.

But remember, 100baseTX works out of the box on a 100Mbit switch.

So, those more experienced, can you shed some light on what is happening?
I'm especially interested in the man em(4) result even though the chipset
has been supported in the past, and intel does provide drivers for this
chipset, though I'm not sure if I could compile them or not. BTW, my
switches are only consumer grade, unmanaged. Is that where I'm stuck?

Thanks for such an awesome license, operating system, and community.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 214832] if_pflog subrulenr incorrectly set

2016-11-27 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214832

Sean Bruno  changed:

   What|Removed |Added

 CC||b...@freebsd.org,
   ||k...@freebsd.org,
   ||sbr...@freebsd.org

--- Comment #2 from Sean Bruno  ---
Adding folks who have done stuff/things in pf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Problem reports for freebsd-net@FreeBSD.org that need special attention

2016-11-27 Thread bugzilla-noreply 
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |203422 | mpd/ppoe not working with re(4) with revision 285 
In Progress |206581 | bxe_ioctl_nvram handler is faulty 
New |204438 | setsockopt() handling of kern.ipc.maxsockbuf limi 
New |205592 | TCP processing in IPSec causes kernel panic   
New |206053 | kqueue support code of netmap causes panic
Open|193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc 
Open|194485 | Userland cannot add IPv6 prefix routes
Open|194515 | Fatal Trap 12 Kernel with vimage  
Open|199136 | [if_tap] Added down_on_close sysctl variable to t 
Open|206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; 
Open|211031 | [panic] in ng_uncallout when argument is NULL 
Open|211962 | bxe driver queue soft hangs and flooding tx_soft_ 
Open|212018 | Enable IPSEC_NAT_T in GENERIC kernel configuratio 

13 problems total for which you should take action.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Mellanox ConnectX/X2/X3 OFED module for FreeBSD 11.x

2016-11-27 Thread Frank DiMitri 
Mellanox has no driver for cards earlier than ConnectX4 available for FreeBSD 
11.x at the moment.



What I have right now is a quick hack to get the 2.1.6 driver for 10.1 to 
compile and work under 11.0. It needs some polishing, but it does work. I 
didn't do anything for the InfiniBand side, only the Ethernet/core.



https://github.com/fdimitri/Mellanox-OFED-ConnectX-FreeBSD11



For anyone looking to run these cards under FreeBSD 11.0, this should work at 
the least in the interim. The only non-functional part under 11.0-release-p1 
are the counters available through sysctl (hw.mlxenX.stat) for packet sizes ie 
in_gt_1548.



Hopefully this is the right place to send this.



Is there a reason the OFED drivers aren't in-tree? They are dual-licensed under 
GPL and BSD.



Thanks,

Frank DiMitri



___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

RE: Mellanox ConnectX/X2/X3 OFED module for FreeBSD 11.x

2016-11-27 Thread Meny Yossefi 
Hi,



Not sure how did you reach that conclusion.



We have an updated 11.x inbox driver for ConnectX-3 under /sys/ofed/



Eth: /sys/ofed/drivers/net/mlx4

InfiniBand: /sys/ofed/drivers/infiniband/..



We have recently (12-CURRENT) moved the ConnectX-3 driver to /sys/dev



We'll be happy to assist in case you have more questions.



-Meny





From: owner-freebsd-net@freebsd.orgOn 
Behalf OfFrank DiMitri

Sent: Monday, November 28, 2016 1:50:18 AM (UTC+00:00) Monrovia, Reykjavik

To: freebsd-net@freebsd.org

Subject: Mellanox ConnectX/X2/X3 OFED module for FreeBSD 11.x



Mellanox has no driver for cards earlier than ConnectX4 available for FreeBSD 
11.x at the moment.







What I have right now is a quick hack to get the 2.1.6 driver for 10.1 to 
compile and work under 11.0. It needs some polishing, but it does work. I 
didn't do anything for the InfiniBand side, only the Ethernet/core.







https://github.com/fdimitri/Mellanox-OFED-ConnectX-FreeBSD11







For anyone looking to run these cards under FreeBSD 11.0, this should work at 
the least in the interim. The only non-functional part under 11.0-release-p1 
are the counters available through sysctl (hw.mlxenX.stat) for packet sizes ie 
in_gt_1548.







Hopefully this is the right place to send this.







Is there a reason the OFED drivers aren't in-tree? They are dual-licensed under 
GPL and BSD.







Thanks,



Frank DiMitri







___

freebsd-net@freebsd.org mailing list

https://lists.freebsd.org/mailman/listinfo/freebsd-net

To unsubscribe, send any mail to 
"freebsd-net-unsubscr...@freebsd.org"
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

RE: Mellanox ConnectX/X2/X3 OFED module for FreeBSD 11.x

2016-11-27 Thread Frank DiMitri 
Meny,



Amazingly enough I completely missed that, and nobody was able to point me to 
them. I was unaware of any in-tree Mellanox drivers.



My (embarrassing) mistake, glad to see they're in the kernel by default.



Thanks!




 On Sun, 27 Nov 2016 22:00:26 -0800 Meny Yossefi  
wrote 




Hi, 

 

 

 

Not sure how did you reach that conclusion. 

 

 

 

We have an updated 11.x inbox driver for ConnectX-3 under /sys/ofed/ 

 

 

 

Eth: /sys/ofed/drivers/net/mlx4 

 

InfiniBand: /sys/ofed/drivers/infiniband/.. 

 

 

 

We have recently (12-CURRENT) moved the ConnectX-3 driver to /sys/dev 

 

 

 

We'll be happy to assist in case you have more questions. 

 

 

 

-Meny 

 

 

 

 

 

From: 
owner-freebsd-net@freebsd.orgOn; 
Behalf OfFrank DiMitri 

 

Sent: Monday, November 28, 2016 1:50:18 AM (UTC+00:00) Monrovia, Reykjavik 

 

To: freebsd-net@freebsd.org; 

 

Subject: Mellanox ConnectX/X2/X3 OFED module for FreeBSD 11.x 

 

 

 

Mellanox has no driver for cards earlier than ConnectX4 available for FreeBSD 
11.x at the moment. 

 

 

 

 

 

 

 

What I have right now is a quick hack to get the 2.1.6 driver for 10.1 to 
compile and work under 11.0. It needs some polishing, but it does work. I 
didn't do anything for the InfiniBand side, only the Ethernet/core. 

 

 

 

 

 

 

 

https://github.com/fdimitri/Mellanox-OFED-ConnectX-FreeBSD11 

 

 

 

 

 

 

 

For anyone looking to run these cards under FreeBSD 11.0, this should work at 
the least in the interim. The only non-functional part under 11.0-release-p1 
are the counters available through sysctl (hw.mlxenX.stat) for packet sizes ie 
in_gt_1548. 

 

 

 

 

 

 

 

Hopefully this is the right place to send this. 

 

 

 

 

 

 

 

Is there a reason the OFED drivers aren't in-tree? They are dual-licensed under 
GPL and BSD. 

 

 

 

 

 

 

 

Thanks, 

 

 

 

Frank DiMitri 

 

 

 

 

 

 

 

___ 

 

freebsd-net@freebsd.org; mailing list 

 

https://lists.freebsd.org/mailman/listinfo/freebsd-net 

 

To unsubscribe, send any mail to 
"freebsd-net-unsubscr...@freebsd.org";
 

___ 

freebsd-net@freebsd.org mailing list 

https://lists.freebsd.org/mailman/listinfo/freebsd-net 

To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" 






___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"