From owner-freebsd-alpha@FreeBSD.ORG Sun Feb 29 21:07:55 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3881216A4CE; Sun, 29 Feb 2004 21:07:55 -0800 (PST) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E174343D31; Sun, 29 Feb 2004 21:07:54 -0800 (PST) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i2157sTr005234; Mon, 1 Mar 2004 00:07:54 -0500 (EST) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i2157sx4005233; Mon, 1 Mar 2004 00:07:54 -0500 (EST) Date: Mon, 1 Mar 2004 00:07:54 -0500 From: Ken Smith To: Peter Grehan Message-ID: <20040301050754.GA4948@electra.cse.Buffalo.EDU> References: <4042C2CA.8020104@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4042C2CA.8020104@freebsd.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: freebsd-alpha@freebsd.org Subject: Re: One more patch for Alpha console issues... X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2004 05:07:55 -0000 On Mon, Mar 01, 2004 at 02:57:46PM +1000, Peter Grehan wrote: > > Any further thoughts? > > The problem is that make_dev() calls devlock(), which requires > curthread to be valid to take out a mutex. > > The fix is to put the hand-crafting of proc0, thread0 and pcpu > data and mutex_init to be *before* the call to cninit(). This > is why i386 works. > > I had the same problem on PPC, and fortunately had the psim simulator > to work out what was going on. Thanks!!! I think that's what my latest patch does, by moving the final console initialization after the proc0/thread0/pcpu setup. I was most worried that what was truly causing the problems was extra function calls consuming more stack than before and that starting to cause problems. It makes me much happier that there is another cause of these problems and that it's deterministic. :-) -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |