From owner-freebsd-current@FreeBSD.ORG Mon Jun 13 18:20:30 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 E38D316A41C for ; Mon, 13 Jun 2005 18:20:30 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 815AC43D1D for ; Mon, 13 Jun 2005 18:20:30 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j5DIPMUO005789; Mon, 13 Jun 2005 12:25:22 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42ADCDD5.9040209@samsco.org> Date: Mon, 13 Jun 2005 12:17:57 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <20050612144703.GB10314@troutmask.apl.washington.edu> In-Reply-To: <20050612144703.GB10314@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-current@freebsd.org, Paul Richards 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: Mon, 13 Jun 2005 18:20:31 -0000 Steve Kargl wrote: > 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. > Does the SNAP004 snapshot that I published work any better for you? Scott