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

[Dustin Marquess <dmarquess%gmail.com@localhost>]

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 Paul Goyette <paul%whooppee.com@localhost> wrote:
>
> 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 will grow as new ABI changes occur, but these
> changes in content don't result in changes to the kernel configuration
> description files such as GENERIC or ALL.  The ABI changes are sort of
> buried inside the kernel configuration _definition_ files, typically
> named src/sys/.../files*   :)
>
> For a quick test, just add ``options COMPAT_90'' to your MYCONFIG
> kernel description.
>
>
>
> On Mon, 10 Feb 2020, Dustin Marquess wrote:
>
> > So as part of my nasty process, after I do a 'cvs update', I diff the
> > old GENERIC and the new GENERIC and look for any major changes and
> > then replicate those into my local config file.  The only config
> > changes I saw where for the various *san(itiziers).
> >
> > I'll attempt to reproduce on GENERIC, and if I can reproduce it, I'll
> > try and ktrace/kdump/ktruss to figure out where it's broken.
> >
> > Thanks all,
> > -Dustin
> >
> > On Mon, Feb 10, 2020 at 9:28 PM Robert Elz <kre%munnari.oz.au@localhost> wrote:
> >>
> >>     Date:        Mon, 10 Feb 2020 19:07:50 -0600
> >>     From:        Dustin Marquess <dmarquess%gmail.com@localhost>
> >>     Message-ID:  <CAJpsHY5cagFPzhkzbnLOgdymOpbANZ-SCbQQFu5m5n30UUxgLQ%mail.gmail.com@localhost>
> >>
> >>   | 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 kernel which will have all the correct
> >> COMPAT_xxx options defined.   Once you have the new userland installed
> >> you can build your own tailored kernel and run that.
> >>
> >> You can also add the needed COMPAT_xxx options to your kernel config
> >> file, but doing it that way can take more try & retry until you finally
> >> get everything needed.
> >>
> >> kre
> >>
> >
> > !DSPAM:5e42233b188721095115340!
> >
> >
>
> +--------------------+--------------------------+-----------------------+
> | Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
> | (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
> | Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
> +--------------------+--------------------------+-----------------------+