From owner-freebsd-current@FreeBSD.ORG Thu Aug 5 12:55:11 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 C57FE16A4CE; Thu, 5 Aug 2004 12:55:11 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 218F143D48; Thu, 5 Aug 2004 12:55:09 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.201] ([192.168.0.201]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i75CsIph006189; Thu, 5 Aug 2004 06:54:18 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <41122DAE.9090501@samsco.org> Date: Thu, 05 Aug 2004 06:53:02 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.1) Gecko/20040801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Kabaev References: <4109B4EF.605@samsco.org> <20040730152119.GA43119@freefall.freebsd.org> <20040805062728.GA58762@freefall.freebsd.org> In-Reply-To: <20040805062728.GA58762@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: FreeBSD Current List Subject: Re: HEADS UP! boot2 problems 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: Thu, 05 Aug 2004 12:55:11 -0000 Alexander Kabaev wrote: > On Fri, Jul 30, 2004 at 03:21:19PM +0000, Alexander Kabaev wrote: > >>On Thu, Jul 29, 2004 at 08:39:43PM -0600, Scott Long wrote: >> >>>All, >>> >>>The GCC 3.4 import seems to have broken the boot2 loader on at least >>>i386. This doesn't affect normal world and kernel builds and installs, >>>but does affect writing new bootblocks via the disklabel program. You >>>should refrain from doing this until it gets fixed. It's being looked >>>into right now. >>> >>>Scott >> >>Commit below made boot2 usable again. > > > As suggested by Matt Dillon, the problems were caused by imcompletely > zeroed out BSS. I merged approproate fixes from DragonflyBSD in commit > below. Success/failure reports from people affected are appreciated. Thanks! Scott