From owner-freebsd-stable@FreeBSD.ORG Tue Nov 15 22:46:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7172416A41F for ; Tue, 15 Nov 2005 22:46:29 +0000 (GMT) (envelope-from dscheidt@panix.com) Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE9C343D5A for ; Tue, 15 Nov 2005 22:46:28 +0000 (GMT) (envelope-from dscheidt@panix.com) Received: from panix3.panix.com (panix3.panix.com [166.84.1.3]) by mail2.panix.com (Postfix) with ESMTP id D3C8F9DE7D; Tue, 15 Nov 2005 17:46:27 -0500 (EST) Received: (from dscheidt@localhost) by panix3.panix.com (8.11.6p3/8.8.8/PanixN1.1) id jAFMkSj12248; Tue, 15 Nov 2005 17:46:28 -0500 (EST) Date: Tue, 15 Nov 2005 17:46:28 -0500 From: David Scheidt To: Kris Kennaway Message-ID: <20051115224627.GA20092@panix.com> References: <4378CD2B.20208@kabelnet.net> <20051114200119.GA82582@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051114200119.GA82582@xor.obsecurity.org> User-Agent: Mutt/1.5.10i Cc: Ales , freebsd-stable@freebsd.org Subject: Re: Strange boot messages under 6.0-STABLE 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: Tue, 15 Nov 2005 22:46:29 -0000 On Mon, Nov 14, 2005 at 03:01:19PM -0500, Kris Kennaway wrote: > On Mon, Nov 14, 2005 at 06:45:15PM +0100, Ales wrote: > > During boot process under 6.0-STABLE I spoted some strange messages. > > > > Nov 14 18:18:45 romcek savecore: reboot after panic: page fault > > Nov 14 18:18:45 romcek savecore: no dump, not enough free space on > > Your system panicked at some point in the past, but it can't save the > dump for the reason specified. If you just want to prevent the message from printing at the next boot time, run 'savecore -c'. If you want to try and retrieve the dump, you can specify an alternate location to save the dump on the savecore command line. David