LOR with -current
M. Warner Losh
imp at bsdimp.com
Thu May 8 10:19:08 PDT 2003
In message: <16058.36990.299231.566625 at grasshopper.cs.duke.edu>
Andrew Gallatin <gallatin at cs.duke.edu> writes:
:
: M. Warner Losh writes:
: > In message: <20030508.124929.74756191.haro at kgt.co.jp>
: > Munehiro Matsuda <haro at 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..
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
More information about the freebsd-current
mailing list