Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Oct 2005 15:30:14 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-current@freebsd.org
Cc:        Andrew Gallatin <gallatin@cs.duke.edu>, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: lockmgr: thread <..> unlocking unheld lock
Message-ID:  <200510131530.16376.jhb@freebsd.org>
In-Reply-To: <17220.5283.170670.956780@grasshopper.cs.duke.edu>
References:  <17218.49812.271334.154595@grasshopper.cs.duke.edu> <20051004195742.GA56798@xor.obsecurity.org> <17220.5283.170670.956780@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 05 October 2005 02:00 pm, Andrew Gallatin wrote:
> It also seems to have started happening on a second amd64 that I just
> upgraded from a mid-august -current to CVS cvsupped yesterday.  This
> is a UP amd64 3000+..

Can you try reverting any of the recent changes to amd64/include/atomic.h?  
The ones to change foo_ptr() to take uintptr_t should be fine, but maybe try 
reverting the changes after that (not using +m for example).

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org



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