daily CVS update output

2016-10-18 Thread NetBSD source update
Updating src tree: P src/crypto/external/bsd/openssl/lib/libcrypto/arch/powerpc/Makefile P src/distrib/sets/lists/comp/ad.mips P src/distrib/sets/lists/comp/md.emips P src/distrib/sets/lists/xserver/md.sgimips P src/external/gpl3/binutils/dist/ld/configure.tgt P src/lib/libperfuse/fuse.h P

Wapbl correct and stable again?

2016-10-18 Thread bch
Yesterday I had an unclean shutdown while ./build.sh distribution (battery on laptop died). On reboot i had corrupted files similar to other week after wapbl refactor. Could wapbl stand to have more demanding testing thrown at it? Can we simulate unclean shutdown with vn file-based filesystem and

Automated report: NetBSD-current/i386 build success

2016-10-18 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2016.10.18.17.56.31 christos src/lib/libperfuse/fuse.h,v 1.7 2016.10.18.17.56.31 christos src/lib/libperfuse/perfuse.c,v 1.39 2016.10.18.17.56.31

Automated report: NetBSD-current/i386 build failure

2016-10-18 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 2016.10.18.15.10.35. An extract from the build.sh output follows:

Assert on shutdown

2016-10-18 Thread coypu
In case this is interesting. I'm not sure if I can reproduce it yet acpibut0: power button pressed, shutting down! syncing disks... 4 done unmounted /dev/sd2a on /mnt type msdos unmounted tmpfs on /var/shm type tmpfs unmounted procfs on /proc type procfs unmounted kernfs on /kern type kernfs sd0:

Re: WANTED: nvme(4) driver testing on MP systems on -current

2016-10-18 Thread Masanobu SAITOH
nic: ioWsAtRNatI_NWG:Au nRSNPILN GbNuO:Ts  SLPOyLW E RN -> panic: iostat_unbust -> WARNINWG:A RSNPILN GNO:T  SLPOLW E RN -> WARNING: SPL NOT LOWER -> WARNING: SPL N The full dmesg is at: http://www.netbsd.org/~msaitoh/nvme-20161018-0.log Any test co