From owner-freebsd-sparc64@FreeBSD.ORG Tue Jan 24 20:21:16 2012 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BFFB106564A for ; Tue, 24 Jan 2012 20:21:16 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id DC3958FC17 for ; Tue, 24 Jan 2012 20:21:15 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id q0OKLDLR007772; Tue, 24 Jan 2012 21:21:14 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id q0OKLBIV007771; Tue, 24 Jan 2012 21:21:11 +0100 (CET) (envelope-from marius) Date: Tue, 24 Jan 2012 21:21:11 +0100 From: Marius Strobl To: Denny Schierz Message-ID: <20120124202111.GB7731@alchemy.franken.de> References: <5C638638-3D1A-417E-A574-9BCE51E08C59@4lin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5C638638-3D1A-417E-A574-9BCE51E08C59@4lin.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Howto debug Kernel problems ? (jail -r -> freeze) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2012 20:21:16 -0000 On Mon, Jan 23, 2012 at 01:16:22PM +0100, Denny Schierz wrote: > hi, > > 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 " the whole machine freezes. Other users with same options (i386) doesn't have this problem. So how can I debug it? > 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. Marius