Date: Wed, 25 Jan 2012 11:28:51 +0100 From: Denny Schierz <linuxmail@4lin.net> To: freebsd-sparc64@freebsd.org Subject: Re: Howto debug Kernel problems ? (jail -r -> freeze) Message-ID: <431CCA8C-2E5E-43BC-89EE-7F06CF8E8E8D@4lin.net> In-Reply-To: <20120124202111.GB7731@alchemy.franken.de> References: <5C638638-3D1A-417E-A574-9BCE51E08C59@4lin.net> <20120124202111.GB7731@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, Am 24.01.2012 um 21:21 schrieb Marius Strobl: > On Mon, Jan 23, 2012 at 01:16:22PM +0100, Denny Schierz wrote: >> hi, >>=20 >> If I stop a jail (v2 with vnet), the jail doesn't completely = disappear. "jls" shows the jail as active. If I try to remove the jail = with "jail -r <id>" the whole machine freezes. Other users with same = options (i386) doesn't have this problem. So how can I debug it? >>=20 >=20 > I'd start with a kernel built with BREAK_TO_DEBUGGER, DDB and KDB > enabled. Then when it appears to hang try to break into the debugger > by sending a break on the serial console. If that works try to bug > virtualization@ and probably bz@ directly for information they > want as given that you mention vnet it sounds like you're not > seeing this problem without VIMAGE. hmm, all debug options are active and I send the break signal from = ALOM, but I think, that FreeBSD isn't configured to interpret the = signal. Can I enter the kdb first (sysctl debug.kdb.enter=3D1) and than = execute "jail -r 1" ? cu denny=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?431CCA8C-2E5E-43BC-89EE-7F06CF8E8E8D>