Date: Sat, 22 Jun 2002 02:03:55 -0700 From: Alfred Perlstein <bright@mu.org> To: Patrick Thomas <root@utility.clubscholarship.com> Cc: Nielsen <nielsen@memberwebs.com>, hackers@freebsd.org Subject: Re: (jail) problem and a (possible) solution ? Message-ID: <20020622090355.GC53232@elvis.mu.org> In-Reply-To: <20020622014826.U68572-100000@utility.clubscholarship.com> References: <200206220652.g5M6qOV84476@utility.clubscholarship.com> <20020622014826.U68572-100000@utility.clubscholarship.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Patrick Thomas <root@utility.clubscholarship.com> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020622090355.GC53232>