Date: Wed, 11 May 2005 16:15:46 +1000 From: Peter Grehan <grehan@freebsd.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-ppc@freebsd.org Subject: Re: Panic, 'giant not owned' kern_mutex.c:299 Message-ID: <4281A312.2010808@freebsd.org> In-Reply-To: <p0621020bbea6c8ec4db8@[128.113.24.47]> References: <p06210208bea6bb371756@[128.113.24.47]> <20050510193922.GA34057@ns1.xcllnt.net> <p0621020bbea6c8ec4db8@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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... I'm running a buildworld to see if inverting mpsafevm is OK. A pre-emptive UP kernel is isn't too far different from an MP system - it's still prone to locking issues and race conditions. BTW, should be getting the mini shortly ! later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4281A312.2010808>