From owner-freebsd-sparc64@FreeBSD.ORG Fri Mar 12 12:44:36 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CE2E16A4CE; Fri, 12 Mar 2004 12:44:36 -0800 (PST) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B164C43D1F; Fri, 12 Mar 2004 12:44:35 -0800 (PST) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i2CKiZ2Z009276; Fri, 12 Mar 2004 15:44:35 -0500 (EST) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i2CKiYZs009274; Fri, 12 Mar 2004 15:44:34 -0500 (EST) Date: Fri, 12 Mar 2004 15:44:34 -0500 From: Ken Smith To: Tillman Hodgson Message-ID: <20040312204434.GA8613@electra.cse.Buffalo.EDU> References: <20040311165639.GJ462@seekingfire.com> <20040311170547.GA22014@ns1.xcllnt.net> <20040312031334.GP462@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040312031334.GP462@seekingfire.com> User-Agent: Mutt/1.4.1i cc: current@freebsd.org cc: sparc64@freebsd.org Subject: Re: (was Re: HEADS UP! MAJOR change to FreeBSD/sparc64) Boot failure on rebuild X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2004 20:44:36 -0000 On Thu, Mar 11, 2004 at 09:13:34PM -0600, Tillman Hodgson wrote: > Mounting root from ufs:/dev/ad0a > setrootbyname failed > ffs_mountroot: can't find rootvp > Root mount failed: 6 > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0a > ? List valid disk boot devices > Abort manual input > mountroot> ? > > Any suggestions? This looks like a geom boot disk thing rather than a > 64bTT thing, but what with the timing I thought I'd better explore all > scenarios. This turns out to have been an unforseeable interaction between the new CPU devices in sys/kern/subr_smp.c and the way sparc64 handles the devices that connect to the nexus bus. njl and jhb were able to help figure out what the problem was. A temporary "fix" just got committed that removes the new CPU devices on sparc64 for now, Nate will work on a better solution shortly. -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |