From owner-freebsd-ppc@FreeBSD.ORG Wed Nov 29 20:47:24 2006 Return-Path: X-Original-To: ppc@freebsd.org Delivered-To: freebsd-ppc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6970216A415 for ; Wed, 29 Nov 2006 20:47:24 +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 4A5EC43CA6 for ; Wed, 29 Nov 2006 20:47:20 +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 CJH12972 (AUTH peterg@ptree32.com.au); Thu, 30 Nov 2006 06:47:10 +1000 (EST) Message-ID: <456DF1F4.6060404@freebsd.org> Date: Wed, 29 Nov 2006 12:47:48 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8b) Gecko/20051014 MIME-Version: 1.0 To: Dario Freni References: <20061122095458.GA86970@builder.freesbie.org> In-Reply-To: <20061122095458.GA86970@builder.freesbie.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ppc@freebsd.org Subject: Re: Instant panic on a recent current 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, 29 Nov 2006 20:47:24 -0000 Hi Dario, > I just upgraded to a -CURRENT from yesterday (previously it was the > 200608 snapshot) and I've got a panic right after the kernel is > booted: > > panic: mutex (null) not owned at /usr/src/sys/vm/vm_page.c:368 > [thread pid 0 tid 0 ] > Stopped at 0x29fb0c: lwz r11, r1, 0x0 Back from holidays and yes, instant panic :( I have a few hacks to try, though maybe it's time for a pmap rewrite :( > Then the ddb prompt, which is unusable with the usb keyboard. And that brings up an interesting point. Console input for devices that have large s/w stacks such as USB is difficult this early in the boot sequence. However, accessing the keyboard through openfirmware (or a PROM i/f such as EFI on other systems) is possible. An experiment I might try is to have an optional 'fallback' for syscons's cngetc, where a PROM call could be done until keyboard devices are probed. This would allow entry to the debugger at boot, which is a worthwhile feature. later, Peter.