On Sun, Oct 18, 2015 at 03:42:07PM -0400, Sonic wrote: > No clue if my bug is related. Attempting to upgrade -current today and I get: > Oct 18 14:29:39 stargate /bsd: ksh(4880): syscall 131 > Oct 18 14:29:46 stargate /bsd: ksh(30776): syscall 131 > etc.
I don't think it's related since it's complaining about different syscalls. You ran into this situation: Old kernel: accepts "flock" pledge but doesn't require it Old ksh: no "flock" pledge New kernel: accepts "flock" and requires it for the syscall New ksh: added "flock" pledge You went from old kernel + old ksh to new kernel + old ksh. It killed ksh because old ksh didn't request "flock" pledge before calling it. The solution for me was to rebuild the userland programs that require "flock" with the old kernel and then reboot with the new kernel. However, that was yesterday and I did it shortly after that commit. It's a fast moving target. You may be better off upgrading from a snapshot and then rebuilding -current.
