From owner-freebsd-current@FreeBSD.ORG Wed Apr 13 10:51:50 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 419D916A4CE for ; Wed, 13 Apr 2005 10:51:50 +0000 (GMT) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8CA843D4C for ; Wed, 13 Apr 2005 10:51:49 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-2.free.fr (Postfix) with ESMTP id 37AF5C085; Wed, 13 Apr 2005 12:51:49 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id EADA1405A; Wed, 13 Apr 2005 12:51:15 +0200 (CEST) Date: Wed, 13 Apr 2005 12:51:15 +0200 From: Jeremie Le Hen To: Eirik =?iso-8859-1?Q?=D8verby?= Message-ID: <20050413105115.GG63229@obiwan.tataz.chchile.org> References: <20050413094338.GE63229@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050413094338.GE63229@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.8i cc: "current@freebsd.org" Subject: Re: Panic after "in_cksum_skip: out of data by 260" 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: Wed, 13 Apr 2005 10:51:50 -0000 > I have no idea about what could have caused this, but in this case, it > would be useful to have a crashdump and its associated kernel.debug file, > or at least a backtrace (but you must have enabled the break to debugger > on panic). I guess you could also use addr2line(1) to determine which > function caused the panic from the instruction pointer, but it's likely > not enough to help understanding the problem. Since it's a NULL pointer derefence, mux@ told me the addr2line(1) result could be relevant, assuming you have a debug kernel compiled. Could you give back the result of the following command please : addr2line -e kernel.debug 0xc066ec33 Once addr2line(1) gave you the file and the line, it is also important to tell us the revision of the file. If you don't have a debug kernel, and you *absolutely* change neither the sources from which you compiled it nor the kernel configuration file, you should be able to rebuild it. -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >