Re: Bad system call errors during an upgrade of -current

2020-02-10 Thread Dustin Marquess
Okay, you guys are absolutely correct. Since the old COMPAT_ settings got moved out of GENERIC and into compat_netbsd15.config, I had completely missed them in my diff :(. Sorry for the noise! It's been a while and I'm obviously gotten VERY rusty -Dustin On Mon, Feb 10, 2020 at 9:51 PM

Re: Bad system call errors during an upgrade of -current

2020-02-10 Thread Paul Goyette
As Robert Elz said in previous reply, you're most likely missing some compatability code. Since you initially indicated that it worked on 9.99.10, you most likely don't have COMPAT_90 in your config. COMPAT_90 brings in stuff for compatability with the 9.0 release. The contents of COMPAT_90

Re: Bad system call errors during an upgrade of -current

2020-02-10 Thread Robert Elz
Date:Mon, 10 Feb 2020 19:07:50 -0600 From:Dustin Marquess Message-ID: | Looking at my history, I did: | | ./build.sh -O ../obj -T ../tools tools distribution kernel=MYCONFIG modules As Kamil suggested, this will be your problem. To start with, use a GENERIC

Re: Bad system call errors during an upgrade of -current

2020-02-10 Thread Paul Goyette
On Tue, 11 Feb 2020, Kamil Rytarowski wrote: Another question is whether your kernel config contains compat glue for old syscalls. It would also be nice to find out which syscall(s) are missing. Can you use ktrace/kdump (or ktruss) to find out which syscall is returning ENOSYS (error

Re: Bad system call errors during an upgrade of -current

2020-02-10 Thread Kamil Rytarowski
Another question is whether your kernel config contains compat glue for old syscalls. On 11.02.2020 02:07, Dustin Marquess wrote: > Looking at my history, I did: > > ./build.sh -O ../obj -T ../tools tools distribution kernel=MYCONFIG modules > ./build.sh -O ../obj -T ../tools installmodules=/ >

Re: Bad system call errors during an upgrade of -current

2020-02-10 Thread Dustin Marquess
Looking at my history, I did: ./build.sh -O ../obj -T ../tools tools distribution kernel=MYCONFIG modules ./build.sh -O ../obj -T ../tools installmodules=/ cp -p /netbsd /onetbsd cp /usr/obj/sys/arch/amd64/compile/MYCONFIG/netbsd / shutdown -r now /stand still has modules for both versions

Re: Bad system call errors during an upgrade of -current

2020-02-10 Thread Kamil Rytarowski
On 11.02.2020 01:49, Dustin Marquess wrote: > I'm trying to upgrade a VM from a 9.99.10 install that was built > around Sep 2th to a 9.99.46 install compiled yesterday. > > I installed the new kernel and modules and rebooted into the new > kernel / old userland. Once done, almost everything

Bad system call errors during an upgrade of -current

2020-02-10 Thread Dustin Marquess
I'm trying to upgrade a VM from a 9.99.10 install that was built around Sep 2th to a 9.99.46 install compiled yesterday. I installed the new kernel and modules and rebooted into the new kernel / old userland. Once done, almost everything crashes with Bad system call. So far "su -", "ls" and