Hi!
There is some serios issue in kernel related to network interfaces.
See my message
"speedtest.net in multi connections mode causes the FreeBSD 13-CURRENT
router to crash"
from 28 aug 2020.
I noticed that kernel every time goes into panic if users run on client
computers in browser
speedt
Dear list,
I have done a few builds of CURRENT in a row one or two weeks apart. The
builds with CPUTYPE?=amdfam10 set produce buggy code, for example while
running mergemaster I get this error:
PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and
include the crash backtrace, preproc
On 26 Sep 2020, at 13:40, Marek Zarychta wrote:
>
> I have done a few builds of CURRENT in a row one or two weeks apart. The
> builds with CPUTYPE?=amdfam10 set produce buggy code, for example while
> running mergemaster I get this error:
>
> PLEASE submit a bug report to https://bugs.freebsd.or
Steffen Nurpmeso wrote in
<20200903191410.sgjuq%stef...@sdaoden.eu>:
|For one: thanks all, it now works!
|
|Steffen Nurpmeso wrote in
| <20200903151825.g_rv9%stef...@sdaoden.eu>:
||Renato Botelho wrote in
|| :
|||On 02/09/20 20:20, Steffen Nurpmeso wrote:
|||> Ed Maste wrote in
|||> :
On Sat, Sep 26, 2020 at 05:48:33PM +0200, Dimitry Andric wrote:
> On 26 Sep 2020, at 13:40, Marek Zarychta
> wrote:
> >
> > I have done a few builds of CURRENT in a row one or two weeks apart. The
> > builds with CPUTYPE?=amdfam10 set produce buggy code, for example while
> > running mergemaster
I know cross-posting is frowned upon, but I wanted everyone who might
like to comment to see this.
Currently copy_file_range(2) only supports regular files, which is compatible
with the Linux one, where EINVAL is returned when either file descriptor
refers to a non-regular file.
Alan Somers would
Wall, Stephen wrote:
> Could the as yet unused options param have a bit assigned to trigger the new
> behavior? Inform the linux community of the addition and let them decide if
> they
> would like to adopt it as well.
I'll assume you are referring to the "flags" argument when you say "param"
a
On Sat, Sep 26, 2020 at 8:52 PM Rick Macklem wrote:
> Wall, Stephen wrote:
> > Could the as yet unused options param have a bit assigned to trigger the
> new
> > behavior? Inform the linux community of the addition and let them
> decide if they
> > would like to adopt it as well.
> I'll assume y
