Date: Sat, 04 Sep 2004 16:53:01 +0100 From: Ian Dowse <iedowse@maths.tcd.ie> To: Deng XueFeng <dsnofe@msn.com> Cc: current@freebsd.org Subject: Re: 6-current's BTX loader auto reboot after make world. Message-ID: <200409041653.aa45226@salmon.maths.tcd.ie> In-Reply-To: Your message of "Sat, 04 Sep 2004 23:06:37 %2B0800." <20040904230250.60A0.DSNOFE@msn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20040904230250.60A0.DSNOFE@msn.com>, Deng XueFeng writes: >i use: > >0:ad(0,a)/boot/loader.old > >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 working loader. 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 cd /usr/src/sys/boot 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: cd /usr/src/sys/boot make clean make make install 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. Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409041653.aa45226>