Date: Thu, 8 May 2003 13:14:38 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: LOR with -current Message-ID: <16058.36990.299231.566625@grasshopper.cs.duke.edu> In-Reply-To: <20030508.102242.72244093.imp@bsdimp.com> References: <20030508.124929.74756191.haro@kgt.co.jp> <20030508.102242.72244093.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh writes: > In message: <20030508.124929.74756191.haro@kgt.co.jp> > Munehiro Matsuda <haro@kgt.co.jp> 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.. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16058.36990.299231.566625>