From owner-freebsd-ppc@FreeBSD.ORG Wed Aug 30 03:55:57 2006 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 7A96216A4DE for ; Wed, 30 Aug 2006 03:55:57 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBEA843D46 for ; Wed, 30 Aug 2006 03:55:56 +0000 (GMT) (envelope-from grehan@freebsd.org) Received: from [10.33.24.110] (nat-198-95-226-228.netapp.com [198.95.226.228]) by dommail.onthenet.com.au (MOS 3.5.7-GR) with ESMTP id CBP76726 (AUTH peterg@ptree32.com.au); Wed, 30 Aug 2006 13:55:48 +1000 (EST) Message-ID: <44F50C55.5040803@freebsd.org> Date: Tue, 29 Aug 2006 20:56:05 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8b) Gecko/20051014 MIME-Version: 1.0 To: Torfinn Ingolfsen References: <20060830002232.01cda8ac.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20060830002232.01cda8ac.torfinn.ingolfsen@broadpark.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: 7.0-CURRENT-200608 on a G4 - panic 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: Wed, 30 Aug 2006 03:55:57 -0000 Hi Torfinn, > I just tried booting 7.0-CURRENT-200608-powerpc-bootonly.iso on a G4 > (the disc1 image, as reported earlier, doesn't work). > It boots allright, loads the kernel and then panics. > Here's the panic, transcribed from the console screen: > KDB: debugger backends: ddb > KDB: current backend: ddb > panic: mutex kobj named at /usr/src/sys/kern/subr_kobj.c: 178 > [thread pid -1 tid 0 ] > stopped at 0: illegal instruction 0 Was this with a boot by holding down the 'C' key at power up ? If so, it might be possible to try a manual load. Break into Open Firmware and 0 > boot cd:,\boot\loader cd:0 The problem you see has been intermittently happening in releases for a long time now. I've never worked out exactly what's going on. later, Peter.