Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 May 2005 16:54:27 -0400
From:      Garance A Drosihn <drosih@rpi.edu>
To:        Marcel Moolenaar <marcel@xcllnt.net>
Cc:        freebsd-ppc@freebsd.org
Subject:   Re: Panic, 'giant not owned' kern_mutex.c:299
Message-ID:  <p0621020bbea6c8ec4db8@[128.113.24.47]>
In-Reply-To: <20050510193922.GA34057@ns1.xcllnt.net>
References:  <p06210208bea6bb371756@[128.113.24.47]> <20050510193922.GA34057@ns1.xcllnt.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0621020bbea6c8ec4db8>