Well, I finally got my cross-compile stuff working, and decided to take the
plunge, and update my Sun3 system with cross-compiled binaries and kernel.

The bins all work wonderfully, but the kernel doesn't.  It goes through
the initialization okay, but as soon as it runs init, bad things happen.

So, I decided to compare the cross-compiled kernel to one build on my
Sun3...
and there was no difference in behaviour, which leads me to beleive it's
a problem in -current.  The symtoms are...

When booting with GENERIC, init runs, and then it loops on
'init got Signal 10'.  L1-A into the kernel ddb, and do a 'ps', shows that
only init, swapper, and pagedaemon are running.

When booting with a custom kernel (GENERIC, with all extraneous drivers
removed) I don't get the error messages, but after ~5 minutes of inactivity
init dies with an error regarding Signal 10, and the system drops to ddb.

This is the first kernel update on this system since Jan28, so the new
items are the copypage m68k stuff, and the new root/swap config.  The
kernel
seems to find the root and swap just fine....and I'm stumped at what to
look
for.

Help! ;-)

-- 
   //////////////////////////////////////////////////////////////////////
  //    Scott Ellis     //   scotte@warped.com   //   sellis@gi.com   //
 //////////////////////////////////////////////////////////////////////
// WARNING: This signature warps  time and space in its vicinity    //