From owner-freebsd-current@FreeBSD.ORG Wed Apr 13 10:37:48 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 23B0D16A4CE for ; Wed, 13 Apr 2005 10:37:48 +0000 (GMT) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2BFE43D41 for ; Wed, 13 Apr 2005 10:37:47 +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 postfix4-2.free.fr (Postfix) with ESMTP id 7F2363192F2; Wed, 13 Apr 2005 12:37:46 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 5A90D405A; Wed, 13 Apr 2005 12:37:10 +0200 (CEST) Date: Wed, 13 Apr 2005 12:37:10 +0200 From: Jeremie Le Hen To: Eirik =?iso-8859-1?Q?=D8verby?= Message-ID: <20050413103710.GF63229@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: User-Agent: Mutt/1.5.8i cc: Jeremie Le Hen 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:37:48 -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. > > I understand that, but this is a production server that has otherwise been > stable for a long time. I suspect that this won't happen again for a while. > > I'll reconfigure it as you suggest at the next opportunity ;) In case of a production server, you should be sure that you want to drop to debugger on panic since the machine won't reboot itself and thus will be down until human intervention. What I would advise you for now is to configure your rc.conf(5) in order to allow rc.d/savecore to save a coredump (see my previous mail). Since you must have rebooted your server now without having dumpdev and dumpdir set in rc.conf(5) at boot time, you should manually run dumpon -v $your_swap_device With this, upon next panic, FreeBSD will try to dump the whole memory into you swap device and then rc.d/savecore will save it in a file when booting. Finally, be sure that you will have enough space on the filesystem where $dumpdir points to. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >