From owner-freebsd-current@FreeBSD.ORG Thu Sep 30 19:07:18 2004 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 7C72916A4CE for ; Thu, 30 Sep 2004 19:07:18 +0000 (GMT) Received: from linwhf.opal.com (119.79.171.66.subscriber.vzavenue.net [66.171.79.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id C88DD43D41 for ; Thu, 30 Sep 2004 19:07:17 +0000 (GMT) (envelope-from jr@linwhf.opal.com) Received: from linwhf.opal.com (localhost [127.0.0.1]) by linwhf.opal.com (8.13.1/8.13.1) with ESMTP id i8UJ7GQb001333; Thu, 30 Sep 2004 15:07:16 -0400 (EDT) (envelope-from jr@linwhf.opal.com) Received: (from jr@localhost) by linwhf.opal.com (8.13.1/8.13.1/Submit) id i8UJ7Gd9001332; Thu, 30 Sep 2004 15:07:16 -0400 (EDT) (envelope-from jr) Date: Thu, 30 Sep 2004 15:07:16 -0400 From: "J.R. Oldroyd" To: Kris Kennaway Message-ID: <20040930190716.GA1236@linwhf.opal.com> References: <20040930184729.GA836@linwhf.opal.com> <20040930185842.GA4759@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20040930185842.GA4759@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: panic after "ifconfig gif0 destroy" 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: Thu, 30 Sep 2004 19:07:18 -0000 After the panic message, the system stops dead. No traceback, no addresses, nothing more. -jr On Sep 30, 11:58, Kris Kennaway wrote: > On Thu, Sep 30, 2004 at 02:47:46PM -0400, J.R. Oldroyd wrote: > > The command: > > # ifconfig gif0 destroy > > panic: page fault > >=20 > > isn't really ideal behavior. >=20 > Nor is this really an ideal bug report ;-) >=20 > You need to post a debugging traceback of the panic, or at the very > least look up the PC address in your kernel with addr2line. >=20 > Kris