[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Bad system call errors during an upgrade of -current
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.
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.
Main Index |
Thread Index |