From owner-freebsd-ppc@FreeBSD.ORG Tue May 10 20:54:29 2005 Return-Path: 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 C334616A4CE for ; Tue, 10 May 2005 20:54:29 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6258543D69 for ; Tue, 10 May 2005 20:54:29 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j4AKsSun017812; Tue, 10 May 2005 16:54:28 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <20050510193922.GA34057@ns1.xcllnt.net> References: <20050510193922.GA34057@ns1.xcllnt.net> Date: Tue, 10 May 2005 16:54:27 -0400 To: Marcel Moolenaar From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.4 cc: freebsd-ppc@freebsd.org Subject: Re: Panic, 'giant not owned' kern_mutex.c:299 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2005 20:54:29 -0000 At 12:39 PM -0700 5/10/05, Marcel Moolenaar wrote: >On Tue, May 10, 2005 at 03:30:32PM -0400, Garance A Drosihn wrote: >> I just rebuilt my ppc system last night, and when I try to boot up >> off the new kernel I get: >> >> Trying to mount root from ufs:/dev/ad0s5 >> panic: mutex Giant not owned at /usr/src/sys/kern/kern_mutex.c:299 >> KDB: enter: panic >> [thread pid 1 tid 100006 ] >> Stopped at 0x259ae4: lwz r11, r1, 0x0 >> db> >> >> Do you need more info than that? > >This is the exact same thing I ran into on ia64. The problem appears >to be the default setting of the debug.mpsafevm tunable. If you set >it to 1 in the loader the problem is resolved, although you might >run into other issues. grehan@ is onto it, so you can also wait for >his commit and/or suggestion. Thanks for the quick reply. I think I'll wait for an official fix, just to be on the safe side. Seems a little odd that this 'mpsafe' issues would be popping up on a single-CPU system... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu