From owner-freebsd-current Sat Nov 24 16:53:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112]) by hub.freebsd.org (Postfix) with ESMTP id 75D8537B405 for ; Sat, 24 Nov 2001 16:53:28 -0800 (PST) Received: (from mux@localhost) by noos.fr (8.11.6/8.11.4) id fAP0rPs01218; Sun, 25 Nov 2001 01:53:25 +0100 (CET) (envelope-from mux) Date: Sun, 25 Nov 2001 01:53:25 +0100 From: Maxime Henrion To: Hiten Pandya Cc: current@FreeBSD.org Subject: Re: some info (new) Message-ID: <20011125015325.B831@nebula.noos.fr> References: <20011125014200.A831@nebula.noos.fr> <20011125004705.22380.qmail@web21109.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011125004705.22380.qmail@web21109.mail.yahoo.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiten Pandya wrote: > one more question... if there is a lock order > reversal.. is there a way that can be solved.. for > e.g. by using on of the MTX_XX things... The lock order verification is not part of the mtx API. It's debugging stuff activated by default in -CURRENT. If you do not want to see these warnings, remove ``options WITNESS'' from your kernel conf or patch the code to solve the problem :-) Regards, Maxime Henrion -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message