From owner-freebsd-current@FreeBSD.ORG Sun Jun 12 14:47:08 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 B69D516A41C for ; Sun, 12 Jun 2005 14:47:08 +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 857F043D1F for ; Sun, 12 Jun 2005 14:47:08 +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 j5CEl88m010653; Sun, 12 Jun 2005 07:47:08 -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 j5CEl34T010652; Sun, 12 Jun 2005 07:47:03 -0700 (PDT) (envelope-from sgk) Date: Sun, 12 Jun 2005 07:47:03 -0700 From: Steve Kargl To: Paul Richards Message-ID: <20050612144703.GB10314@troutmask.apl.washington.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Immediate reboots on amd64 after upgrading to current 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 14:47:08 -0000 On Sun, Jun 12, 2005 at 12:37:43PM +0100, Paul Richards wrote: > > I followed the handbook instructions of essentially make buildworld, > buildkernel, installkernel etc.. When I rebooted however I found that > the new kernel immediately reboots after selecting any of the options > on the boot menu (safe mode, normal, single user, etc). I'm seeing the exact same behavior. I upgraded a mid May current to June 9th current and see this problem. I backed up to June 1st via cvsup and the boot problem is still there. Ran out of time to track things down until next week :-(. > Is the 6-current broken at the moment? (unlikely as it seems like > quite a severe break) In my experience, the answer is yes. -- Steve