From owner-freebsd-stable@FreeBSD.ORG Sat Jul 30 08:14:38 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E9B3106566B for ; Sat, 30 Jul 2011 08:14:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B50B98FC0A for ; Sat, 30 Jul 2011 08:14:37 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA24462; Sat, 30 Jul 2011 11:14:35 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qn4gt-000812-9E; Sat, 30 Jul 2011 11:14:35 +0300 Message-ID: <4E33BD6A.4030303@FreeBSD.org> Date: Sat, 30 Jul 2011 11:14:34 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: maestro something References: <4E2E9F60.1060808@FreeBSD.org> <4E33B7CF.90200@FreeBSD.org> In-Reply-To: <4E33B7CF.90200@FreeBSD.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: dtrace ustack kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2011 08:14:38 -0000 on 30/07/2011 00:27 maestro something said the following: > on 30/07/2011 10:50 Andriy Gapon said the following: >> #7 0xc11012d7 in dtrace_panic_trigger () from /boot/kernel/dtrace.ko >> > Previous frame inner to this frame (corrupt stack?) >> > (kgdb) >> > >> > what am I doing wrong and what do I have to do to get the specific assert that >> > fails? > I am not quite sure. Apparently there is some issue with either what > information we store in a crash dump and how, or with how kgdb interprets that > information, or with a combination of both... Or maybe it's because dtrace_panic_trigger is a function implemented in assembly and we do not provide enough debug information to (k)gdb in that case. -- Andriy Gapon