From owner-freebsd-hackers Sat Jun 22 2: 4: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 2D2E537B408 for ; Sat, 22 Jun 2002 02:03:56 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id EB420AE302; Sat, 22 Jun 2002 02:03:55 -0700 (PDT) Date: Sat, 22 Jun 2002 02:03:55 -0700 From: Alfred Perlstein To: Patrick Thomas Cc: Nielsen , hackers@freebsd.org Subject: Re: (jail) problem and a (possible) solution ? Message-ID: <20020622090355.GC53232@elvis.mu.org> References: <200206220652.g5M6qOV84476@utility.clubscholarship.com> <20020622014826.U68572-100000@utility.clubscholarship.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020622014826.U68572-100000@utility.clubscholarship.com> User-Agent: Mutt/1.3.27i 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 * Patrick Thomas [020622 01:56] wrote: > > What it does is the userland hangs, but the kernel keeps running. > ... > I'm mostly just curious if this kind of crash (userland hung but kernel > running) is a possible outcome of someone in a jail fiddling with those > /dev nodes, or if fiddling with dev/mem or /dev/kmem or io would just lock > the machine up hard and completely. > > Terry? This typically means some sort of deadlock has happened, if possible getting a crash dump (this is detailed in the handbook i think) would help. The reason why it seems like apps are responding is because the kernel is only processing interrupts, something has hung the scheduler or deadlocked the kernel somehow... FYI, the kernel is not running except when interrupted by a device. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message