System borked: loader stack overflow.
lankfordandrew at charter.net
Sun Jan 18 11:19:38 PST 2009
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?
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...:)
More information about the freebsd-stable