The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2020.06.15.00.37.24 christos src/external/bsd/file/dist/ChangeLog,v 1.11
2020.06.15.00.37.24 christos src/external/bsd/file/dist/Makefile.am,v 1.4
Updating src tree:
P src/common/lib/libprop/prop_array_util.c
P src/common/lib/libprop/prop_dictionary_util.c
P src/crypto/external/bsd/openssh/bin/sshd/Makefile
P src/crypto/external/bsd/openssh/dist/pfilter.c
P src/distrib/ews4800mips/floppies/instkernel/Makefile
P
Hello folks,
I've renamed blacklist to blocklist, so if you are currently using it,
you should rename things accordingly:
- rc.conf variable
- /var/db/blacklist.db file
- npf table name
Apologies for the inconvenience,
christos
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.06.15.00.31.21.
An extract from the build.sh output follows:
--- funcs.lo ---
CC funcs.lo
---
Hi,
On Fri, Jun 12, 2020 at 11:17:30PM +0200, Thomas Klausner wrote:
> With a 9.99.63/amd64 kernel from May 19 I saw a panic:
>
> Jun 7 01:01:01 yt savecore: reboot after panic: [ 396809.5836453] panic:
> kernel diagnostic assertion "c->c_cpu->cc_lwp == curlwp ||
> c->c_cpu->cc_active != c"
On Sat, Jun 13, 2020 at 09:44:35PM -0700, Greywolf wrote:
> raidctl -a /dev/wd0c raid1
>
> raidctl -F component0 raid1
I would have expected that to work. What is the raidctl status output
after the -a ?
Martin
