Date: Sat, 27 Aug 2005 09:17:23 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: alc@freebsd.org, FreeBSD current mailing list <current@freebsd.org>, Kris Kennaway <kris@obsecurity.org> Subject: Re: panic: _sx_xlock (user map): xlock already held @ ../../../vm/vm_map.c:2997 Message-ID: <Pine.BSF.4.53.0508270916370.969@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <20050825105945.GH37107@cirb503493.alcatel.com.au> References: <20050825105945.GH37107@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0508270916370.969>