From owner-freebsd-stable@FreeBSD.ORG Thu Feb 22 16:28:31 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F32816A404 for ; Thu, 22 Feb 2007 16:28:31 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.192.81]) by mx1.freebsd.org (Postfix) with ESMTP id 0A8A813C428 for ; Thu, 22 Feb 2007 16:28:31 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-71-198-0-135.hsd1.ca.comcast.net[71.198.0.135]) by comcast.net (rwcrmhc11) with ESMTP id <20070222162830m1100jee4ue>; Thu, 22 Feb 2007 16:28:30 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 105511FA01F; Thu, 22 Feb 2007 08:28:25 -0800 (PST) Date: Thu, 22 Feb 2007 08:28:25 -0800 From: Jeremy Chadwick To: Alexander Shikoff Message-ID: <20070222162824.GA24305@icarus.home.lan> Mail-Followup-To: Alexander Shikoff , freebsd-stable@freebsd.org References: <20070222115644.GA55416@crete.org.ua> <20070222132224.GA14615@icarus.home.lan> <20070222141333.GA60026@crete.org.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070222141333.GA60026@crete.org.ua> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@freebsd.org Subject: Re: Cannot obtain kernel dump in /var/crash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Feb 2007 16:28:31 -0000 On Thu, Feb 22, 2007 at 04:13:33PM +0200, Alexander Shikoff wrote: > /etc/rc.d/dumpon creates symbolic link /dev/dumpdev. It's present in > my /dev directory. I think a problem is somewhere deeply, probably > with savecore(8). When a panic occurs I see in console process of > dumping (size of RAM, number of pages, dump device etc.) and it's > completely normal. Anything shown on the actual console? There's some error conditions which emit messages via syslog() only (see lines ~278-286 of src/sbin/savecore/savecore.c). Also, any chance of output from savecore -f -vv? There's some extra debugging info which might come in handy (lines ~288 of src/sbin/savecore/savecore.c). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |