From owner-freebsd-questions@FreeBSD.ORG Wed Jun 25 14:12:11 2008 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BD3B106566B for ; Wed, 25 Jun 2008 14:12:11 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from mail.televork.ee (mail.televork.ee [IPv6:2a01:1b8:0:2::22]) by mx1.freebsd.org (Postfix) with ESMTP id D8D368FC12 for ; Wed, 25 Jun 2008 14:12:10 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from localhost (localhost [127.0.0.1]) by mail.televork.ee (Postfix) with ESMTP id 1E52714DD72 for ; Wed, 25 Jun 2008 17:12:07 +0300 (EEST) Received: from mail.televork.ee ([81.21.240.22]) by localhost (mail.televork.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26933-08 for ; Wed, 25 Jun 2008 17:12:00 +0300 (EEST) Received: from bsd.kodu.lan (77-233-66-250.cdma.dyn.kou.ee [77.233.66.250]) by mail.televork.ee (Postfix) with ESMTP id 83A3414DDB4 for ; Wed, 25 Jun 2008 17:11:59 +0300 (EEST) From: Toomas Aas Organization: Tartu Linnavalitsus To: questions@freebsd.org Date: Wed, 25 Jun 2008 17:11:56 +0300 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806251711.56906.toomas.aas@raad.tartu.ee> X-Virus-Scanned: at mail.televork.ee Cc: Subject: Cannot get kernel core dump X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 14:12:11 -0000 Hello! I'm trying to report a problem which involves kernel panic, but I cannot get a core dump. The system is 7.0-STABLE from June 18th. I've set the following in /etc/rc.conf (and of course rebooted, even several times): dumpdev="/dev/ad0s1b" dumpdir="/home/crash" The machine has 512 MB RAM and swap partition is also 512 MB, but according to dumpon(8) this shouldn't be a problem, because hw.physmem is still somewhat smaller than the swap partition: bsd# sysctl hw.physmem hw.physmem: 527863808 bsd# swapinfo Device 1K-blocks Used Avail Capacity /dev/ad0s1b 524288 0 524288 0% /home partition, where I've created the crash directory, has 55 GB free space. When the machine boots up, it dutifully reports: kernel dumps on /dev/ad0s1b Then I "do the thing" that causes the panic. System prints the panic message and hangs. Only thing left to do is press the reset button. On next boot, the log says savecore: no dumps found When the system panics and prints the panic message, it doesn't say anything about saving the coredump. I haven't had a kernel panic for a long time, but I seem to remember that in the past there was some kind of message to that effect. Are there known conditions under which the core dump really isn't recorded, or am I simply missing something obvious? -- Toomas