From owner-freebsd-current@FreeBSD.ORG Wed Apr 13 10:57:08 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 6EAC516A4CE for ; Wed, 13 Apr 2005 10:57:08 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17C6643D2F for ; Wed, 13 Apr 2005 10:57:08 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from [213.225.74.166] (helo=[10.0.16.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1DLfYQ-0001fF-Mu; Wed, 13 Apr 2005 12:57:07 +0200 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Wed, 13 Apr 2005 12:56:58 +0200 From: Eirik =?ISO-8859-1?B?2A==?=verby To: Jeremie Le Hen Message-ID: In-Reply-To: <20050413105115.GG63229@obiwan.tataz.chchile.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit 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:57:08 -0000 On 13-04-05 12:51, "Jeremie Le Hen" wrote: >> 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. In that case I'm pretty much screwed ... I ran a 'make update' yesterday, but never got around to compiling a new kernel. Damn :( For next time - how do default to building a debug kernel along with the normal one? Thanks for your efforts though.. /Eirik