Date: Mon, 09 May 2005 16:26:42 -0500 From: Jonathan Noack <noackjr@alumni.rice.edu> To: noackjr@alumni.rice.edu Cc: David Gurvich <david.freebsd@verizon.net> Subject: Re: loader causes reboot Message-ID: <427FD592.4060103@alumni.rice.edu> In-Reply-To: <427EE6C4.3040100@alumni.rice.edu> References: <200505081529.31238.david.freebsd@verizon.net> <427EDFB4.3070309@alumni.rice.edu> <200505082319.22161.david.freebsd@verizon.net> <427EE6C4.3040100@alumni.rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1A65E006C04024FFCB7C9D4C Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 5/8/2005 11:27 PM, Jonathan Noack wrote: > On 05/08/05 22:19, David Gurvich wrote: >> On Sunday 08 May 2005 23:57, Jonathan Noack wrote: >>> On 05/08/05 14:29, David Gurvich wrote: >>>> cdrom /boot/loader from 5.3 has no problem. However, after updating >>>> world from kernel, /boot/loader is replaced with cvs version. This one >>>> goes into endless cycle of reboots. When replaced with /boot/loader >>>> from >>>> cdrom boots normally. >>> >>> Are you setting CPUTYPE? A few people have reported an endless reboot >>> with the athlon-xp or pentium-m settings. I experience this on my >>> athlon-xp and the only workaround I've found is just to not set CPUTYPE. >>> This problem is way beyond my feeble skills to track down and fix, but >>> it doesn't seem to affect many people and no one has stepped up to >>> resolve it. As it is easily worked around, I've brought it up a few >>> times but haven't made too big of a fuss. Come to think of it, why >>> didn't I ever open a PR? Hmm... perhaps I'll do that at work tomorrow >>> (this is on a machine at work). >> >> I am setting CPUTYPE?=athlon-xp >> I never considered that might be the cause. If it is then there is >> clearly a bug in the configuration of the loader. Perhaps when the >> loader is being compiled it should use the most basic flags possible >> for just that. > > There was an attempt to resolve this issue a few months ago. The commit > was rev. 1.10 of src/sys/boot/i386/Makefile.inc and the log message was, > "Ensure GCC does not use FP registers in integer code." This fix was > MFC'd to RELENG_5 a day later and is present in 5.4. > > For the life of me I can't remember if I tested the change when it was > made. I think it didn't work for me, but I'll test it again tomorrow. Well, looks like it was really fixed. With CPUTYPE?=athlon-xp and 5.4-RELEASE everything works fine. -- Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195 --------------enig1A65E006C04024FFCB7C9D4C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFCf9WSUFz01pkdgZURAuHEAJ9anO5a0adnKBfAYpSl9xqErHGN1wCeMbNC NGETaKCHp10RfDfHiedrwmA= =oziy -----END PGP SIGNATURE----- --------------enig1A65E006C04024FFCB7C9D4C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?427FD592.4060103>