daily CVS update output

2018-03-20 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/comp/ad.aarch64 P src/distrib/sets/lists/comp/ad.arm P src/share/man/man4/altq.4 P src/share/man/man9/altq.9 P src/sys/arch/aarch64/include/armreg.h P src/sys/arch/amd64/amd64/amd64_trap.S P src/sys/arch/amd64/amd64/locore.S P src/sys/arch/arm/include/Ma

Automated report: NetBSD-current/i386 test failure

2018-03-20 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libc/sys/t_recvmmsg:recvmmsg_basic The above test failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The following commits we

Re: failure to build distribution

2018-03-20 Thread Riccardo Mottola
Hi, Martin Husemann wrote: On Sun, Mar 18, 2018 at 10:08:52PM +0100, Riccardo Mottola wrote: Hi, when I try to build distribution, I get an issue in X: all ===> external/mit/xorg/tools/bdftopcf check src/UPDATING: 20180311: bdftopcf was updated and may need cleaning in the

Re: nfs client issue at netbsd-8

2018-03-20 Thread 6bone
On Tue, 20 Mar 2018, Martin Husemann wrote: Which network driver is used on the client? ixg0 at pci8 dev 0 function 0: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k ixg0: device 82599EB ixg0: ETrackID 830d ixg0: for TX/RX, interrupting at msix0 vec 0, bound queue 0 to

Re: nfs client issue at netbsd-8

2018-03-20 Thread Martin Husemann
On Tue, Mar 20, 2018 at 10:20:08AM +0100, 6b...@6bone.informatik.uni-leipzig.de wrote: > Are there any ideas which mount option can be the problem? Is it possible to > eliminate the problem with a configuration change or is it a bug? Which network driver is used on the client? Martin

nfs client issue at netbsd-8

2018-03-20 Thread 6bone
Hello, I have problems with the nfs-client under netbsd-8. In principle, the nfs works. Some time after an nfs share is mounted, there are network breaks on the client. The following ping from the outside on the client shows the phenomenon. ... 64 bytes from 139.18.xx.yy: icmp_seq=6496 ttl=

Re: uefi boot attempt

2018-03-20 Thread Kimihiro Nonaka
Hi, 2018-03-19 3:38 GMT+09:00 Patrick Welche : > On a -current/amd64 box which normally boots a raidframe softroot via > bios, I added a disk, and attempted a uefi boot with it. > >2048 524288 1 GPT part - EFI System > 5263362097152 2 GPT part - NetBSD FFSv1/FFSv2

Re: raidframe oddity

2018-03-20 Thread Patrick Welche
On Tue, Mar 20, 2018 at 08:54:13AM +0100, Martin Husemann wrote: > On Mon, Mar 19, 2018 at 05:36:26PM +, Patrick Welche wrote: > > Seems it is widespread: just updated another box to 8.99.14/amd64, and > > see (raid 1): > > Indeed, it is broken for me as well: > > # raidctl -s raid0 > Compone

Re: raidframe oddity

2018-03-20 Thread Martin Husemann
On Tue, Mar 20, 2018 at 08:54:13AM +0100, Martin Husemann wrote: > On Mon, Mar 19, 2018 at 05:36:26PM +, Patrick Welche wrote: > > Seems it is widespread: just updated another box to 8.99.14/amd64, and > > see (raid 1): > > Indeed, it is broken for me as well: > > # raidctl -s raid0 > Compone

Re: raidframe oddity

2018-03-20 Thread Martin Husemann
On Mon, Mar 19, 2018 at 05:36:26PM +, Patrick Welche wrote: > Seems it is widespread: just updated another box to 8.99.14/amd64, and > see (raid 1): Indeed, it is broken for me as well: # raidctl -s raid0 Components: /dev/sd0a: optimal /dev/sd1a: optimal No spares. Compo