From owner-freebsd-current@FreeBSD.ORG Fri Jul 30 00:39:49 2004 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 88AC816A4CE for ; Fri, 30 Jul 2004 00:39:49 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D09543D60 for ; Fri, 30 Jul 2004 00:39:49 +0000 (GMT) (envelope-from kan@FreeBSD.org) Received: from freefall.freebsd.org (kan@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i6U0dnBW017643 for ; Fri, 30 Jul 2004 00:39:49 GMT (envelope-from kan@freefall.freebsd.org) Received: (from kan@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6U0dnLl017642 for freebsd-current@freebsd.org; Fri, 30 Jul 2004 00:39:49 GMT (envelope-from kan) Date: Fri, 30 Jul 2004 00:39:49 +0000 From: Alexander Kabaev To: freebsd-current@freebsd.org Message-ID: <20040730003949.GA17506@freefall.freebsd.org> References: <20040729235949.GA2185@parodius.com> <20040730001444.GA2544@parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040730001444.GA2544@parodius.com> User-Agent: Mutt/1.4.1i Subject: Re: Latest CVS: disklabel broken? 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: Fri, 30 Jul 2004 00:39:49 -0000 On Thu, Jul 29, 2004 at 05:14:44PM -0700, Jeremy Chadwick wrote: > Minor typo/clarification: the transition problem lies between boot1 > and boot2, it seems. > > On one of the machines (which uses boot1 across serial console), > the system reports "Invalid partition" when trying to boot from -- > and yes, this is not a typo -- 0:ad(0,`). Manually typing in the > correct device (which is 0:ad(0,a)) causes the machine to spit out > an exception error and reboot automatically. > > Just wanted to clarify on that point. > GCC 3.4 seems to be very likely cause of this problem. I guess your only option is to get boot2 file from a system which predates GCC 3.4 and install in on broken boxes. I am trying to find the likely cause of this failure. The very first idea I managed to think of is that your problem is yet another fallout from new GCC unit-at-a-time optimisation mode. Could you please test an attached patch and report results here? Index: Makefile =================================================================== RCS file: /home/ncvs/src/sys/boot/i386/boot2/Makefile,v retrieving revision 1.55 diff -u -r1.55 Makefile --- Makefile 17 Feb 2004 07:13:03 -0000 1.55 +++ Makefile 30 Jul 2004 00:31:37 -0000 @@ -22,6 +22,7 @@ CFLAGS= -Os \ -fno-guess-branch-probability -fomit-frame-pointer\ + -fno-unit-at-a-time \ -mno-align-long-strings \ -mrtd \ -D${BOOT2_UFS} \