From owner-freebsd-stable@FreeBSD.ORG Wed Jan 23 14:49:47 2008 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 3679F16A419; Wed, 23 Jan 2008 14:49:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 02B8C13C46A; Wed, 23 Jan 2008 14:49:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 21A0F1A4D8C; Wed, 23 Jan 2008 06:45:55 -0800 (PST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 23 Jan 2008 09:30:37 -0500 User-Agent: KMail/1.9.7 References: <004b01c85c4e$e1c44540$a54ccfc0$@muni.cz> <4795A2EE.1020605@yandex.ru> <001901c85ce1$6b72ecf0$4258c6d0$@muni.cz> In-Reply-To: <001901c85ce1$6b72ecf0$4258c6d0$@muni.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801230930.38405.jhb@freebsd.org> Cc: stable@freebsd.org, Petr Holub , 'Kris Kennaway' , "'Andrey V. Elsukov'" , rwatson@freebsd.org, 'Colin Percival' Subject: Re: 6.3-RELEASE 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: Wed, 23 Jan 2008 14:49:47 -0000 On Tuesday 22 January 2008 05:27:36 am Petr Holub wrote: > > > I thought we shipped the debugging symbols in /boot precisely for the > > > reason of making panics with default installs not report useless traces > :( > > > > I think building GENERIC kernel from sources with > > tag=RELENG_6_3_0_RELEASE will help. > > I tried to build it from the sources that come from the freebsd-update > and thus I assume they are actually RELENG_6_3_0_RELEASE. Still I was > unable to run gdb with the given vmcore against such a kernel. You will need to build a debug kernel and reproduce the panic and use kgdb on the new crash with the new kernel. -- John Baldwin