From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 19:19:37 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C23F8106564A for ; Sun, 18 Jan 2009 19:19:37 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mta11.charter.net (mta11.charter.net [216.33.127.80]) by mx1.freebsd.org (Postfix) with ESMTP id 581D88FC08 for ; Sun, 18 Jan 2009 19:19:37 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv06.charter.net ([10.20.200.76]) by mta11.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090118191924.DYGC21265.mta11.charter.net@aarprv06.charter.net> for ; Sun, 18 Jan 2009 14:19:24 -0500 Received: from [192.168.1.151] (really [68.191.116.244]) by aarprv06.charter.net with ESMTP id <20090118191924.GISH128.aarprv06.charter.net@[192.168.1.151]> for ; Sun, 18 Jan 2009 14:19:24 -0500 Message-ID: <497380BB.1050409@charter.net> Date: Sun, 18 Jan 2009 14:19:23 -0500 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: stable@freebsd.org References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> <20090118185605.GA28874@citylink.fud.org.nz> In-Reply-To: <20090118185605.GA28874@citylink.fud.org.nz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 Cc: Subject: Re: System borked: loader stack overflow. 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: Sun, 18 Jan 2009 19:19:38 -0000 Andrew Thompson wrote: > On Sun, Jan 18, 2009 at 05:47:24PM +0100, Luigi Rizzo wrote: > >> On Sun, Jan 18, 2009 at 10:38:51AM -0500, Andrew Lankford wrote: >> >>> I can't say what version of the loader it is that I'm using, but >>> (following Peter's advice, thanks), I've tried loader.old (about a week >>> old) and the latest loader (built yesterday), and both start. Where >>> each loader has a problem appears to be reading (include-ing?) >>> /boot/default/loader.conf . The spinner spins for a longer time than >>> >> ok so the problem could be is a recursive assignment of loader_conf_files >> in your previous installation (either as a result of the default >> installation, or because of manual modifications). >> Could you please send me a copy of your /boot/loader.conf and >> /boot/defaults/loader.conf so i can check ? >> >> A recent commit fixed the handling of loader_conf_files, >> which previously was broken (in some cases assignments were ignored). >> A side effect of the fix is that now certain errors in the config >> files are now detected as such. >> > > Having the following in /boot/loader.conf triggers it for me, > > loader_conf_files="/boot/device.hints /boot/loader.conf" > > You may say thats its an invalid config line but the loader shouldnt > blow up from it. Can this be fixed up somehow? > > Andrew > > Indeed, it would be nice if um someone (anyone, mind you) with commit priviledges might put some descriptive comments around the "default-only" settings in /boot/default/loader.conf...:) Andrew Lankford