Automated report: NetBSD-current/i386 build failure

2017-05-22 Thread NetBSD Test Fixture
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.23.03.23.58. An extract from the build.sh output follows: --- rscreate.d --- #create

daily CVS update output

2017-05-22 Thread NetBSD source update
Updating src tree: P src/lib/libedit/chartype.h P src/share/man/man4/rum.4 P src/share/mk/bsd.lib.mk P src/sys/arch/arm/arm32/pmap.c P src/sys/arch/vax/bi/bi_mainbus.c P src/sys/arch/vax/bi/bi_nmi.c P src/sys/arch/vax/boot/boot/autoconf.c P src/sys/arch/vax/boot/boot/conf.c P

Re: disabling mediaopts for if_wm(4)

2017-05-22 Thread Paul Goyette
On Thu, 11 May 2017, Paul Goyette wrote: FWIW, the re(4) situation is worse - very much worse! The re(4) negotiates 100BaseTX with no mediaopts at all, neither full nor half, and no flow-control. It took a couple of minutes before dhcpcd could configure the interface and even then it was

Re: re0 watchdog timeouts

2017-05-22 Thread Patrick Welche
On Wed, May 17, 2017 at 11:49:38PM -0700, Soren Jacobsen wrote: > On 05/17 14:21, Patrick Welche wrote: > > On Wed, May 17, 2017 at 01:12:14PM +, Jared McNeill wrote: > > > Are you able to get performance numbers before/after this set of > > > changes? It has a noticeable impact on my arm