Automated report: NetBSD-current/i386 build failure

2020-03-08 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.03.09.01.06.34. An extract from the build.sh output follows: obsolete_stand fix: postinstall fixes passed:

daily CVS update output

2020-03-08 Thread NetBSD source update
Updating src tree: P src/common/lib/libc/misc/ubsan.c P src/distrib/sets/lists/base/shl.mi P src/distrib/sets/lists/debug/mi P src/distrib/sets/lists/debug/shl.mi P src/distrib/sets/lists/modules/ad.aarch64 P src/distrib/sets/lists/tests/mi P src/etc/etc.sun2/Makefile.inc P

Weird qemu-nvmm problem

2020-03-08 Thread Chavdar Ivanov
Hi, On a -current (from today, but has happened before), when running a particular nvmm guest (32-bit Windows 10), usually when it is busy going through some updates, the host gets into a weird state. I have an ssh connection to it with several tmux panes open; I can switch between them, so the

Re: diagnostic assertion curcpu()->ci_biglock_count == 0 failed

2020-03-08 Thread Andrew Doran
Hi, On Sun, Feb 23, 2020 at 10:30:24AM +0100, Thomas Klausner wrote: > With a 9.99.47/amd64 kernel from February 16, I just had panic (handcopied): > > panic: kernel diagnostic assertion "curcpu()->ci_biglock_count == 0" failed: > file .../kern_exit.c line 214: kernel_lock leaked > cpu12: