Olav,
Does anything change if you set -tso -lro on the serving NIC on your
FreeBSD server side? Do the Linux clients remain responsive then?
I had seen something similar with a Ubuntu 20.04 client going to a
13.0-CURRENT/STABLE server but chalked it up to it starting around the time
of the last
On Nov 1, 2015 10:06 AM, "Boris Samorodov" wrote:
>
> 30.10.2015 23:57, Jung-uk Kim пишет:
>
> > OpenSSL on head has been updated to 1.0.2d. Please make sure to
> > recompile all binaries depending on libcrypto.so.7 or libssl.so.7.
>
> Great, thanks!
>
> How do those who use FreeBSD official pack
On Mon, Oct 12, 2015 at 4:16 PM, Pedro Giffuni wrote:
> Hello;
>
> On 12/10/2015 02:56 p.m., Justin Hibbits wrote:
>>
>> The default ports gcc for USE_GCC is still 4.8, which does not support
>> -fstack-protector-strong. This breaks several ports including (from
>> my poudriere run): libfpx and q
Evening,
I have a Soekris 6501 running i386 11-CURRENT that I had seen panic at
boot when updating this weekend. It'll panic right after the "SMP: AP
CPU #1 Launched" and go into a long loop of __mtx_lock_spin_flags,
i8254_get_timecount, binuptime, _mtx_lock_spin_cookie. An abbreviated
outp
e and mentioned in the PR. Both versions can be
fixed up the the patch in the PR. The latest 8.4-RELEASE still uses the
old way of doing things with an explict "rc=3" statement at the end so
that output never gets masked.
Best regards,
Jason Unovitch
smime.p7s
Description: S/MIME Cryptographic Signature
