From owner-freebsd-current  Wed May  8 00:01:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA00582
          for current-outgoing; Wed, 8 May 1996 00:01:16 -0700 (PDT)
Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA00573
          for <freebsd-current@FreeBSD.ORG>; Wed, 8 May 1996 00:01:13 -0700 (PDT)
Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id AAA07259; Wed, 8 May 1996 00:01:06 -0700
From: Brian Litzinger <brian@MediaCity.com>
Message-Id: <199605080701.AAA07259@MediaCity.com>
Subject: Re: -current not booting
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Wed, 8 May 1996 00:01:06 -0700 (PDT)
Cc: ec0@s1.GANet.NET, ejc@nasvr1.cb.att.com, freebsd-current@FreeBSD.ORG
In-Reply-To: <11301.831521624@time.cdrom.com> from "Jordan K. Hubbard" at "May 7, 96 07:13:44 pm"
Reply-To: brian@MediaCity.com
X-Mailer: ELM [version 2.4ME+ PL11 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Jordan K. Hubbard wrote:
> It may also be something to do with phk's changes to locore.s.  I
> don't know, there are so many variables!  Would it be possible for you
> to grab a copy of the CVS tree and roll back /sys until you get a
> working kernel again?  That would definitely help us to figure out
> *when* the problem crept in.

I too ran into the kernel boot problem.  Building a GENERIC
kernel works fine.  Building based on my LOCAL definition produces
a kernel which reboots just after loading the kernel.

I re'suped and built again.  Still rebooted.

I 'cp LOCAL LOCAL.bak', 'cp GENERIC LOCAL', then edited the new LOCAL
adding my original LOCAL specific stuff back in.

And now the kernel is booting fine.

I did plenty of config's, make depends, et al, as I was trying different
combinations.

Brian Litzinger
brian@mediacity.com