Date: Tue, 27 Feb 2007 15:26:08 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Robert Watson <rwatson@freebsd.org>, Jiawei Ye <leafy7382@gmail.com> Subject: Re: Processes stuck in *unp_m after recent uipc changes Message-ID: <200702271526.09457.jhb@freebsd.org> In-Reply-To: <20070227090505.K56223@fledge.watson.org> References: <c21e92e20702270007u277d6a9xfaca7883da9dedd@mail.gmail.com> <20070227084214.Y56223@fledge.watson.org> <20070227090505.K56223@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 27 February 2007 04:05, Robert Watson wrote: > On Tue, 27 Feb 2007, Robert Watson wrote: > > > On Tue, 27 Feb 2007, Jiawei Ye wrote: > > > >> With the latest uipc locking changes, I experienced a hard lockup on my > >> -current machine. Many processes got stuck in *unp_m state and > >> ctrl-alt-delete at the console cannot properly restart the machine and I > >> had to hard-reset (no coredump available). Is there anyway to diagnose > >> this? > > > > Please configure WITNESS, DDB, and BREAK_TO_DEBUGGER on a box with a serial > > console. Then attach the output of "ps", "show alllocks", and "alltrace" to > > an e-mail. With any luck, this is a leaked lock in some missed error case > > and we can just add a missing unlock. Thanks! > > Obviously, INVARIANTS also good on general principle. :-) > > See the handbook chapter on debugging, and in particular live DDB debugging, > if you're running into any problems. 'show allchains' also considered helpful as it will reveal any deadlocks. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200702271526.09457.jhb>