From owner-freebsd-current@FreeBSD.ORG Mon May 9 04:17:02 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9533F16A4E6 for ; Mon, 9 May 2005 04:17:02 +0000 (GMT) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 644C743D86 for ; Mon, 9 May 2005 04:17:02 +0000 (GMT) (envelope-from david.freebsd@verizon.net) Received: from OSTest ([68.161.118.114])0.04 <0IG7006DWFWDJLH5@vms048.mailsrvcs.net> for freebsd-current@freebsd.org; Sun, 08 May 2005 23:17:02 -0500 (CDT) Date: Sun, 08 May 2005 23:19:21 -0400 From: David Gurvich In-reply-to: <427EDFB4.3070309@alumni.rice.edu> To: noackjr@alumni.rice.edu, freebsd-current@freebsd.org Message-id: <200505082319.22161.david.freebsd@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200505081529.31238.david.freebsd@verizon.net> <427EDFB4.3070309@alumni.rice.edu> User-Agent: KMail/1.8 Subject: Re: loader causes reboot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2005 04:17:02 -0000 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. 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).