From owner-freebsd-current@FreeBSD.ORG Sat Aug 27 09:20:10 2005 Return-Path: X-Original-To: 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 CD40D16A41F; Sat, 27 Aug 2005 09:20:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FF4B43D5A; Sat, 27 Aug 2005 09:20:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 9308A1FFACF; Sat, 27 Aug 2005 11:20:08 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 238D71FF90C; Sat, 27 Aug 2005 11:20:06 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 1E08815380; Sat, 27 Aug 2005 09:17:23 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 1387415329; Sat, 27 Aug 2005 09:17:24 +0000 (UTC) Date: Sat, 27 Aug 2005 09:17:23 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Peter Jeremy In-Reply-To: <20050825105945.GH37107@cirb503493.alcatel.com.au> Message-ID: References: <20050825105945.GH37107@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: alc@freebsd.org, FreeBSD current mailing list , Kris Kennaway Subject: Re: panic: _sx_xlock (user map): xlock already held @ ../../../vm/vm_map.c:2997 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: Sat, 27 Aug 2005 09:20:11 -0000 On Thu, 25 Aug 2005, Peter Jeremy wrote: > I just got the same panic on -current from a couple of weeks ago (though > newer than Kris's). In my case, the system had been running happily > for about 3 days and starting mplayer triggered it. The saved message > buffer was: > > lock order reversal > 1st 0xc4097224 vnode interlock (vnode interlock) @ /usr/src/sys/vm/vnode_pager.c:1181 > 2nd 0xc2007898 process lock (process lock) @ /usr/src/sys/i386/i386/trap.c:728 though I am unsure it is helpful I added the LOR with ID 141: http://sources.zabbadoz.net/freebsd/lor.html#141 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT