Date: Thu, 3 Jul 2008 15:16:48 -0400 From: Ed Maste <emaste@freebsd.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-current@freebsd.org Subject: remove debug.mpsafevfs tunable? (was Re: head panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184) Message-ID: <20080703191648.GA39891@sandvine.com> In-Reply-To: <20080703185833.GQ17123@deviant.kiev.zoral.com.ua> References: <20080703181431.GA10858@sandvine.com> <20080703185833.GQ17123@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 03, 2008 at 09:58:33PM +0300, Kostik Belousov wrote: > On Thu, Jul 03, 2008 at 02:14:31PM -0400, Ed Maste wrote: > > > > Loading configuration files. > > panic: mutex Giant owned at /d2/emaste/svn-head/src/sys/geom/geom_dev.c:184 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 35 tid 100069 ] > > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > db> > > [...] > > Do you have sysctl debug.mpsafevfs=0 ? It turns out that due to an artifact of my lab environment, the tunable debug.mpsafevfs=0 was being set -- thanks for the suggestion! Since it seems the tunable doesn't work properly anymore, and probably isn't at needed at all, should we just remove it? -Ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080703191648.GA39891>