daily CVS update output

2020-05-15 Thread NetBSD source update


Updating src tree:
P src/Makefile
P src/common/lib/libc/atomic/atomic_init_testset.c
P src/distrib/notes/common/legal.common
P src/distrib/sets/lists/base/shl.mi
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/comp/shl.mi
P src/distrib/sets/lists/debug/mi
P src/distrib/sets/lists/debug/shl.mi
P src/external/bsd/jemalloc/dist/src/jemalloc.c
P src/external/bsd/jemalloc/dist/src/mutex.c
P src/external/cddl/osnet/dev/profile/profile.c
P src/external/gpl3/gcc/lib/libgomp/Makefile
P src/external/gpl3/gcc/lib/liblsan/Makefile
P src/external/lgpl3/mpfr/lib/libmpfr/Makefile
P src/external/mpl/dhcp/dist/common/bpf.c
P src/external/mpl/dhcp/dist/common/discover.c
P src/external/mpl/dhcp/dist/common/lpf.c
P src/external/mpl/dhcp/dist/common/packet.c
P src/external/mpl/dhcp/dist/common/raw.c
P src/external/mpl/dhcp/dist/common/socket.c
P src/lib/libc/shlib_version
P src/lib/libc/gen/pthread_atfork.c
P src/lib/libc/include/extern.h
P src/lib/libc/stdlib/jemalloc.c
P src/lib/libc/stdlib/malloc.c
P src/lib/libpthread/pthread.c
P src/share/man/man4/adb.4
P src/share/mk/bsd.sys.mk
P src/sys/arch/aarch64/aarch64/cpufunc.c
P src/sys/arch/aarch64/aarch64/cpuswitch.S
P src/sys/arch/aarch64/aarch64/genassym.cf
P src/sys/arch/aarch64/aarch64/locore.S
P src/sys/arch/aarch64/aarch64/pmap.c
P src/sys/arch/aarch64/aarch64/vectors.S
P src/sys/arch/aarch64/include/cpufunc.h
P src/sys/arch/amd64/include/pmap.h
P src/sys/arch/arm/sunxi/sun8i_crypto.c
P src/sys/arch/evbarm/fdt/fdt_machdep.c
P src/sys/arch/i386/include/pmap.h
P src/sys/arch/sparc/include/cpu.h
P src/sys/arch/x86/x86/pmap.c
P src/sys/arch/xen/include/intr.h
P src/sys/arch/xen/x86/pintr.c
P src/sys/dev/ata/ata_wdc.c
P src/sys/dev/ata/atareg.h
P src/sys/dev/i2c/ibmhawk.c
P src/sys/dev/ic/ciss.c
P src/sys/dev/usb/ehci.c
P src/sys/dev/usb/if_cdce.c
P src/sys/dev/usb/ohci.c
P src/sys/dev/usb/uhci.c
P src/sys/dev/usb/uhub.c
P src/sys/dev/usb/usb_mem.c
P src/sys/dev/usb/usbdi.c
P src/sys/dev/usb/usbdi_util.c
P src/sys/dev/usb/usbdivar.h
P src/sys/dev/usb/vhci.c
P src/sys/external/bsd/dwc2/dwc2.c
P src/sys/fs/puffs/puffs_msgif.c
P src/sys/fs/puffs/puffs_vnops.c
P src/sys/fs/tmpfs/tmpfs_vnops.c
P src/sys/kern/subr_kcov.c
P src/sys/kern/subr_lockdebug.c
P src/sys/kern/subr_msan.c
P src/sys/net/agr/ieee8023ad_lacp_sm_tx.c
P src/sys/netinet/igmp.c
P src/sys/rump/fs/Makefile.rumpfscomp
U src/sys/rump/fs/lib/libnofifovfs/Makefile
U src/sys/rump/fs/lib/libnofifovfs/nofifo_vnops.c
P src/sys/rump/librump/rumpvfs/rumpfs.c
P src/sys/sys/kcov.h
P src/sys/uvm/uvm_aobj.c
P src/sys/uvm/uvm_fault.c
P src/sys/uvm/uvm_page_status.c
P src/tests/Makefile.inc
P src/tests/fs/ffs/Makefile
P src/tests/fs/puffs/Makefile
P src/usr.bin/sed/defs.h
P src/usr.bin/sed/main.c
P src/usr.bin/sed/process.c
P src/usr.sbin/postinstall/postinstall.in

Updating xsrc tree:


Killing core files:


Updating tar files:
src/top-level: collecting... replacing... done
src/bin: collecting... replacing... done
src/common: collecting... replacing... done
src/compat: collecting... replacing... done
src/crypto: collecting... replacing... done
src/dist: collecting... replacing... done
src/distrib: collecting... replacing... done
src/doc: collecting... replacing... done
src/etc: collecting... replacing... done
src/external: collecting... replacing... done
src/extsrc: collecting... replacing... done
src/games: collecting... replacing... done
src/gnu: collecting...pax: Unable to access src/gnu (No such file or directory)
pax: WARNING! These file names were not selected:
src/gnu
 done
src/include: collecting... replacing... done
src/lib: collecting... replacing... done
src/libexec: collecting... replacing... done
src/regress: collecting... replacing... done
src/rescue: collecting... replacing... done
src/sbin: collecting... replacing... done
src/share: collecting... replacing... done
src/sys: collecting... replacing... done
src/tests: collecting... replacing... done
src/tools: collecting... replacing... done
src/usr.bin: collecting... replacing... done
src/usr.sbin: collecting... replacing... done
src/config: collecting... replacing... done
src: collecting... replacing... done
xsrc/top-level: collecting... replacing... done
xsrc/external: collecting... replacing... done
xsrc/local: collecting... replacing... done
xsrc: collecting... replacing... done



Updating release-8 src tree (netbsd-8):
U doc/CHANGES-8.3
P sys/arch/x86/pci/if_vmx.c

Updating release-8 xsrc tree (netbsd-8):


Updating release-8 tar files:
src/top-level: collecting... replacing... done
src/bin: collecting... replacing... done
src/common: collecting... replacing... done
src/compat: collecting... replacing... done
src/crypto: collecting... replacing... done
src/dist: collecting... replacing... done
src/distrib: collecting... replacing... done
src/doc: collecting... replacing... done
src/etc: collecting... replacing... done
src/external: collecting... replacing... done
src/extsrc: collecting... replacing... done
src/games: collecting... replacing... done

Automated report: NetBSD-current/i386 build failure

2020-05-15 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 2020.05.15.23.57.17.

An extract from the build.sh output follows:

--- cleandir-swsensor ---
cleandir ===> sys/modules/swsensor
--- cleandir-sysv_ipc ---
(cd /tmp/bracket/build/2020.05.15.23.57.17-i386/src/sys/modules/sysv_ipc && 
rm -f machine i386 i386 x86 xen   a.out [Ee]rrs mklog core *.core sysv_ipc.kmod 
sysv_ipc.o sysv_msg.o sysv_sem.o sysv_shm.o   sysv_ipc.kmod.map || true) 
--- cleandir-sysvbfs ---
--- __docleandir ---
(cd /tmp/bracket/build/2020.05.15.23.57.17-i386/src/sys/modules/sysvbfs && 
rm -f .depend bfs.d bfs_sysvbfs.d sysvbfs.d sysvbfs_vfsops.d sysvbfs_vnops.d 
bfs.d.tmp bfs_sysvbfs.d.tmp sysvbfs.d.tmp sysvbfs_vfsops.d.tmp 
sysvbfs_vnops.d.tmp 
/tmp/bracket/build/2020.05.15.23.57.17-i386/src/sys/modules/sysvbfs/tags  || 
true) 
--- cleandir-suser ---
--- __doclean ---
--- cleandir-lib ---
(cd /tmp/bracket/build/2020.05.15.23.57.17-i386/src/lib/libbpfjit && rm -f 
libbpfjit.a   bpfjit.o bpfjit.o.tmp || true) 
--- cleandir-../external/bsd/sljit/lib ---
--- libclean3 ---
(cd /tmp/bracket/build/2020.05.15.23.57.17-i386/src/external/bsd/sljit/lib 
&& rm -f libsljit_g.a|| true) 
--- cleandir-../external/bsd/libpcap/lib ---
A failure has been detected in another branch of the parallel make
nbmake[5]: stopped in 
/tmp/bracket/build/2020.05.15.23.57.17-i386/src/external/bsd/libpcap/lib
--- cleandir-libbpfjit ---
A failure has been detected in another branch of the parallel make
--- cleandir-../external/bsd/libpcap/lib ---
*** [cleandir-../external/bsd/libpcap/lib] Error code 2
nbmake[4]: stopped in /tmp/bracket/build/2020.05.15.23.57.17-i386/src/lib
--- cleandir-libbpfjit ---

The following commits were made between the last successful build and
the failed build:

2020.05.15.22.15.43 ad src/sys/fs/tmpfs/tmpfs_vnops.c,v 1.137
2020.05.15.22.17.45 ad src/sys/arch/amd64/include/pmap.h,v 1.66
2020.05.15.22.17.45 ad src/sys/arch/i386/include/pmap.h,v 1.125
2020.05.15.22.19.01 ad src/sys/arch/x86/x86/pmap.c,v 1.390
2020.05.15.22.22.06 ad src/sys/arch/x86/x86/pmap.c,v 1.391
2020.05.15.22.22.44 ad src/sys/arch/x86/x86/pmap.c,v 1.392
2020.05.15.22.25.18 ad src/sys/uvm/uvm_page_status.c,v 1.5
2020.05.15.22.27.04 ad src/sys/uvm/uvm_aobj.c,v 1.140
2020.05.15.22.35.05 ad src/sys/uvm/uvm_fault.c,v 1.226
2020.05.15.22.39.54 christos src/usr.bin/sed/defs.h,v 1.13
2020.05.15.22.39.54 christos src/usr.bin/sed/main.c,v 1.36
2020.05.15.22.39.54 christos src/usr.bin/sed/process.c,v 1.53
2020.05.15.23.32.27 christos src/distrib/sets/lists/base/shl.mi,v 1.886
2020.05.15.23.32.27 christos src/distrib/sets/lists/comp/mi,v 1.2326
2020.05.15.23.32.28 christos src/distrib/sets/lists/comp/shl.mi,v 1.332
2020.05.15.23.32.28 christos src/distrib/sets/lists/debug/mi,v 1.310
2020.05.15.23.32.28 christos src/distrib/sets/lists/debug/shl.mi,v 1.247
2020.05.15.23.32.28 christos src/sys/rump/fs/Makefile.rumpfscomp,v 1.8
2020.05.15.23.32.28 christos src/sys/rump/librump/rumpvfs/rumpfs.c,v 1.161
2020.05.15.23.32.28 christos src/tests/Makefile.inc,v 1.7
2020.05.15.23.32.28 christos src/tests/fs/ffs/Makefile,v 1.22
2020.05.15.23.32.28 christos src/tests/fs/puffs/Makefile,v 1.16
2020.05.15.23.57.17 ad src/external/cddl/osnet/dev/profile/profile.c,v 1.11

Logs can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2020.05.html#2020.05.15.23.57.17


Re: lang/rust build fails

2020-05-15 Thread Andrew Doran
On Thu, May 14, 2020 at 11:53:04AM -0500, Robert Nestor wrote:
> Ran into an interesting problem trying to build lang/rust from both -current 
> and 2020Q1 pkgsrc.  On a NetBSD installation of 9.99.45 kernel and user land, 
> the builds succeed.  Under 9.99.60 kernel and user land the builds fail.
> 
> The failure doesn?t give much of a clue about what?s happened.  The last 
> lines in the build.log are:
> 
> running: /pkg_comp/work/pkg/lang/rust/work/rust-bootstrap/bin/cargo build 
> --manifest-path 
> /pkg_comp/work/pkg/lang/rust/work/rustc-1.42.0-src/src/bootstrap/Cargo.toml 
> --frozen
>Compiling proc-macro2 v0.4.30
> 
> At that point there?s nothing consuming CPU time in the build and everything 
> seems to be waiting on something to happen that never does.  I?ve left the 
> system in that state for about 24 hours and still no progress.
> 
> Any  clues? Could this be something related to some of the recent kernel 
> changes?

I think it's likely a race condition with pthread_mutex.  I found a decent
repro and will take a look, hopefully this weekend.

Andrew


Re: lang/mono6 fails build under -current

2020-05-15 Thread maya
On Tue, May 12, 2020 at 02:41:19PM +0100, Chavdar Ivanov wrote:
> On Tue, 12 May 2020 at 14:03,  wrote:
> >
> > On Mon, May 11, 2020 at 05:25:03PM +0100, Chavdar Ivanov wrote:
> > > Has anybody been able to build lang/mono6 under reasonably recent
> > > -current? I keep getting exciting crashes in various places, seem not
> > > to repeat, e.g.
> >
> >
> > I can build it.
> >
> > Setup:
> > userland: 9.99.51 (early March)
> > kernel: 9.99.59 (early May)
> 
> Userland and kernel from yesterday, 11th of May
> >
> > GCC 8.4.0
> 
> Ditto
> 
> > binutils 2.31.1
> 
> As far as I can see it, on this version of the system it is 2.34:
> 
> nm -V
> GNU nm (NetBSD Binutils nb1) 2.34.
> 
> I never run kernel and userland from different versions, as I use
> sysbuild and sysupgrade.
 
 I am failing to reproduce it on 9.99.61. Any other guesses for what
 might be different on your setup?


Re: qemu emulated machine crashes due to disk timeouts

2020-05-15 Thread Jaromír Doleček
Le ven. 15 mai 2020 à 15:53, Jonathan A. Kollasch
 a écrit :
>
> On Sat, May 02, 2020 at 12:02:45PM +1000, Paul Ripke wrote:
> > Since I have my qemu disk images on slow spinning rust host disks, when the
> > host disk is busy (esp. daily+security runs), I find my qemu vm's see disk
> > timeouts, and end up crashing. This isn't great behaviour.
>
> Timeout issue aside, crashing because of it is a bug in the error
> handling code somewhere.

Yes, this is root cause of the panic:

panic: LOCKDEBUG: Mutex error: mutex_vector_enter,509: assertion
failed: !cpu_intr_p()
[ 13493.1166960] cpu0: Begin traceback...
[ 13493.1166960] vpanic() at netbsd:vpanic+0x178
[ 13493.1166960] snprintf() at netbsd:snprintf
[ 13493.1166960] lockdebug_more() at netbsd:lockdebug_more
[ 13493.1166960] mutex_enter() at netbsd:mutex_enter+0x656
[ 13493.1166960] suspendsched() at netbsd:suspendsched+0x19
[ 13493.1166960] cpu_reboot() at netbsd:cpu_reboot+0x46
[ 13493.1166960] sys_reboot() at netbsd:sys_reboot
[ 13493.1166960] vpanic() at netbsd:vpanic+0x181
[ 13493.1166960] snprintf() at netbsd:snprintf
[ 13493.1166960] startlwp() at netbsd:startlwp
[ 13493.1166960] alltraps() at netbsd:alltraps+0xc3
[ 13493.1166960] wdc_ata_bio_start() at netbsd:wdc_ata_bio_start+0xcbd
[ 13493.1166960] ata_xfer_start() at netbsd:ata_xfer_start+0x4f
[ 13493.1166960] wdc_ata_bio_intr() at netbsd:wdc_ata_bio_intr+0x3b9
[ 13493.1166960] wdcintr() at netbsd:wdcintr+0x10a
[ 13493.1166960] intr_biglock_wrapper() at netbsd:intr_biglock_wrapper+0x36
[ 13493.1166960] Xhandle_ioapic_edge3() at netbsd:Xhandle_ioapic_edge3+0x6d

I're-recheck the path, something seems to still fool the code to run
handling in interrupt context when it things it's in process context.

Jaromir


Re: lang/rust build fails

2020-05-15 Thread Robert Nestor
Thanks!  I’ll give your suggestions a try.

-bob

On May 15, 2020, at 7:27 AM, Martin Husemann  wrote:

> On Fri, May 15, 2020 at 06:27:41AM -0500, Robert Nestor wrote:
>> Yes, and it appears to be different from what Chavdar has on his slightly 
>> earlier system.
>> seed  0 ???  estimate, collect, v
> 
> Bingo!
> 
> You do not have a hardware random number generator, and your setup did not
> provide initial entropy.
> 
> There is an ongoing thread on some other list where this currently is
> discussed with lots of technical details and irritation, but the short
> story is:
> 
> - Easiest fix for now is to provide a properly seeded /var/db/entropy-file
>   (shutdown to single user, manually copy file over, reboot).
>   You can create such a file on another machine (with working random
>   number generator) via "rndctl -S $file".
>   After that reboot, all should be fine and the next rust build will
>   not block.
> 
> - If this is a virtual machine, add viornd(4) to your kernel (and hope the
>   hypervisor supports it)
> 
> There are variants of the first solution, like generating random bytes
> by some other means and write them to /dev/random.
> 
> Martin



Re: lang/rust build fails

2020-05-15 Thread Robert Nestor
Yes, and it appears to be different from what Chavdar has on his slightly 
earlier system.

Source Bits Type  Flags
/dev/random   0 ???  estimate, collect, v
ums0  0 tty  estimate, collect, v, t, dt
ukbd0 0 tty  estimate, collect, v, t, dt
cd0   0 disk estimate, collect, v, t, dt
wd2   0 disk estimate, collect, v, t, dt
wd1   0 disk estimate, collect, v, t, dt
wd0   0 disk estimate, collect, v, t, dt
cpu7  0 vm   estimate, collect, v, t, dv
cpu6  0 vm   estimate, collect, v, t, dv
cpu5  0 vm   estimate, collect, v, t, dv
cpu4  0 vm   estimate, collect, v, t, dv
cpu3  0 vm   estimate, collect, v, t, dv
cpu2  0 vm   estimate, collect, v, t, dv
cpu1  0 vm   estimate, collect, v, t, dv
cpu0  0 vm   estimate, collect, v, t, dv
coretemp3-cpu30 env  estimate, collect, v, t, dv, dt
coretemp2-cpu20 env  estimate, collect, v, t, dv, dt
coretemp1-cpu10 env  estimate, collect, v, t, dv, dt
coretemp0-cpu00 env  estimate, collect, v, t, dv, dt
wm0   0 net  estimate, v, t, dt
system-power  0 power estimate, collect, v, t, dt
autoconf  0 ???  estimate, collect, t
seed  0 ???  estimate, collect, v

-bob

On May 14, 2020, at 11:47 PM, Martin Husemann  wrote:

> Can you show output (as root) of rndctl -l please?
> 
> Martin



Re: lang/rust build fails

2020-05-15 Thread Martin Husemann
On Fri, May 15, 2020 at 06:27:41AM -0500, Robert Nestor wrote:
> Yes, and it appears to be different from what Chavdar has on his slightly 
> earlier system.
> seed  0 ???  estimate, collect, v

Bingo!

You do not have a hardware random number generator, and your setup did not
provide initial entropy.

There is an ongoing thread on some other list where this currently is
discussed with lots of technical details and irritation, but the short
story is:

 - Easiest fix for now is to provide a properly seeded /var/db/entropy-file
   (shutdown to single user, manually copy file over, reboot).
   You can create such a file on another machine (with working random
   number generator) via "rndctl -S $file".
   After that reboot, all should be fine and the next rust build will
   not block.

 - If this is a virtual machine, add viornd(4) to your kernel (and hope the
   hypervisor supports it)

There are variants of the first solution, like generating random bytes
by some other means and write them to /dev/random.

Martin


Re: lang/rust build fails

2020-05-15 Thread Mike Pumford




On 14/05/2020 17:53, Robert Nestor wrote:


running: /pkg_comp/work/pkg/lang/rust/work/rust-bootstrap/bin/cargo build 
--manifest-path 
/pkg_comp/work/pkg/lang/rust/work/rustc-1.42.0-src/src/bootstrap/Cargo.toml 
--frozen
Compiling proc-macro2 v0.4.30

At that point there’s nothing consuming CPU time in the build and everything 
seems to be waiting on something to happen that never does.  I’ve left the 
system in that state for about 24 hours and still no progress.

Any  clues? Could this be something related to some of the recent kernel 
changes?
It might be but it also happens sometimes on 9.0-stable as well. Never 
managed to work out why.


Mike


Re: lang/rust build fails

2020-05-15 Thread Martin Husemann
On Fri, May 15, 2020 at 09:15:20AM +0100, Chavdar Ivanov wrote:
> Sure, here it is.

Heh, sorry- I meant Robert.

> rdrand  512 rng  estimate, collect, v

I wanted to know if a line with "rng" is in his output (just a wild guess).

Martin


Re: lang/rust build fails

2020-05-15 Thread Chavdar Ivanov
Sure, here it is.

# rndctl -l
Source Bits Type  Flags
/dev/random   0 ???  estimate, collect, v
ukbd0 0 tty  estimate, collect, v, t, dt
wd2   0 disk estimate, collect, v, t, dt
wd1   0 disk estimate, collect, v, t, dt
wd0   0 disk estimate, collect, v, t, dt
acpibat0-discha   0 power estimate, collect, v, t, dv, dt
acpibat0-charge   0 power estimate, collect, v, t, dv, dt
acpibat1-discha   0 power estimate, collect, v, t, dv, dt
acpibat1-charge   0 power estimate, collect, v, t, dv, dt
cpu7  0 vm   estimate, collect, v, t, dv
cpu6  0 vm   estimate, collect, v, t, dv
cpu5  0 vm   estimate, collect, v, t, dv
cpu4  0 vm   estimate, collect, v, t, dv
cpu3  0 vm   estimate, collect, v, t, dv
cpu2  0 vm   estimate, collect, v, t, dv
cpu1  0 vm   estimate, collect, v, t, dv
cpu0  0 vm   estimate, collect, v, t, dv
coretemp3-cpu60 env  estimate, collect, v, t, dv, dt
coretemp2-cpu40 env  estimate, collect, v, t, dv, dt
coretemp1-cpu20 env  estimate, collect, v, t, dv, dt
coretemp0-cpu00 env  estimate, collect, v, t, dv, dt
wm0   0 net  estimate, v, t, dt
pms0  0 tty  estimate, collect, v, t, dt
pckbd00 tty  estimate, collect, v, t, dt
acpitz7-tempera   0 env  estimate, collect, v, t, dv, dt
acpitz6-tempera   0 env  estimate, collect, v, t, dv, dt
acpitz5-tempera   0 env  estimate, collect, v, t, dv, dt
acpitz4-cpu0-te   0 env  estimate, collect, v, t, dv, dt
acpitz3-tempera   0 env  estimate, collect, v, t, dv, dt
acpitz2-tempera   0 env  estimate, collect, v, t, dv, dt
acpitz1-cpu0-te   0 env  estimate, collect, v, t, dv, dt
acpitz0-tempera   0 env  estimate, collect, v, t, dv, dt
system-power  0 power estimate, collect, v, t, dt
autoconf  0 ???  estimate, collect, t
seed256 ???  estimate, collect, v
rdrand  512 rng  estimate, collect, v

On Fri, 15 May 2020 at 05:47, Martin Husemann  wrote:
>
> Can you show output (as root) of rndctl -l please?
>
> Martin



--