From owner-freebsd-current@FreeBSD.ORG Wed Apr 13 10:41:04 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 9156B16A4CE for ; Wed, 13 Apr 2005 10:41:04 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3845443D54 for ; Wed, 13 Apr 2005 10:41:04 +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 1DLfIt-0001c2-9y; Wed, 13 Apr 2005 12:41:03 +0200 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Wed, 13 Apr 2005 12:41:01 +0200 From: Eirik =?ISO-8859-1?B?2A==?=verby To: Jeremie Le Hen Message-ID: In-Reply-To: <20050413103710.GF63229@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:41:04 -0000 On 13-04-05 12:37, "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. >> >> 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). On it. Besides, the server fails to reboot at this stage anyway, so it doesn't matter. The server is surveilled 24/7 and all personnel at the monitoring centre knows how to reboot it via power sockets (remote controlled).. Whoever invented those should receive a nobel prize or something ;) > 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. Thanks for your advice! /Eirik > Regards,