After rebuilding world from 7-stable after cvsup, I can no longer boot. The loader tries to load the kernel but instead locks up with a stack overflow. Wish I could send more details, but I'll have to find another way to boot up my system first. Andrew Lankford
On Sat, Jan 17, 2009 at 10:09:52PM -0500, Andrew Lankford wrote:> After rebuilding world from 7-stable after cvsup, I can no longer boot. > The loader tries to load the kernel but instead locks up with a stack > overflow. Wish I could send more details, but I'll have to find another > way to boot up my system first.just to identify the problem - what was the version of your previous loader, and what kind of CPU do you have (Intel or AMD, single or multi core) etc. (to boot again you can replace /boot/loader with one taken from an older 6.3 or 7.0 CD) cheers luigi
On 2009-Jan-17 22:09:52 -0500, Andrew Lankford <lankfordandrew@charter.net> wrote:>After rebuilding world from 7-stable after cvsup, I can no longer boot. >The loader tries to load the kernel but instead locks up with a stack >overflow. Wish I could send more details, but I'll have to find another >way to boot up my system first.If you press any key during the first spinner, you should get a prompt similar to the following:>> FreeBSD/i386 BOOTDefault: 0:ad(0,a)/boot/loader boot: You can then enter the name of the program you wish to run - eg /boot/loader.old (or directly load /boot/kernel/kernel) See the following for a more complete description: http://www.freebsd.org/cgi/man.cgi?query=boot&apropos=0&sektion=0&manpath=FreeBSD+7.1-RELEASE&format=html Alternatively, you could boot off a "live filesystem" CD. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090118/ff83247f/attachment.pgp
Shortened my loader.conf to the bare essentials and now I'm back in business! Still curious whether redefining loader_conf_files (which I suppose should only be defined in the default loader.conf) caused the problem or whether it was something else. Thanks, Andrew Lankford
On Sun, Jan 18, 2009 at 09:08:56PM +0100, Luigi Rizzo wrote:> On Sun, Jan 18, 2009 at 02:19:23PM -0500, Andrew Lankford wrote: > > Andrew Thompson wrote: > ... > > >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? > > no, this cannot be "fixed" because it is the user misprogramming > the system, such as providing the wrong path to the kernel > or writing a loop in /etc/rc.conf or a billion other ways.Yes, but you can copy /etc/defaults/rc.conf to /etc/rc.conf and things still work.> Setting loader_conf_files="x y z" is basically equivalent to > writing "call a; call b; call c;" in a programming language, > with the only difference that the action is done at the end of > the current file.Ok, then loader_conf_files needs to be marked as special and not to be overridden from /boot/defaults/loader.conf like all the other options. A better way would be to track included files and not reprocess them. Also an entry in UPDATING that a config error that was once harmless now renders the system unbootable (without intervention). cheers, Andrew
Andrew Thompson wrote:> Also an entry in UPDATING that a config error that was once harmless now > renders the system unbootable (without intervention).Would this also be something that mergemaster could check for and warn against? Jim
I suppose that was what was required with XP (normally used boot0, but tinkered with using windows boot as an alternate method), but I haven't had to update boot1 since I first installed everything on this laptop ...so far. Andrew Lankford Bruce Simpson wrote:> Andrew Lankford wrote: >> >> >> FYI: I'm using the Windows Vista boot manager with boot1 instead of >> boot0, although boot1 doesn't appear to have changed since I first >> installed 7.0 on my notebook. > > grub4dos is good, means you don't need to keep dd'ing the boot1 out of > the FreeBSD slice. >