From owner-freebsd-current@FreeBSD.ORG Thu May 8 10:19:08 2003 Return-Path: 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 89BEF37B401 for ; Thu, 8 May 2003 10:19:08 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9796B43F75 for ; Thu, 8 May 2003 10:19:07 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h48HJ4Tl020726; Thu, 8 May 2003 11:19:04 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 08 May 2003 11:18:36 -0600 (MDT) Message-Id: <20030508.111836.130233489.imp@bsdimp.com> To: gallatin@cs.duke.edu From: "M. Warner Losh" In-Reply-To: <16058.36990.299231.566625@grasshopper.cs.duke.edu> References: <20030508.124929.74756191.haro@kgt.co.jp> <20030508.102242.72244093.imp@bsdimp.com> <16058.36990.299231.566625@grasshopper.cs.duke.edu> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: LOR with -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 08 May 2003 17:19:08 -0000 In message: <16058.36990.299231.566625@grasshopper.cs.duke.edu> Andrew Gallatin writes: : : M. Warner Losh writes: : > In message: <20030508.124929.74756191.haro@kgt.co.jp> : > Munehiro Matsuda writes: : > : Hi all, : > : : > : I got this LOR with today's -current, when I tried to start X Window up. : > : : > : lock order reversal : > : 1st 0xc30b94c0 vm object (vm object) @ vm/vm_object.c:507 : > : 2nd 0xc082f110 system map (system map) @ vm/vm_kern.c:325 : > : > That reminds me, would anybody object if I were to hack traceback so : > that it would actually put the traceback in the dmesg buffer when not : > called from ddb? : : FWIW, I think that tracebacks generated from DDB_TRACE should also : go into the dmesg buffer. It would save quite a few initial exchanges : with users.. Does anybdoy know why the ddb output doesn't go into the dmesg buffer in general? It sure would save me a lot of grief as well if it did. Warner