From owner-freebsd-current Sun Nov 17 11:46:37 2002 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 0579C37B401 for ; Sun, 17 Nov 2002 11:46:36 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1581543E3B for ; Sun, 17 Nov 2002 11:46:35 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gAHJdTBF006114; Sun, 17 Nov 2002 14:39:29 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 17 Nov 2002 14:39:29 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: Processes hanging in thrd_sleep In-Reply-To: <20021117105919.GA677@rot13.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I ran into that during heavy builds on one of my boxes a few months ago -- I never really got around to properly debugging it because the UFS file systems promptly ate themselves. Oddly, I had two boxes in particular that this happened on, and none of my others, and it wasn't clear to me if there was a useful pattern. I will try reproducing it sometime this weekend. Basically, the system seemed fairly live, but any attempt to execve() would hang the process in that sleep state. It looked a bit like a VM lock leak followed by piling up on locks into a deadlock staet. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories On Sun, 17 Nov 2002, Kris Kennaway wrote: > Since upgrading my kernel to today's current (from a couple of weeks > ago) I have had a number of hangs where processes block in the kernel, > usually in the thrd_sleep state (but once one hung in the ufs state). > > e.g: > > > load: 0.01 cmd: cc 708 [ufs] 0.00u 0.00s 0% 56k > > > load: 0.01 cmd: tcsh 709 [thrd_sleep] 0.00u 0.00s 0% 1220k > > I've seen this on my sparc64 box as well as an i386 box. > > Any bright ideas? Anyone feeling guilty? :) > > Kris > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message