From owner-freebsd-current@FreeBSD.ORG Fri Oct 14 21:20:50 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 B88DF16A41F; Fri, 14 Oct 2005 21:20:50 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B6BA43D45; Fri, 14 Oct 2005 21:20:44 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.4/8.13.4) with ESMTP id j9ELKhgQ005997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Oct 2005 17:20:43 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id j9ELKcBZ013740; Fri, 14 Oct 2005 17:20:38 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17232.8486.199356.888297@grasshopper.cs.duke.edu> Date: Fri, 14 Oct 2005 17:20:38 -0400 (EDT) To: John Baldwin In-Reply-To: <200510141428.46595.jhb@freebsd.org> References: <17218.49812.271334.154595@grasshopper.cs.duke.edu> <200510131530.16376.jhb@freebsd.org> <17230.49819.985757.378764@grasshopper.cs.duke.edu> <200510141428.46595.jhb@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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:20:50 -0000 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