Date: Tue, 02 Dec 2003 15:29:59 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Robert Watson <rwatson@FreeBSD.org> Cc: Current <freebsd-current@FreeBSD.org> Subject: Re: -current lockup (how to diagnose?) Message-ID: <7mad6bbul4.wl@black.imgsrc.co.jp> In-Reply-To: <Pine.NEB.3.96L.1031201092204.74465L-100000@fledge.watson.org> References: <7mznedas57.wl@black.imgsrc.co.jp> <Pine.NEB.3.96L.1031201092204.74465L-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Mon, 1 Dec 2003 09:23:21 -0500 (EST), Robert Watson wrote: > This could be a sign of a VM or VFS lock leak or deadlock. I'd advise > hooking up a serial console, dropping to DDB over serial line, and posting > the results of "ps" and "show lockedvnods". We might then ask you to use > the "show locks" command on various processes. You'll need to have DDB > and WITNESS compiled in. I got it. http://www.imgsrc.co.jp/~kuriyama/BSD/lock-20031202.log -- Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc. <kuriyama@FreeBSD.org> // FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mad6bbul4.wl>