Trying to debug another issue, so I attempted to boot a special kernel
using 'boot netbsd.test -d'.
Much to my surprise, after loading the kernel, it immediately crashed
with no console output at all, and proceeded to reboot.
With the exact same kernel, I am able to use 'boot -s' and then
Ever since my upgrade from 6.99.23 6.99.24, I've had issues with the
nfsserver module. (See [1] and [2] and PR kern/48027). The issue in
[2] was resolved by Christos, but the initial problem remains.
I'm still digging in, and today I tried to get more details on what was
sending the SIGSYS
With everything built from today's sources, I get
crash exam/ins syscall
syscall:pushq %rbp
syscall+0x1:H\211\345AWAVAUATSH\203\354(I\211\374eH\213\034%\340\001
crash
I don't think the second line should be printed... :)
More:
crash exam/inst syscall,5
syscall:pushq
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 2013.12.08.20.45.30.
An extract from the build.sh output follows:
Updating src tree:
P src/bin/cat/cat.c
P src/lib/csu/arch/mips/crt0.S
P src/lib/libc/shlib_version
P src/sbin/gpt/add.c
P src/sbin/gpt/gpt.8
P src/sbin/gpt/resize.c
P src/sbin/gpt/show.c
P src/sys/arch/amd64/amd64/cpufunc.S
P src/sys/arch/arm/pic/pic.c
P src/sys/arch/i386/i386/freebsd_machdep.c
P