From owner-freebsd-current@FreeBSD.ORG Fri Oct 14 21:47:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 851C316A41F for ; Fri, 14 Oct 2005 21:47:10 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23B1743D45 for ; Fri, 14 Oct 2005 21:47:09 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Fri, 14 Oct 2005 18:03:25 -0400 From: John Baldwin To: Andrew Gallatin Date: Fri, 14 Oct 2005 17:48:20 -0400 User-Agent: KMail/1.8.2 References: <17218.49812.271334.154595@grasshopper.cs.duke.edu> <200510141428.46595.jhb@freebsd.org> <17232.8486.199356.888297@grasshopper.cs.duke.edu> In-Reply-To: <17232.8486.199356.888297@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510141748.21113.jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: lockmgr: thread <..> unlocking unheld lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2005 21:47:10 -0000 On Friday 14 October 2005 05:20 pm, Andrew Gallatin wrote: > John Baldwin writes: > > On Thursday 13 October 2005 04:24 pm, Andrew Gallatin wrote: > > > John Baldwin writes: > > > > 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). > > > > > > Inline asm is Greek to me, and I'd be no better than a monkey typing > > > at making changes like that. > > > > > > Would you like me to just try reverting all of 1.38? > > > > > > Drew > > > > Yes, that would work fine. > > I just did a pair of buildworlds, and a portsnap fetch & update, and > got 11 of those messages. So it looks like it wasn't your atomic > changes. > > Drew Ok, just wanted to make sure. Thanks for testing. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org