From owner-freebsd-ppc@FreeBSD.ORG Thu Oct 13 15:32:21 2005 Return-Path: X-Original-To: freebsd-ppc@freebsd.org Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC6E616A41F; Thu, 13 Oct 2005 15:32:21 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id A35E643D48; Thu, 13 Oct 2005 15:32:20 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Thu, 13 Oct 2005 11:48:42 -0400 From: John Baldwin To: freebsd-ppc@freebsd.org Date: Thu, 13 Oct 2005 11:33:42 -0400 User-Agent: KMail/1.8.2 References: <000701c5d003$1d0a49e0$13b46743@TIM> In-Reply-To: <000701c5d003$1d0a49e0$13b46743@TIM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510131133.44645.jhb@freebsd.org> Cc: 'Peter Grehan' Subject: Re: Panic on boot from CD X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2005 15:32:22 -0000 On Thursday 13 October 2005 10:33 am, Tim Simmons wrote: > Sorry it's taken me a while to respond, I've been out on family leave. I > have tried as you suggested, booting from the open firmware screen instead > of directly from the CD, and I get the same result. > > I downloaded and burned the 6.0RC1 ISO this morning, and get a slightly > different error, but in the same place. The error now reads: > > KDB: debugger backends: ddb > KDB: current backend: ddb > Panic: Assertion curthread != NULL failed at > /usr/src/sys/kern/kern_mutex.c:268 > > KDB: enter: panic > [thread pid -1 tid 0 ] > Stopped at 0: illegal instruction 0 > Db> > > > I can't interact with the system at this point to run a stack trace. Any > ideas? Oh, and no, it's not an eMac. It's a PowerMac G4 667mhz w/ 256 megs > ram. This same machine runs fine under OSX. curthread of NULL would certainly indicate that mtx_lock() is being called before mutex_init(). If there's any way to get a stack trace, that would be helpful. Alternatively, you can try inserting a while (1); hang in the code prior to the call to mutex_init() and move it around until you find out where the hang is. However, looking in powerpc_init(), it seems that kdb_init() (which does the KDB printf's) doesn't get called until after mutex_init(), so it seems that curthread is getting reset to NULL after it was initially set before mutex_init(). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org