From owner-freebsd-questions Mon Jun 11 12:50:23 2001 Delivered-To: freebsd-questions@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 913F937B403; Mon, 11 Jun 2001 12:49:57 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id VAA07055; Mon, 11 Jun 2001 21:49:54 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.4/8.11.4) id f5BJYbe99452; Mon, 11 Jun 2001 21:34:37 +0200 (MET DST) (envelope-from j) Date: Mon, 11 Jun 2001 21:34:37 +0200 From: Joerg Wunsch To: =?iso-8859-1?Q?Carles_G=F3mez?= Cc: "freebsd-questions@FreeBSD.org" , paul@freebsd.org, doc@freebsd.org, teljpa@mat.upc.es, acalveras@mat.upc.es Subject: Re: Problems in debugging kernel crash dumps Message-ID: <20010611213437.O94133@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <3B24EFFE.37C0A4D@mat.upc.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <3B24EFFE.37C0A4D@mat.upc.es>; from carlesgo@mat.upc.es on Mon, Jun 11, 2001 at 06:21:18PM +0200 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Umm, too many recipients...] As Carles Gómez wrote: > # fsck -p > # mount -a -t ufs > # savecore -N /kernel.panicked /var/crash > # exit > > I use those commands, but after typing the "savecore -N ...", the > following message appears on screen: > > savecore: /kernel.panicked : nlist: no such file or directory > savecore: /kernel.panicked : _time_second not in timelist > > Well, it seems like the /kernel.panicked file or directory hasn't been > created. Sure. This is merely meant to be a meta-name for the kernel that has panicked. In your case, it seems it's actually really /kernel still. Note that if you're enabling crash dump recording in /etc/rc.conf (dumpdev="/dev/wd0s1b" in your case), the rc scripts handle the default savecore case (i. e. saving a core dump for the kernel that has been booted again) by default, so you don't need to type it manually in single-user mode as above. The instructions using the name "kernel.panicked" have been written with the idea in mind that your new kernel panics right away when booting. In that case, it's often only possible to boot an alternate kernel (like kernel.old). That however means that the default savecore logic wouldn't work (since it would try to save a coredump for /kernel.old, but the coredump has actually been made from /kernel, again the names are /examples/ only), so you would have to type it manually. Maybe someone from doc@freebsd.org can clarify the wording a little. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message