From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 25 16:05:32 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 426B61065676 for ; Wed, 25 Jan 2012 16:05:32 +0000 (UTC) (envelope-from boland37@xs4all.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.freebsd.org (Postfix) with ESMTP id C0C2D8FC12 for ; Wed, 25 Jan 2012 16:05:31 +0000 (UTC) Received: from charlemagne.boland.org (150-42-215.ftth.xms.internl.net [82.215.42.150]) (authenticated bits=0) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id q0PFrgPQ015308 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Wed, 25 Jan 2012 16:53:43 +0100 (CET) (envelope-from boland37@xs4all.nl) Message-ID: <4F202586.5010808@xs4all.nl> Date: Wed, 25 Jan 2012 16:53:42 +0100 From: Michiel Boland User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.25) Gecko/20120114 Thunderbird/3.1.17 MIME-Version: 1.0 To: freebsd-sparc64@freebsd.org References: <5C638638-3D1A-417E-A574-9BCE51E08C59@4lin.net> <20120124202111.GB7731@alchemy.franken.de> <431CCA8C-2E5E-43BC-89EE-7F06CF8E8E8D@4lin.net> <20120125150054.GA15762@alchemy.franken.de> <926170B2-9DF2-4DCC-9643-E66E6504B185@4lin.net> In-Reply-To: <926170B2-9DF2-4DCC-9643-E66E6504B185@4lin.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner 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: Wed, 25 Jan 2012 16:05:32 -0000 On 01/25/2012 16:09, Denny Schierz wrote: > > Am 25.01.2012 um 16:00 schrieb Marius Strobl: >> >> Not that I'm aware of. Do you have a kernel built with options >> BREAK_TO_DEBUGGER? Does it work when the machine doesn't hang > > jupp, I have > >> (you can resume via the "continue" command in the kernel > > works too > >> debugger)? Do you send the break via the "break" command of the >> ALOM or by sending a break via a terminal attached to the ALOM >> console? > > > ssh alom -> login -> type break -> type console -f -> normal freebsd console > > but, It happens nothing. I expected to get into the kdb. > > cu denny What happens if you do # sysctl debug.kdb.alt_break_to_debugger=1 then type the alternate break sequence (Enter ~ ^B) on the console?