6-current's BTX loader auto reboot after make world.
iedowse at maths.tcd.ie
Sat Sep 4 08:53:02 PDT 2004
In message <20040904230250.60A0.DSNOFE at msn.com>, Deng XueFeng writes:
>to enter system, then:
># mv loader.old loader.
>reboot, all is ok.
>My last build world is 2004-08-02.
>Is there any change to loader during there days?
The amd64 module support and a few other changes went in during
that timeframe. If possible, could you try to track down which
changes are to blame? This will involve using cvs or cvsup to update
the boot code to a few different versions and test if you get a
First make sure you have a working copy of the loader (e.g. copy
to /boot/loader.good and test that it works).
To test each case, you'll first need to update your boot code sources
to a particular date. With CVS, you'd use
env TZ=GMT cvs update -D'2004/08/28 14:00:00' (for example)
With cvsup you can add a 'date=2004.08.28.14.00.00' for example to
your supfile and `cvsup ... -i src/sys/boot supfile'. To build and
install the loader you'll need to do something like:
Some dates that are worth checking are:
2004/08/28 14:00:00 GMT (before amd64 loader work started)
2004/08/28 17:00:00 GMT (after addition of helper functions)
2004/08/29 00:00:00 GMT (after relocation changes)
2004/08/29 02:00:00 GMT (all amd64 loader changes complete)
It would be great if you could narrow down when the problem was
introduced this way, as it may be hard to find otherwise.
More information about the freebsd-current