From owner-freebsd-hackers Sun May 5 17: 2:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d182.as14.nwbl0.wi.voyager.net [169.207.136.56]) by hub.freebsd.org (Postfix) with ESMTP id D38E737B401 for ; Sun, 5 May 2002 17:02:31 -0700 (PDT) Received: from patrocles.silby.com (localhost [127.0.0.1]) by patrocles.silby.com (8.12.3/8.12.3) with ESMTP id g4603NUm057701; Sun, 5 May 2002 19:03:23 -0500 (CDT) (envelope-from silby@silby.com) Received: from localhost (silby@localhost) by patrocles.silby.com (8.12.3/8.12.3/Submit) with ESMTP id g4603MhT057698; Sun, 5 May 2002 19:03:23 -0500 (CDT) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Sun, 5 May 2002 19:03:21 -0500 (CDT) From: Mike Silbersack To: Patrick Thomas Cc: freebsd-hackers@freebsd.org Subject: Re: what causes a userland to stop, but allows kernel to continue ? In-Reply-To: <20020505162455.K86733-100000@utility.clubscholarship.com> Message-ID: <20020505184056.J57177-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 5 May 2002, Patrick Thomas wrote: > So, based on a previous thread, it looks like I have a server whose > userland halted, essentially, but the kernel continued running. My guess would be that userland apps are not necessarily stopped, but perhaps a few processes are somehow locking out all others. I think the best way to determine what is happening is for you to compile DDB into your kernel, then break into during the next pseudo-lockup incident to see if you can determine what is going on. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message