From owner-freebsd-pf@FreeBSD.ORG Tue Jun 28 15:49:17 2011 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50D60106566C for ; Tue, 28 Jun 2011 15:49:17 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id DED558FC13 for ; Tue, 28 Jun 2011 15:49:16 +0000 (UTC) Received: by wyg24 with SMTP id 24so336204wyg.13 for ; Tue, 28 Jun 2011 08:49:15 -0700 (PDT) Received: by 10.227.55.67 with SMTP id t3mr6621239wbg.90.1309276155799; Tue, 28 Jun 2011 08:49:15 -0700 (PDT) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id fi5sm248118wbb.39.2011.06.28.08.49.14 (version=SSLv3 cipher=OTHER); Tue, 28 Jun 2011 08:49:14 -0700 (PDT) Message-ID: <4E09F7F9.3080608@my.gd> Date: Tue, 28 Jun 2011 17:49:13 +0200 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: Espartano References: <4E099A36.7000104@my.gd> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-pf@freebsd.org Subject: Re: Reboot after start pf on ALIX board X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 15:49:17 -0000 On 6/28/11 4:25 PM, Espartano wrote: > On Tue, Jun 28, 2011 at 4:09 AM, Damien Fleuriot wrote: >> >> You need to define a dump device then, so that you may extract the >> kernel's crash dump for analysis. > > > I don't know if there is enought free space to allocate a kernel dump > file into the Alix board's cf card, I will see if it is possible. > > >> >> >> >> [SNIP] >> >> >>> >>> Before I updated my Nanobsd image from FreeBSD 8.1 to 8.2 RELEASE my >>> alix board worked very well, the big diference between my old nanobsd >>> image and my new nanobsd image is that the new one have "option >>> VIMAGE" active. >>> >> >> Well, the next logical step would be to comment out the VIMAGE option >> and rebuild a kernel don't you think ? >> > > Of course, however I wanted to know if this scenario is useful to the > freebsd pf developers. > >> >>> >>> Could someone help me ? >>> >>> If there is some another thing that you need to figure out what was >>> happen please let me know. >>> >> >> Describe the procedure you followed to update your machine. >> >> It is possible that you did not update correctly, who knows... >> >> > > I don't think so, when I said "update" I really have installed Nanobsd > using FreeBSD 8.2 from scratch. > > > Well at this point I don't know what to do, it is useful for you that > I try to get a kernel dump file ? or simply recompile nanobsd without > vimage option ? > > > Thanks a lot. Well, you want to try things in this order: 1/ rebuild a kernel without VIMAGE and try again, while you're at it enable debug options like the KDTRACE hooks and such. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options KDB # Kernel debugger related code options KDTRACE_FRAME # Ensure frames are compiled in options KDTRACE_HOOKS # Kernel DTrace hooks 2/ enable kernel crash dumps, reproduce problem, obtain a dump for analysis.