On Wed, 10 May 2017, Paul Goyette wrote:
ISTR that wm(4) has one or more bugs concerning flow control. It's
possible that when flow control is negotiated, the MAC is not set up to
respect flow control signals, so it keeps sends frames to the peer after
it is asked to pause. With all buffers
On Tue, 9 May 2017, David Young wrote:
On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote:
Well, I got a little bit of a problem...
My new fiber-to-the-home router only has one RJ45 port available, so
I had to get a switch to connect all of the hard-wired network
devices. It all
On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote:
> Well, I got a little bit of a problem...
>
> My new fiber-to-the-home router only has one RJ45 port available, so
> I had to get a switch to connect all of the hard-wired network
> devices. It all seems to work, except for one
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2017.05.10.02.46.33.
An extract from the build.sh output follows:
^
Updating src tree:
P src/bin/sh/eval.c
P src/bin/sh/jobs.c
P src/bin/sh/nodetypes
P src/bin/sh/parser.c
P src/bin/sh/show.c
P src/distrib/sets/lists/base/shl.mi
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/debug/shl.mi
P src/include/signal.h
P src/lib/libc/shlib_version
P
On Tue, May 09, 2017 at 11:05:19PM -0400, Thor Lancelot Simon wrote:
> On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote:
> >
> > So, what is the magic incantation to set the interface to 100TX FDX, but
> > with flow/pause disabled?
>
> You can't. Or, more rightly, you can't do it
On Wed, May 10, 2017 at 09:35:44AM +0800, Paul Goyette wrote:
>
> So, what is the magic incantation to set the interface to 100TX FDX, but
> with flow/pause disabled?
You can't. Or, more rightly, you can't do it the way you probably want to.
If you explicitly set a speed and duplex, you will
Well, I got a little bit of a problem...
My new fiber-to-the-home router only has one RJ45 port available, so I
had to get a switch to connect all of the hard-wired network devices.
It all seems to work, except for one problem...
In the uplink direction, I can only push about 3.5Mb/sec,
On May 7, the NetBSD Test Fixture wrote:
> This is an automatically generated notice of new failures of the
> NetBSD test suite.
>
> The newly failing test cases are:
>
> lib/libc/sys/t_clone:clone_basic
> lib/libc/sys/t_clone:clone_null_func
There is also a new failure of
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2017.05.09.05.38.50 ozaki-r src/sys/netipsec/key.c,v 1.122
Log files can be found at:
10 matches
Mail list logo