Try turning TSO off.. i.e. ifconfig igb3 -tso or sysctl net.inet.tcp.tso=0
The transition to iflib has exposed much jankiness in the Intel "shared
code" of the e1000 drivers. In particular, the locking contracts may not
align with FreeBSD locking primitives. I have boxes running the legacy
drive
Hi,
The DPRINTF macro in netmap-fwd is defined as #define *DPRINTF*(_fmt,
args...) if (verbose) dprintf(_fmt, ## args)
while dprintf is defined as dprintf(int fd, const char * restrict format,
...); in stdio.h
You could try, simplistically, to change DPRINTF macro to #define
*DPRINTF*(_fmt,
arg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #14 from Aiko Barz ---
Maybe nothing you like to hear, but I tried the pufferfish.
It is running for some days now without issues so far and it handles the
workload quite well. We cannot utilize the full 10Gbit/s at the moment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212018
Alex Dupre changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #7 from
FreeBSD 11 and prior, dprintf in stdio.h had to be specifically called
by setting particular defines.
These were removed in -CURRENT, which caused dprintf from
/usr/include/stdio.h to coflict with the declarations in netmap-fwd.
Commenting out the #define and the int dprintf statements in
netmap-f
On 03/24/2017 08:51 PM, Navdeep Parhar wrote:
> On 03/24/2017 16:53, Caraballo-vega, Jordan A. (GSFC-6062)[COMPUTER
> SCIENCE CORP] wrote:
>> It looks like netmap is there; however, is there a way of figuring out
>> if netmap is being used?
>
> If you're not running netmap-fwd or some other netmap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212018
--- Comment #8 from Andrey V. Elsukov ---
(In reply to Alex Dupre from comment #7)
> Does this mean that StrongSwan will finally work OOTB on FreeBSD 11.1? :-)
You can test and report. I have one report about panics with strongswan on
stab
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217721
--- Comment #7 from Pyun YongHyeon ---
(In reply to Eugene Lozovoy from comment #6)
Added Kevin(driver author) to CC list.
Let's see whether he has a better idea on the issue.
--
You are receiving this mail because:
You are the assignee f
