Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Dec 2003 20:20:21 +0100
From:      "Christoph P. Kukulies" <kuku@kukulies.org>
To:        Robert Watson <rwatson@freebsd.org>
Cc:        freebsd-mobile@freebsd.org
Subject:   Re: lock order reversals - what do they mean?
Message-ID:  <20031214192021.GA18834@gilberto.physik.rwth-aachen.de>
In-Reply-To: <Pine.NEB.3.96L.1031214123127.58831C-100000@fledge.watson.org>
References:  <200312141145.hBEBjxJo016494@www.kukulies.org> <Pine.NEB.3.96L.1031214123127.58831C-100000@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 14, 2003 at 12:34:59PM -0500, Robert Watson wrote:
> 
> On Sun, 14 Dec 2003, C. Kukulies wrote:
> 
> > I'm getting 
> > lock order reversal
> >  1st 0xc09524c0 UMA lock (UMA lock) @ /u/src/sys/vm/uma_core.c:1200
> >  2nd 0xc1431100 system map (system map) @ /u/src/sys/vm/vm_map.c:2210
> > Stack backtrace:
> > 
> > This happenend while doing a find . something on my notebook hd. 
> 
> These warnings are generated by Witness, a run-time lock diagnostic system
> found in FreeBSD 5-CURRENT kernels (but removed in releases).  You can
> read more about Witness in the WITNESS(4) man page, which talks about its
> capabilities.  Among other things, Witness performs run-time lock order
> verification using a combination of hard coded lock orders, and run-time

Thanks for the information. 

--
Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de



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