From owner-freebsd-current@FreeBSD.ORG Sun Jun 12 16:54:54 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A88016A475 for ; Sun, 12 Jun 2005 16:54:54 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC8E143E4D for ; Sun, 12 Jun 2005 16:54:31 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.3/8.13.1) with ESMTP id j5CGsUtq011868; Sun, 12 Jun 2005 09:54:30 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.3/8.13.1/Submit) id j5CGsUNQ011867; Sun, 12 Jun 2005 09:54:30 -0700 (PDT) (envelope-from sgk) Date: Sun, 12 Jun 2005 09:54:30 -0700 From: Steve Kargl To: jasonh@cc.gatech.edu Message-ID: <20050612165430.GA11825@troutmask.apl.washington.edu> References: <32946.24.27.59.14.1118528242.squirrel@24.27.59.14> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32946.24.27.59.14.1118528242.squirrel@24.27.59.14> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Reboot when trying to load -current (amd64) kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2005 16:54:57 -0000 On Sat, Jun 11, 2005 at 06:17:22PM -0400, jasonh@cc.gatech.edu wrote: > > I just tried upgrading from 5.4-STABLE/amd64 to 6.0-CURRENT/amd64, using > the conventional cvsup/make buildworld/make kernel method. Everything > built cleanly, but upon rebooting, I found that all of the boot loader > options except "Escape to loader prompt" cause the machine to immediately > reboot with absolutely no indication as to the cause of the problem. > Nothing is displayed on the console, even with the verbose option. This > happens both with GENERIC and my own custom (no SMP/debugging) kernel > config. However, as I mentioned earlier, I can escape to a loader prompt > and boot my 5.4 kernel with no problems. The mailing list and > /usr/src/UPDATING don't seem to provide any hint as to what could be > wrong--is there something obvious I'm missing? > -current of amd64 is currently hosed. -- Steve