From owner-freebsd-current@FreeBSD.ORG Sat Mar 5 19:05:00 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33C8116A4CE for ; Sat, 5 Mar 2005 19:05:00 +0000 (GMT) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by mx1.FreeBSD.org (Postfix) with SMTP id AC7DC43D67 for ; Sat, 5 Mar 2005 19:04:59 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO 172.16.0.1) (mikej@69.193.222.195 with login) by smtp100.rog.mail.re2.yahoo.com with SMTP; 5 Mar 2005 19:04:58 -0000 Received: from 172.16.0.199 (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Sat, 5 Mar 2005 14:05:06 -0500 (EST) Message-ID: <1646.172.16.0.199.1110049506.squirrel@172.16.0.199> In-Reply-To: <20050304230723.T4084@carver.gumbysoft.com> References: <2861.172.16.0.199.1109814152.squirrel@172.16.0.199> <20050303015438.GF15329@obiwan.tataz.chchile.org> <2910.172.16.0.199.1109816379.squirrel@172.16.0.199> <20050304230723.T4084@carver.gumbysoft.com> Date: Sat, 5 Mar 2005 14:05:06 -0500 (EST) From: "Mike Jakubik" To: "Doug White" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Reproducible Panic with port iplog X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2005 19:05:00 -0000 Doug White said: > I'll see if I can reproduce this, but in the interim you might try > disabling PREEMPTION. It doesn't quite have all the bugs worked out yet. Disabling PREEMPTION does indeed stop the panic from occuring. > If you want to get a dump try compiling in KDB and DDB then doing "call > doadump" when it panics. It should either start dumping or complain why > it can't. Last I checked dumps to ATA worked :) Typing "call doadump" in the kernel debugger does work. Is there no way to have the kernel automatically do a dump when the system panics and there is no debugger compiled in?